Since nobody has actually definitively stated that it works for them: I've just tested mine and I can successfully access machines on my LAN. Admittedly I'm running RISC OS rather than Linux, but it rules out an issue with the actual Pi hardware/firmware.
Behodar: Since nobody has actually definitively stated that it works for them: I've just tested mine and I can successfully access machines on my LAN. Admittedly I'm running RISC OS rather than Linux, but it rules out an issue with the actual Pi hardware/firmware.
Googling hasn't helped me so I assume the issue is isolated to mine. But just can't see how hardware could cause such a specific network fault.
Assume the Pi runs some kind of base firmware tho? Like a BIOS. Wonder if there could be something dodgy there
Indeed, it does seem very strange! Like you say, there must be some sort of "firmware loader"; I believe that there's a firmware image on the SD card but even then it needs to know how to load that in the first place.
gstarkey: Can you post the output of the following commands, when run on the Pi: ifconfig netstat -r
Also firewall can cause this, what do you get from: /sbin/iptables -L
Yep. Will do this tonight when I get home and post back. I rebooted it remotely before and it hasn't come back online (sometimes gives me a card read error on warm reboot)
Had a quick scan of this thread again, couldn't see if you had said if you could ping devices or not. The implication in a lot of what you have written is that you cannot - but the assuming something is the mother of all cock ups so...
Can you ping your router? Can you ping any other device on your LAN? Have you tried to force a IPv4 ping? (e.g. ping -4 192.168.1.1)
nzkc: Had a quick scan of this thread again, couldn't see if you had said if you could ping devices or not. The implication in a lot of what you have written is that you cannot - but the assuming something is the mother of all cock ups so...
Can you ping your router? Can you ping any other device on your LAN? Have you tried to force a IPv4 ping? (e.g. ping -4 192.168.1.1)
Can ping the router from the Pi Can ping the Pi from LAN hosts Cannot ping LAN hosts from the Pi
nzkc: Had a quick scan of this thread again, couldn't see if you had said if you could ping devices or not. The implication in a lot of what you have written is that you cannot - but the assuming something is the mother of all cock ups so...
Can you ping your router? Can you ping any other device on your LAN? Have you tried to force a IPv4 ping? (e.g. ping -4 192.168.1.1)
Can ping the router from the Pi Can ping the Pi from LAN hosts Cannot ping LAN hosts from the Pi
ping -4 didn't work. Says invalid option
When you say: Cannot ping LAN hosts from the Pi Do you use name or IP address, if only name try IP address
gstarkey: When you say: Cannot ping LAN hosts from the Pi Do you use name or IP address, if only name try IP address
If name it successfully resolved IP from hostname, but fails to ping. If IP - fails
pi@raspbmc:~$ ping -c 4 media1 PING media1 (192.168.1.50) 56(84) bytes of data. From raspbmc (192.168.1.70) icmp_seq=1 Destination Host Unreachable From raspbmc (192.168.1.70) icmp_seq=2 Destination Host Unreachable From raspbmc (192.168.1.70) icmp_seq=3 Destination Host Unreachable From raspbmc (192.168.1.70) icmp_seq=4 Destination Host Unreachable
pi@raspbmc:~$ ping -c 4 192.168.1.50 PING 192.168.1.50 (192.168.1.50) 56(84) bytes of data. From 192.168.1.70 icmp_seq=1 Destination Host Unreachable From 192.168.1.70 icmp_seq=2 Destination Host Unreachable From 192.168.1.70 icmp_seq=3 Destination Host Unreachable From 192.168.1.70 icmp_seq=4 Destination Host Unreachable
pi@raspbmc:~$ ping -c 4 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.774 ms 64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.681 ms 64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.668 ms 64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.647 ms
pi@raspbmc:~$ ping -c 4 geekzone.co.nz PING geekzone.co.nz (108.162.203.66) 56(84) bytes of data. 64 bytes from 108.162.203.66: icmp_req=1 ttl=57 time=16.7 ms 64 bytes from 108.162.203.66: icmp_req=2 ttl=57 time=17.1 ms 64 bytes from 108.162.203.66: icmp_req=3 ttl=57 time=16.6 ms 64 bytes from 108.162.203.66: icmp_req=4 ttl=57 time=17.0 ms
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
