I learned that iperf shows that even PI3B+ ethernet can do 318Mbps:
I wanted to test raspividyuv traffic between PI3B and laptop.
Unfortunately there is only one ethernet cable in vacation house.
So I measured between PI3B with ethernet cable and PI2B with 300Mbps USB Wifi dongle.
For measurement I had to add "-w 1" to sender netcat command, otherwise the connection would hang endlessly.
I added "-pts tst.pts" to raspividyuv command, and reduced framerate to 75fps in order to go back to 261Mbps.
What I measured was crap, analysis of tst.pts with ptsanalyze showed frameskips all over the place.
Next I tried to run the test locally, and reroute traffic from PI3B to PI3B via default gateway.
It took quite some time to find solution for that here:
Unfortunately the script did not work, I had to replace one of its commands with slightly different and add another command.
I did add determination of ip from passed interface and gw to the scipt local2gw:
https://gist.github.com/Hermann-SW/5641 ... 83b2900cfa
After ssh into PI3B (192.168.87.115) after reboot I do "sudo ./local2gw eth0" and send traffic to 192.168.87.115.
Running ipconfig afterwards shows that all traffic went through eth0, and 0 packets were sent/received on loopback interface.
Because still seeing junk, I reduced traffic to 142Mbps by changing raspividyuv options (-md 1 -fps 6).
Still seeing a lot of framelosses with ptsanalyze.
So I will have to wait for a 2nd ethernet cable to do the measurements between PI3B and something else, both connected via Gigabit ethernet.
I just installed ethtool and it confirms that the router only allows for "Speed: 100Mb/s".
Either I will do the measurements in 9 days when back home, or perhaps somebody else does them before.
You can find ptsanalyze in my userland fork tool directory:
https://github.com/Hermann-SW/userland/ ... ptsanalyze