Network connection lost after reboot or resume from suspend

1st Official Post

    I have been running OMV for quite a number of years, I have two identically configured devices, both running on AMD A10 -7700K motherboards, patched up to v6.5.4-1. I use these devices to provide NFS/CIFS shares and they also run Docker to support a MariaDB container but generally they are fairly simple bog-standard configurations. I only update these machines using the built in OMV update procedures.


    I use the Autoshutdown plugin to suspend both these machines each evening at 22:00 and they rewake at 07:00 the following day. This has worked really well for a long time but recently one machine seems to loose its network configuration (enp3s0) when it is rebooted or resumes from suspension. Running omv-firstaid fixes the problem but I would like to know how to fix it so that this problem doesn't re-occur. The network interface is configured within OMV to get its IP (v4) address from DHCP


    The problem seemed to start following a recent 6.x update but I can't now be sure which one. As I mentioned above, this problem only affects one of my two machines and I tend to update them both at the same time so I would have expected both to be affected but that is not the case.


    After boot/resume, my network config looks like:


    root@cmhomenas1:~# ip a

    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

    valid_lft forever preferred_lft forever

    2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

    link/ether d0:50:99:ab:4b:ad brd ff:ff:ff:ff:ff:ff

    3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

    link/ether 2c:6e:85:11:21:be brd ff:ff:ff:ff:ff:ff

    4: veth4a8de2a5@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default

    link/ether 3a:27:54:83:7d:0e brd ff:ff:ff:ff:ff:ff link-netns cni-1fabaa5b-b763-979e-f90d-00228b4445fd

    inet 172.16.16.1/32 scope global veth4a8de2a5

    valid_lft forever preferred_lft forever

    inet6 fe80::3827:54ff:fe83:7d0e/64 scope link

    valid_lft forever preferred_lft forever

    5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default

    link/ether 02:42:6d:e1:7c:c3 brd ff:ff:ff:ff:ff:ff

    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0

    valid_lft forever preferred_lft forever

    inet6 fe80::42:6dff:fee1:7cc3/64 scope link

    valid_lft forever preferred_lft forever

    6: br-f39706717056: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default

    link/ether 02:42:ea:79:13:7f brd ff:ff:ff:ff:ff:ff

    inet 172.19.0.1/16 brd 172.19.255.255 scope global br-f39706717056

    valid_lft forever preferred_lft forever

    8: vethd08ebfa@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default

    link/ether 46:9d:99:15:45:08 brd ff:ff:ff:ff:ff:ff link-netnsid 1

    inet6 fe80::449d:99ff:fe15:4508/64 scope link

    valid_lft forever preferred_lft forever

    10: veth65e7816@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default

    link/ether 12:1c:35:cd:46:64 brd ff:ff:ff:ff:ff:ff link-netnsid 2

    inet6 fe80::101c:35ff:fecd:4664/64 scope link

    valid_lft forever preferred_lft forever

    12: veth9a2c3e9@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default

    link/ether ae:52:dc:ba:7f:2b brd ff:ff:ff:ff:ff:ff link-netnsid 3

    inet6 fe80::ac52:dcff:feba:7f2b/64 scope link

    valid_lft forever preferred_lft forever

    14: veth8a74d9f@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default

    link/ether b2:81:f2:1b:ef:84 brd ff:ff:ff:ff:ff:ff link-netnsid 4

    inet6 fe80::b081:f2ff:fe1b:ef84/64 scope link

    valid_lft forever preferred_lft forever


    After running omv-firstaid my network config then looks like:


    root@cmhomenas1:~# ip a

    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

    valid_lft forever preferred_lft forever

    2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

    link/ether d0:50:99:ab:4b:ad brd ff:ff:ff:ff:ff:ff

    inet 192.168.86.250/24 brd 192.168.86.255 scope global dynamic enp3s0

    valid_lft 85252sec preferred_lft 85252sec

    3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

    link/ether 2c:6e:85:11:21:be brd ff:ff:ff:ff:ff:ff

    4: veth4a8de2a5@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default

    link/ether 3a:27:54:83:7d:0e brd ff:ff:ff:ff:ff:ff link-netns cni-1fabaa5b-b763-979e-f90d-00228b4445fd

    inet 172.16.16.1/32 scope global veth4a8de2a5

    valid_lft forever preferred_lft forever

    inet6 fe80::3827:54ff:fe83:7d0e/64 scope link

    valid_lft forever preferred_lft forever

    5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default

    link/ether 02:42:6d:e1:7c:c3 brd ff:ff:ff:ff:ff:ff

    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0

    valid_lft forever preferred_lft forever

    inet6 fe80::42:6dff:fee1:7cc3/64 scope link

    valid_lft forever preferred_lft forever

    6: br-f39706717056: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default

    link/ether 02:42:ea:79:13:7f brd ff:ff:ff:ff:ff:ff

    inet 172.19.0.1/16 brd 172.19.255.255 scope global br-f39706717056

    valid_lft forever preferred_lft forever

    8: vethd08ebfa@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default

    link/ether 46:9d:99:15:45:08 brd ff:ff:ff:ff:ff:ff link-netnsid 1

    inet6 fe80::449d:99ff:fe15:4508/64 scope link

    valid_lft forever preferred_lft forever

    10: veth65e7816@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default

    link/ether 12:1c:35:cd:46:64 brd ff:ff:ff:ff:ff:ff link-netnsid 2

    inet6 fe80::101c:35ff:fecd:4664/64 scope link

    valid_lft forever preferred_lft forever

    12: veth9a2c3e9@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default

    link/ether ae:52:dc:ba:7f:2b brd ff:ff:ff:ff:ff:ff link-netnsid 3

    inet6 fe80::ac52:dcff:feba:7f2b/64 scope link

    valid_lft forever preferred_lft forever

    14: veth8a74d9f@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default

    link/ether b2:81:f2:1b:ef:84 brd ff:ff:ff:ff:ff:ff link-netnsid 4

    inet6 fe80::b081:f2ff:fe1b:ef84/64 scope link

    valid_lft forever preferred_lft forever



    Can anybody offer an explanation / fix please ?


    Thanks


    Chris


    • Official Post

    If, as you say, they are two identical and updated machines at the same time, it doesn't make much sense to think of a software bug. So I would look for the reason in the hardware. Perhaps a simple cable or connection in poor condition. Or the motherboard that starts to fail.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login