Thing are working at the moment. It turned out to be some weirdness with my wireless router. All of my machines could see the router and could get to the internet… but some of the machines were not able to see one another. I restarted the router and all seems to be working.
Not sure if it was due to my clients all running different 802.11 speeds of b/g/n. I am currently using a OLD USB wireless NIC for my OpenBSD machine. Can anyone recommend a good wireless, mini-PCI NIC that is compatible with OpenBSD? Has to be mini-PCI. I am running on a Shuttle XPC machine, and it only has a mini-PCI slot. Or, I could use another (albeit newer) USB NIC. Thanks, Dan. On Jan 24, 2014, at 10:18 AM, Peter N. M. Hansteen <pe...@bsdly.net> wrote: > Dan Daley <ddda...@yahoo.com> writes: > >> I am new to OpenBSD and just installed 5.4 on an AMD 64 machine. >> Still running generic kernel. > > Unless you have very specific needs that are somehow not met by > GENERIC, the general advice is to not bother compiling your own. > >> sshd is running and I can ssh into the local machine using ssh >> 192.168.1.4 >> >> However, if I attempt to ssh into the box from another machine on >> the network, I get "Operation timed out" > > I'd try the obvious things first, like checking that the boxes on the > local net agree on the netmask, check that they can ping each other, > check ifconfig output to see that you actually have a link (you want > "status: active" in the output for the relevant interface) and so on. > >> I tried disabling pf by adding PF=NO to rc.conf.local, to make sure >> that that wasn't the culprit, but that didn't help. > > Editing the file was followed by "sudo pfctl -d" or a reboot to make > extra sure? The default pf.conf allows ssh in anyway, so unless you > changed it, that would normally not be the problem. > >> I also attempted to telnet to port 22 to see if I received the SSH >> header response but that timed out with no response. >> >> Also tried with a hosts.allow with ALL: 192. >> >> Any other suggestions to assist troubleshooting this? I haven't >> seen any messages output to any of the logs when attempting to ssh >> into the machine. > > ssh running but producing no messages anywhere means that it's not > seeing any traffic. to me this sounds like a basic connectivity issue > or a banal misconfiguration, but ICBW. > > - Peter > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
