new lan card installed, all good but no internet in containers

  • happy new year everyone!


    as in the title ,installed a new lan card, all good but no internet in any of my 2 containers. (plex and syncthing)

    kvm was also effected, but i could fix it by changing the kvm network bridge to the new lan-name (enp2s0).


    i thought this would be happening, so i disabled the old lan in the bios first, then installed the card....... thinking it would keep the old name.....but no it couldn't be that easy.....

    opened omv-firstaid and changed to the new network.


    fiddling around, i found that even when the containers are running, docker0 is down.


    ip route outputs this:


    default via 192.168.1.1 dev enp2s0 onlink

    10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown

    172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown

    172.18.0.0/16 dev br-64436848859d proto kernel scope link src 172.18.0.1

    192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.64


    the network in compose has bridge, host , none , and "syncthing_default" which is created by itself every time the container runs.

    the network in omv has just the new network with it's new name (enp2s0). same as before with another name.(eno1 i think)

  • the main network should be bridged if you are using KMV.

    Plugins - compose, cputemp, omv-extras, sharerootfs.

    Drives - 1tb nvme Data, 2TB nvme Leeching, 24TB (8tbx 3 merg) Media,

    Docker - nginx-proxy-manager, plex, prowlarr, qbittorrentvpn, radarr, sonarr, watchtower.

  • I had used this after a hardware's change:


    Locate and delete the file called local-kv.db (make a backup first) inside /var/lib/docker/network/files/

    Restart the docker's service

    Delete and re-deploy all containers

    Done.

  • chente

    Hat das Label gelöst hinzugefügt.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!