I just installed the latest raspbian image available on the download page (2012-07-15). Installation went flawlessly but I am having some issues with my network interface. As the dhcp wouldn't allocate an ip address, I changed my interfaces file to make it static. The iface eth0 is up and running and has an ip address but I get a lot of packet error/lost (more than 90% on the RX packets). Therefore, networking is unusable. ping'ing another host on my lan takes ages whens it work and often returns "network unreachable" although the kernel IP routing table looks ok. The syslog files remain silent and only confirms that the eth0 is up and running ok.
First time I have such a problem on a linux box. Any hint for troubleshooting?
Network problem
Using Linux command line usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Re: Network problem
What is the voltage between the test points on the board? ethernet is often one of the first things to stop working properly if the voltage is too low.
Re: Network problem
I don't know how much pc's you have, but please try:
Another switch/router (maybe the error is there), or another cable.
If you have 2 normal x86 pc's / laptops, can they ping eachother neatly?
Another switch/router (maybe the error is there), or another cable.
If you have 2 normal x86 pc's / laptops, can they ping eachother neatly?
Re: Network problem
@plugwash: I have btw 4.85 and 4.90 v. . Power supply is the stock one supplied by rs components. I have also disconnected all peripherals except the ethernet cable as I suspected either the HDMI-DVI cable or the keyboard/mouse to drain too much current.
@LeroyZ84: I have connected the rpi straight into my laptop and gave them both an IP on the same subnet. No better.
It really make me think of a hw problem. Nothing weird in the logs.
@LeroyZ84: I have connected the rpi straight into my laptop and gave them both an IP on the same subnet. No better.
It really make me think of a hw problem. Nothing weird in the logs.
Using Linux command line usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Re: Network problem
@plugwash: I have btw 4.85 and 4.90 v. . Power supply is the stock one supplied by rs components. I have also disconnected all peripherals except the ethernet cable as I suspected either the HDMI-DVI cable or the keyboard/mouse to drain too much current.
@LeroyZ84: I have connected the rpi straight into my laptop and gave them both an IP on the same subnet. No better.
It really make me think of a hw problem. Nothing weird in the logs.
@LeroyZ84: I have connected the rpi straight into my laptop and gave them both an IP on the same subnet. No better.
It really make me think of a hw problem. Nothing weird in the logs.
Using Linux command line usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Re: Network problem
Did you use a cross over cable (or have a switch in between)?ripat wrote:@LeroyZ84: I have connected the rpi straight into my laptop and gave them both an IP on the same subnet. No better.
http://mmm-pi.co.uk - my adventures with a Pi
Re: Network problem
No cross over cable. Just a regular patch cable as I usually do with my other linux devices (routers WAP). I just tried archLinux. Same problem. I will try to connect them through another switch but I doubt this could solve the problem.
Using Linux command line usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Re: Network problem
Not better on another switch and different cables. My usual switch never caused any problem with any other host. I really suspect a fried ethernet port. All led are lit. Still nothing in syslog.
Never had this type of problem before. Am I the only one with faulty Rpi? Would RS component accept to replace it under warranty? And, most importantly, will I have to wait another 11 weeks to get that replacement unit?
Never had this type of problem before. Am I the only one with faulty Rpi? Would RS component accept to replace it under warranty? And, most importantly, will I have to wait another 11 weeks to get that replacement unit?
Using Linux command line usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Re: Network problem
sorry to hear no solution has been found yet.
about warranty, i can't tell you.. I was wondering, did you use another UTP cable?
is there proberbly any fysical damage to the port? e.g. the connector is close-circuited? (my englisch s**cks...)
there are 8 coper strains in the rj45 connector, perhaps 2 of them make contact with eachother?
edit:
does ifconfigh eth0 show any errors? e.g
about warranty, i can't tell you.. I was wondering, did you use another UTP cable?
is there proberbly any fysical damage to the port? e.g. the connector is close-circuited? (my englisch s**cks...)
there are 8 coper strains in the rj45 connector, perhaps 2 of them make contact with eachother?
edit:
does ifconfigh eth0 show any errors? e.g
Code: Select all
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:81014 errors:0 dropped:0 overruns:0 frame:0
TX packets:20028 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
Re: Network problem
No apparent physical damage to the ethernet port. I tried different cables, no change .
A s for the ifconfig, I can't even copy/paste the result of ifconfig but, yes, it returns something likeTX packet seem to go through but all RX packets are blocked for any reason. So, I started tcpdump on my router and launched a ping from the Rpi to a host or on my router and the ARP 'who has' packet seem to be broadcasted in some way. The Rpi has 192.168.0.117.
My kernel routing table:
I am really puzzled. May be a routing problem. Can someone post his routing table?
A s for the ifconfig, I can't even copy/paste the result of ifconfig but, yes, it returns something like
Code: Select all
eth0 Link encap:Ethernet HWaddr 00:1f:e2:12:ea:d8
inet adr:192.168.0.117 Bcast:192.168.0.255 Masque:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:376 dropped:163 overruns:0 frame:163
TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
Code: Select all
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
20:09:57.494750 ARP, Request who-has ibm.lan tell 192.168.0.117, length 46
20:09:58.494607 ARP, Request who-has ibm.lan tell 192.168.0.117, length 46
....
20:10:06.874654 ARP, Request who-has openwrt.lan tell 192.168.0.117, length 46
20:10:07.874516 ARP, Request who-has openwrt.lan tell 192.168.0.117, length 46
Code: Select all
Destination Gateway Genmask Indic Metric Ref Use Iface
0.0.0.0 192.168.0.200 0.0.0.0 UG 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
Using Linux command line usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Re: Network problem
More over packet sent. When I configure the interfaces file for dhcp, the UDP dhcp packets reach the router (which is also the dhcp server for my lan) and my router seem to send a reply back to the Rpi but with no effect on it just as if the response packets never reach the Rpi.
On the Rpi:
tcpdump on the router:
I won't give up until I am sure its a hw issue!
Edit: I am not the only one having exactly the same problem:
http://www.raspberrypi.org/phpBB3/viewt ... 28&t=12799
On the Rpi:
Code: Select all
# dhclient -v -d eth0
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/b8:27:eb:a1:0e:2d
Sending on LPF/eth0/b8:27:eb:a1:0e:2d
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67 interval 6
DHCPREQUEST on eth0 to 255.255.255.255 port 67 interval 10
DHCPREQUEST on eth0 to 255.255.255.255 port 67 interval 19
and so on...Code: Select all
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
20:30:50.840038 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:27:eb:a1:0e:2d, length 300
20:30:53.094039 IP 192.168.0.200.67 > 192.168.0.175.68: BOOTP/DHCP, Reply, length 300
20:30:54.151267 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:27:eb:a1:0e:2d, length 300
20:30:54.152394 IP 192.168.0.200.67 > 192.168.0.175.68: BOOTP/DHCP, Reply, length 300
Edit: I am not the only one having exactly the same problem:
http://www.raspberrypi.org/phpBB3/viewt ... 28&t=12799
Using Linux command line usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Re: Network problem
That post concerns a problem caused by a hub powered RPi. Mine is powered by the stock power supply that RS Component recommends for the RPi. I am more and more convinced that it is a hw problem on the NIC. See the other post I refer to in my post above. Exactly the same problem.
Using Linux command line usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Re: Network problem
I am also experiencing network problems. On latest Rasbian Wheezy fully updated. Board voltage 5.05V on test points. .Direct connection to BT HomeHub. Sound dongle on first USB and hub with keyboard and mouse connected on second USB. System gets time and sets clock OK at boot.
If I ping my router after login it works very well with round trip time about 1.05mS. Problem is when I go into LXDE. With no other applications running I can open LXTerminal and ping the router, there is a long delay of many seconds then usually the first three pings or so often come back as unreachable and those pings that do come back show a time of 22 seconds or more dropping to around 470mS (if I'm lucky). With any other applications running it is much worse, usually unreachable. Midori sometimes makes connection but often fails to connect. Unplug sound dongle and network is accessible and Midori works normally.
Seems to be a major problem when using the sound dongle. I have tried several USB sound devices and this one is the only one that works at all on input. My problem is that my application analyses and decodes data from incoming audio and uploads data to the internet at regular intervals so I need both working. This must be the known interaction between network and USB on the RPi.
If I ping my router after login it works very well with round trip time about 1.05mS. Problem is when I go into LXDE. With no other applications running I can open LXTerminal and ping the router, there is a long delay of many seconds then usually the first three pings or so often come back as unreachable and those pings that do come back show a time of 22 seconds or more dropping to around 470mS (if I'm lucky). With any other applications running it is much worse, usually unreachable. Midori sometimes makes connection but often fails to connect. Unplug sound dongle and network is accessible and Midori works normally.
Seems to be a major problem when using the sound dongle. I have tried several USB sound devices and this one is the only one that works at all on input. My problem is that my application analyses and decodes data from incoming audio and uploads data to the internet at regular intervals so I need both working. This must be the known interaction between network and USB on the RPi.