Rock 5b, 16Gb: after some runtime the network hangs

[rolsch]

Hi rock5b user 🙂

 

My sbc hangs after 8-14 hours on the network.

 

no ping from inside or outside works

 

# ip link 

- show eth0 up

 

after the commands

ip link set eth0 down
ip link set eth0 up
- the network worgs again,

 

https://paste.armbian.com/tiqabekoje
 

- any hints for this issue?

 

 

[eselarm]

already in the first dmesg part I see:

[54475.779558] r8169 0004:41:00.0 eth0: Link is Down
[54479.115749] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[54479.115748] r8169 0004:41:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
[55390.928391] br-ce724241dce3: port 1(veth1664549) entered disabled state
[55390.928949] veth6932af4: renamed from eth0
[55391.020157] br-ce724241dce3: port 1(veth1664549) entered disabled state
[55391.021811] device veth1664549 left promiscuous mode
[55391.021831] br-ce724241dce3: port 1(veth1664549) entered disabled state
[55391.493933] br-ce724241dce3: port 1(veth1a65439) entered blocking state
[55391.493954] br-ce724241dce3: port 1(veth1a65439) entered disabled state
[55391.494085] device veth1a65439 entered promiscuous mode
[55391.500502] br-ce724241dce3: port 1(veth1a65439) entered blocking state
[55391.500519] br-ce724241dce3: port 1(veth1a65439) entered forwarding state
[55391.539757] eth0: renamed from vethb9b9ca0
[55391.561925] IPv6: ADDRCONF(NETDEV_CHANGE): veth1a65439: link becomes ready

Which means to me that you use containers/docker or so and something on that networking level goes wrong. I think it had nothing specifically to do with Armbian nor ROCK5B.

 

You should figure out what is running on your computer and what is done to networking in general. 

 

I do not use containers like seems to be done here, so cannot really help here. I have no clue about your networking setup and plans.

I use various bridges and VLANs on my ROCK5B (Armbian Trixie), but all strict manually done by myself, only own files in /etc/NetworkManager/system-connections/