Raspberry PI Odd Network Issue - Can't access LAN hosts

Check our new Geekzone Price Comparison web site for electronics prices in New Zealand.

Forums › Linux › Raspberry PI Odd Network Issue - Can't access LAN hosts

1 | 2 | 3

3015 posts

Uber Geek

Subscriber

Reply # 708548 29-Oct-2012 16:53
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.

ajobbins

Awesome
3090 posts

Uber Geek

Trusted

Subscriber

Reply # 708553 29-Oct-2012 17:00
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 Twitter: ajobbins

Behodar

3015 posts

Uber Geek

Subscriber

Reply # 708555 29-Oct-2012 17:03
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

48 posts

Geek

Reply # 708559 29-Oct-2012 17:11
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

ajobbins

Awesome
3090 posts

Uber Geek

Trusted

Subscriber

Reply # 708564 29-Oct-2012 17:16
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) Twitter: ajobbins

ajobbins

Awesome
3090 posts

Uber Geek

Trusted

Subscriber

Reply # 708743 29-Oct-2012 21:35
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 /sbin/iptables -L didn't work pi@raspbmc:~$ /sbin/iptables -L -bash: /sbin/iptables: No such file or directory pi@raspbmc:~$ ifconfig eth0 Link encap:Ethernet HWaddr b8:27:eb:82:5a:af inet addr:192.168.1.70 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fe82:5aaf/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4557 errors:0 dropped:0 overruns:0 frame:0 TX packets:835 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:384291 (375.2 KiB) TX bytes:99064 (96.7 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:824 (824.0 B) TX bytes:824 (824.0 B) pi@raspbmc:~$ netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface default SFDDWRT1 0.0.0.0 UG 0 0 0 eth0 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 Twitter: ajobbins

nzkc

217 posts

Master Geek

Reply # 708746 29-Oct-2012 21:40
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)

gstarkey

48 posts

Geek

Reply # 708752 29-Oct-2012 21:43
/sbin/iptables -L didn't work pi@raspbmc:~$ /sbin/iptables -L -bash: /sbin/iptables: No such file or directory pi@raspbmc:~$ ifconfig eth0 Link encap:Ethernet HWaddr b8:27:eb:82:5a:af inet addr:192.168.1.70 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fe82:5aaf/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4557 errors:0 dropped:0 overruns:0 frame:0 TX packets:835 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:384291 (375.2 KiB) TX bytes:99064 (96.7 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:824 (824.0 B) TX bytes:824 (824.0 B) pi@raspbmc:~$ netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface default SFDDWRT1 0.0.0.0 UG 0 0 0 eth0 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 Look normal. What happens when you ping SFDDWRT1 using (1) name (2) IP address ?

ajobbins

Awesome
3090 posts

Uber Geek

Trusted

Subscriber

Reply # 708759 29-Oct-2012 21:50
Pinging SFDDWRT1 works fine. That's the router. Twitter: ajobbins

ajobbins

Awesome
3090 posts

Uber Geek

Trusted

Subscriber

Reply # 708761 29-Oct-2012 21:51
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 Twitter: ajobbins

nzkc

217 posts

Master Geek

Reply # 708764 29-Oct-2012 21:56
Have you tried a traceroute to one of your LAN hosts? Does it fall over at the Pi or the router?

gstarkey

48 posts

Geek

Reply # 708771 29-Oct-2012 22:09
ajobbins: 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

ajobbins

Awesome
3090 posts

Uber Geek

Trusted

Subscriber

Reply # 708780 29-Oct-2012 22:28
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 Twitter: ajobbins

ajobbins

Awesome
3090 posts

Uber Geek

Trusted

Subscriber

Reply # 708784 29-Oct-2012 22:37
The plot thickens. There is another windows host on the LAN presenting the same symptoms (One I hadn't tested with) as the Pi. Twitter: ajobbins

mjb

904 posts

Ultimate Geek

Trusted

Subscriber

Reply # 708785 29-Oct-2012 22:41
ajobbins: The plot thickens. There is another windows host on the LAN presenting the same symptoms (One I hadn't tested with) as the Pi. Hmm, that's curious. I'd look at your switch. got another to swap out temporarily? contentsofsignaturemaysettleduringshipping

1 | 2 | 3