06-10-2016, 11:12 AM
I received the board from @androsch, plugged it in, tested - works fine.
iperf2 pine64 is server
iperf2 pine64 is client
So no problem of the board itself and this is probably true for all the other non working 1000M reports here. The reason is something else / external to the Pine64. The switch, the cable, the psu, and a combination of those together with the Pine64. So its up to you folks which have the issue to find out what triggers it (start by replacing the switch).
iperf2 pine64 is server
Code:
root@pine64:~# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[ 4] local 192.168.1.29 port 5001 connected with 192.168.1.232 port 40359
[ ID] Interval Transfer Bandwidth
[ 4] 0.0-10.0 sec 320 MBytes 267 Mbits/sec
iperf2 pine64 is client
Code:
root@pine64:~# iperf -c 192.168.1.232
------------------------------------------------------------
Client connecting to 192.168.1.232, TCP port 5001
TCP window size: 22.5 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.29 port 39981 connected with 192.168.1.232 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 813 MBytes 682 Mbits/sec
So no problem of the board itself and this is probably true for all the other non working 1000M reports here. The reason is something else / external to the Pine64. The switch, the cable, the psu, and a combination of those together with the Pine64. So its up to you folks which have the issue to find out what triggers it (start by replacing the switch).