a windows host, or the (problematic) windows host? Really does sounds like arp poisoning.
edit: does `arp -a` list the MAC addresses of the hosts you're trying to ping? are they correct?
Adam-PC (192.168.1.21) at 90:a4:de:2f:00:38 [ether] on eth0 CANT PING SFDDWRT1 (192.168.1.1) at b0:48:7a:c9:b3:cb [ether] on eth0 CAN PING Media1 (192.168.1.50) at <incomplete> on eth0 CANT PING ? (192.168.1.102) at 5c:0a:5b:30:45:cd [ether] on eth0 CAN PING S685-IP (192.168.1.20) at <incomplete> on eth0 CANT PING
Media1 is the Windows host that is showing the same symptoms as the Pi. I hadn't tried it as the source directly until today as it is a pain to log into.
If 192.168.1.50 can ping 192.168.1.70 (and get an echo reply) But 192.168.1.70 does not get a echo reply when pinging 192.168.1.50. This is very odd (but not unknown). 192.168.1.70 can send to 192.168.1.50, it did it with echo reply. So arp works etc.
Looks like it was a dodgy DD-WRT firmware that was isolating each of the devices plugged into the switch from each other. Flashed a new version and it's now working as expected.
Not sure why it didn't work with the Belkin router I tried yesterday. I didn't do a huge amount of testing with it tho, so I probably over looked something simple there.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
Trusted
