Vero 4k wired ethernet dropouts

Help and Support Vero 4K / Vero 4K +
1

Setup:

Vero 4k
fstab smb mounts
wired ethernet
mysql db
smb shares
tvheadend (separate server)

I have a very odd network issue preventing me from enjoying this new device. I saw many posts about streaming/buffering, modified my settings and things work okay…there is no stuttering or anything.

But at some point, the box will just stop communicating with samba machine. So the buffer will run out, a new video won’t start, interface freezes, all fun stuff. The same thing happens if I watch the PVR, eventually the tvh host can’t be reached. Since I’m using mysql db, when it drops out this causes even more UX problems.

I can ssh in without issues when this happens. I can’t ping the SMB server anymore, the fstab mount freezes and eventually after a few minutes it starts back up and connectivity resumes.

I see just 1 or 2 dropped packets in ifconfig, I can see via netstat sometimes network queues that aren’t zero and a few syn_sent while it’s in this state.

I have several kodi boxes, this is the first time I’ve had any issue like this. Even when nothing is playing, I’ll get packet loss. The vero replaced a PC running Kodi, so cabling, connectivity is all the same and was working for years.

Is something happening under load? I see every 5 mins it does timers on tvh, or the skin updates playlists/stats, maybe?

Very random, two pings a couple minutes apart. Box is idle.

osmc@htpc:/var/log$ ping itchy
PING itchy (192.168.100.76): 56 data bytes
64 bytes from 192.168.100.76: seq=6 ttl=64 time=0.804 ms
64 bytes from 192.168.100.76: seq=7 ttl=64 time=0.805 ms
64 bytes from 192.168.100.76: seq=8 ttl=64 time=0.932 ms
64 bytes from 192.168.100.76: seq=9 ttl=64 time=0.809 ms
64 bytes from 192.168.100.76: seq=10 ttl=64 time=0.998 ms

--- itchy ping statistics ---
11 packets transmitted, 5 packets received, 54% packet loss
round-trip min/avg/max = 0.804/0.869/0.998 ms
osmc@htpc:/var/log$ ping itchy
PING itchy (192.168.100.76): 56 data bytes
64 bytes from 192.168.100.76: seq=0 ttl=64 time=0.832 ms
64 bytes from 192.168.100.76: seq=1 ttl=64 time=0.821 ms
64 bytes from 192.168.100.76: seq=2 ttl=64 time=0.790 ms
64 bytes from 192.168.100.76: seq=3 ttl=64 time=0.669 ms
64 bytes from 192.168.100.76: seq=4 ttl=64 time=0.810 ms

--- itchy ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.669/0.784/0.832 ms
2

We need logs.

3

Ensure that there are no IP address conflicts on the network. They can cause this kind of behaviour.

4

I’ll check for conflicts, but all hosts work via DHCP. I’ll change it’s fixed lease, perhaps something will change.

I’ve been looking at Kodi and system logs, but nothing is pointing to an issue. I’m just seeing the fallout from the connection being lost.

5

It’s a “feature” of Linux that it doesn’t report IP conflicts, so you’re unlikely to see anything in the system log.

Nevertheless I’d recomend you install arp-scan and run sudo arp-scan -I eth0 -l to see if it shows anything. It’s a quick test.

Is there anything in your network, such as switches, that might cause issues?

6

I changed my lease, will test more.

Will also try the arp-scan.

7

I think this did it! I had an android device on a fixed ip for some reason and it would wake up and cause havoc it seems.

8

Try use an IP, not hostname resolution. It could simply be that DNS is problematic on your network.
Static IPs make things a lot simpler.

Sam