08-24-2016, 11:41 AM
(This post was last modified: 08-24-2016, 03:58 PM by MarkHaysHarris777.)
(08-21-2016, 11:31 AM)androsch Wrote: Have ordered this switch today and will connect my Pine64+ with this switch and all of my GbE-PCs again (each separately and without any other ports active and new cables also). Will take some time (delivery till 24th), so will come back then...
Maybe we get this sorted
some results with the new switch:
Code:
Pine64 as client, only connected via the new switch to the destop:
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.01 sec 470 MBytes 394 Mbits/sec 254 sender
[ 4] 0.00-10.01 sec 470 MBytes 394 Mbits/sec receiver
acting as server, same bad speed again:
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-10.05 sec 693 KBytes 565 Kbits/sec sender
[ 5] 0.00-10.05 sec 606 KBytes 494 Kbits/sec receiver
BUT: while i had to change my network config to give the pine and the desktop a fixed ip for the test, i got some errors during ethtool or ifup/ifdown, so it seems there is something messed up with my network config on the Pine. Could not yet figure it out, cause only chage i made was on
/etc/network/interfaces:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
# Disable wlan1 by default (8723bs has two intefaces)
iface wlan1 inet manual
auto eth0
iface eth0 inet dhcp
# mtu 1492
#iface eth0 inet static
# address 192.168.178.63
# netmask 255.255.255.0
# broadcast 192.168.178.255
# network 192.168.178.0
# mtu 1492
# gateway 192.168.178.1
For the switch as standalon i commented the dhcp-section and activated the fixed ip-part, same here in
/etc/network/interfaces.d/eth0
auto eth0
iface eth0 inet dhcp
## mtu 1492
#iface eth0 inet static
# address 192.168.178.63
# netmask 255.255.255.0
# broadcast 192.168.178.255
# network 192.168.178.0
# mtu 1492
# gateway 192.168.178.1
mtu 1492 is always disabled, that was something i tried earlier...
With dhcp the interface eth0 is coming up and the Pine connects to the network.
With fixed address it boots (had to check with a monitor attached, normally it's headless), but the interface only comes up after logging in at the terminal and calling ifup eth0 as root. It gives a warning (didn't copy that unfortunately), but afterwards the eth-interface shows up (LEDs are blinking) and ifconfig shows a valid ip.
Will try again to use a brand new image from longsleep and repeat those tests. Maybe i messed up some configs by testing and trial-and-error in the beginning....
At least connected it again with my normal switch and it still gives about 400-500 mbits as client, but server is still poor. So its capable to do GbE, just need to sort out why only as client and fix the server part...
Will keep you posted.
Still a linux newbie with several EEE-PCs, PI's, LattePanda and some Desktops/Laptops running Win10. Now also proudly using Pine64+ 2GB and gigabit LAN