New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raspberry PI not working properly on gigabit switch #217
Comments
Does "latest firmware" imply that at some time in the past this worked correctly? |
pi ~ # mii-tool i'm also seeing the same problem on my rpi when plugged directly into a gigabit switch the LED's on the switch say that its only running at 100mbit, and its unmanaged so i cant force things but i'm not seeing any noticeable packet loss, how did you test it? |
Yes, it did work correctly with firmware that was RPI shipped with (sorry I don't know version). About packet loss I use iperf to fetch multicast stream and watch for loss. Funny thing if I connect RPI to "dumb" 100 meg switch it works just fine. No loss, link ok. |
I can confirm that mii-tool reports 1GbE when plugged into a gigabit switch but link is at 100mbit. Bug in the kernel's smsc95xx driver, probably. I've never seen packet loss though. Can you post the iperf commands you used? |
i'm not able to get any packet loss in the RX direction, but i am getting a single lost packet in the TX direction pi ~ # iperf -suServer listening on UDP port 5001 UDP buffer size: 160 KByte (default)[ 6] local 192.168.2.19 port 5001 connected with 192.168.2.61 port 58288 if i run it in the other direction, its 0 lost every time, but from the pi->normal desktop, it always looses 1 packet, not sure how to make it do a longer test |
I am using: /usr/bin/iperf -s -u -B 239.239.2.149 -i 10 -y c To fetch multicasts. To make longer test use -t with how many seconds it should run. But if you want test it with multicast you need to have multicast source. And about firmware version: root@sonda00:~# /opt/vc/bin/vcgencmd version |
hmmm, when in plain udp mode, i cant get it to drop more then 1 packet, and it doesnt seem to play nicely with the multicast stream my ISP is feeding TV over, how do i make my own multicast source? |
To be honest I have no idea. Never tried creating multicast source. I am using one from my IPTV provider. Here are snippets of my log. When connected to gigabit switch: Oct 17 10:21:38 sonda00 iperf: 20131017102138,239.239.2.149,5001,10.200.200.207,53068,3,1150.0-1160.0,25017160,20013728,0.146,1,19011,0.005,0 And snippet when connected via "dumb" 100 megabit switch: Oct 17 11:40:34 sonda00 iperf: 20131017114034,239.239.2.149,5001,10.200.200.207,53068,3,4020.0-4030.0,25018476,20014780,0.037,0,19011,0.000,0 Look at second column from right, it should be always 0. |
And about generating own multicast: http://taosecurity.blogspot.com/2006/09/generating-multicast-traffic.html |
how does it know when its lost a packet in the IPTV stream, udp doesnt have sequence numbers, and iperf shouldnt understand rtp |
when i try the commands from that page, it just goes nuts, printing the same line forever, at infinite speed [ 3] -1380984776.7--1380984766.7 sec 0.00 Bytes 0.00 bits/sec 0.000 ms 0/ 0 (-nan%) |
Sorry but I have no idea how it knows. It always worked flawlessy that way and it still does on other RPIs and one Beagle Bone. Only one having trouble is that one with updated firmware. And one thing, this is firmware version on working fine RPI:
Also I contacted more knowledlable technician and it seems that multicast we are receiving for testing purposes is not IPTV stream but a stream from iperf with 20 Mbps UDP. |
BTW maybe you have some kind of multicast routing issues. So you could try in plain UDP mode 20 megabits (-b 20M), because by default iperf is generating only 1 Mbps. |
hmmm, when i try to push 1000mbit from pi->desktop, it only goes thru at 95mbit, and only a single packet is lost not seeing any major packet loss, even when forcing it to go 10x faster then the link can handle |
Sorry for making a mess but I did tests with plain UDP mode and can't reproduce trouble that I get with multicast. So in fact it may be problem with mii-tool reporting only and multicast trouble is some kind of "side effect". |
i have had other multicast problems over wifi, the source simply expects more bandwidth, so it winds up DoS'ing the wifi completely, nothing works until i leave the multicast group |
Hello, I know I can't reproduce it properly, but we have installed another few RPIs and used firmware that was
And on following gives loss:
|
Is your reported issue simply that the ethernet connection speed is reported as 100mbit on the 1st september 2013 release and 1gbit on the 12th oct release? |
It is about two things:
Altough I can't prepare a test case for a second issue for you to reproduce. So lets say it is inly about 1). |
I faintly remeber to have read that mii-Tools is no longer properly supported by the Linux kernel, but one should use ethtool instead. Wait a Minute... http://ubuntuforums.org/showthread.php?t=1680837 |
@alchemyx is this still an issue? |
Sorry I don't have access to spare RPI anymore to check it. Michał Margula, alchemyx@uznam.net.pl, http://alchemyx.uznam.net.pl/ Dnia 17 cze 2015 o godz. 19:56 Rasmus Christiansen notifications@github.com napisał(a):
|
@cleverca22 do you still have an issue? |
@popcornmix this issue seems to be stalled |
Hi, i want only ask, if is this issue have some solution, becouse i have still this issue. When i plug in to 1000gb ether, havnt link, only when i change operation speed-duplex to 100Full than have link and working without packet lost. |
This issue was on very early devices (last post 2015), so its likely your issue is different. Please start a new issue, with a lot more details on exactly what is happens. Which Pi, which switch, which OS, how you are testing, what symptoms are etc. |
Hello,
With latest firmware I have a strange issues when RPI is connected to gigabit switch. It reports via mii-tool that it has 1000 half duplex link and gives some packet loss. On switch I see that it is 100 full duplex.:
If I force 100 full duplex on switch side, RPI starts to report properly 100 full duplex:
So for me it is a definitely a bug, because ethernet on RPI is 100 Mbps.
The text was updated successfully, but these errors were encountered: