Same load of retries as the others are getting
osmc@Kodibox:~$ iperf3 -c 192.168.1.10
[ ID] Interval Transfer Bandwidth Retr
Asus RT-AC88U router. Which again, works fine over WIFI and works fine over ethernet with the other Kodibox.
fzinken
20 September 2018 11:21
254
If you don’t mind maybe you can set speed to 100 MBit with ethtool to check if at least that is stable.
ethtool -s eth0 speed 100 duplex full autoneg off
IPERFS, reverse and forwards, after ethtool
osmc@Kodibox:~$ iperf3 -R -c 192.168.1.10
[ ID] Interval Transfer Bandwidth
iperf Done.
[ ID] Interval Transfer Bandwidth Retr
iperf Done.
fzinken
20 September 2018 11:27
256
IPERFS, reverse and forwards, after ethtool
Ok so that is definetly different to problems others have reported
Set it back to 1000 afterwards. Same load of retries and slow speeds.
osmc55
20 September 2018 11:29
258
that’s at least 3 people saying the vero4k+ can’t handle gigabit which is worrying - the only reason i bought one (still waiting).
as for missing images, i noticed the same lately on my raspberry pi 3’s running libreelec, although my atom running kodi 18 nightlies fetches the images fine using the same fileserver/switch.
the atom is using ubuntu with nfs4 over gige and the pi’s are using nfs3 (despite what the devs say libreelec cannot do nfs4) on 100mbit.
so image problem could be a kodi 17 vs 18 issue, or could be arm vs x86 etc. no idea about network issue though until my 4k+ turns up.
Yeah, unclear if others have issues one way, or two ways.
But dropping to 100, or swapping to WIFI, seems to fix the retries on one of the other threads too. Seems related.
fzinken
20 September 2018 11:36
260
But dropping to 100, or swapping to WIFI, seems to fix the retries on one of the other threads too. Seems related
But that is the strange thing on yours dropping to 100Mbit only fixes one direction
osmc55
20 September 2018 11:38
261
have you got a gigabit switch you can try with, routers with gigabit are generally pretty naff.
assume you don’t have jumbo frames enabled (mtu 9000)?
ip link show eth0
edit: no logs say 1500 mtu
Ha. Didn’t notice. Was looking at retries.
So, at 100 iperf3 -R is slow as hell (2Mbits), but the other way is fine (81Mbits).
Excellent. If I can combine the two it’ll either be the slowest device ever or work ok
Smurphy
20 September 2018 12:03
263
That is why I had requested a packet capture. The TTL should tell us where the retries are coming from (Device).
Nope. Not messing with the router. It works fine. It works fine with VERO under WIFI, it works fine with the other Kodi box. It happily feeds streams from the server to multiple devices over ethernet and wifi.
1 Like
Smurphy
20 September 2018 12:16
265
Has nothing to with messing with the router. If there are retries, they come from somewhere.
I took some regular parameters from my vero device.
root@vero4k2:~# ethtool -i eth0
root@vero4k2:~# ethtool -c eth0
rx-usecs: 393
tx-usecs: 40000
rx-usecs-low: 0
rx-usecs-high: 0
root@vero4k2:~# ethtool -g eth0
Smurphy - I was replying to the guy above asking about my “pretty naff” router.
As requested though:
osmc@Kodibox:~$ ethtool -i eth0
osmc@Kodibox:~$ ethtool -a eth0
osmc@Kodibox:~$ ethtool -c eth0
rx-usecs: 393
tx-usecs: 40000
rx-usecs-low: 0
rx-usecs-high: 0
ethtool -g eth0
osmc@Kodibox:~$ ethtool -S eth0
osmc@Kodibox:~$ ethtool eth0
eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
Smurphy
20 September 2018 12:37
267
Well, the pause parameters on your end are not negociated.
osmc@Kodibox:~$ ethtool -a eth0
You also have some errors:
Advertised pause frame use: Symmetric Receive-only
The rest seems clean. Could you try activating Autonegociation:
ethtool -A autoneg on eth0
Don’t know if it helps, but that is the only real diffference I would think of.
Any chance you could provide me a packet capture while transfering some data.
sudo tcpdump -c 100000 -i eth0 -w /tmp/output.pcap
Note that you will need the vero to generate traffic etc. You can interrupt traffic captur anytime with ctrl-c.
Only shell stuff I’ve done is FSTAB and IPERF and stuff listed here. I’ve tried every combination of network setting available directly through OSMC. Will try your suggestions.
Smurphy
20 September 2018 12:55
269
Well, I suspect it to be an incompatiblity on the interfaces.
Well, the pause parameters on your end are not negociated.
That’s just the DHCP on or off through the menu. Turned it back on. Tried both ways.
osmc@Kodibox:~$ ethtool -a eth0
Still 79 retries from iperf.
Smurphy
20 September 2018 13:10
271
Could you send me a packet capture of it?
sudo apt install tcpdump
Then issue the command as before in the thread.