OMV and docker cannot reach vlan

    Hello,


    OMV is running on a NAS which has IP 192.168.178.57. On OMV is running docker with different container.


    I have a openwrt-router for managing VLANs: 192.168.178.64 → 192.168.1.1
    One of the VLAN-Networks is 105 with IP 192.168.105.1/24.


    Since an update in OMV on 04/12/2024 no container can reach any device in a VLAN. Before it works.


    There are static routes in main-router (fritz box) with IP 192.168.178.1:

    192.168.1.0 → 192.168.178.64

    192.168.105.0 → 192.168.178.64


    On a raspberrypi with IP192.168.178.33 PI-Hole is running and set in the main router as DNS-server.


    From any computer in the main network 192.168.178.x the target ip 192.168.105.161 is reachable.


    Now I found, that OMV itself cannot reach a device in a VLAN:

    Code
    curl -v -i -k 192.168.105.161
*   Trying 192.168.105.161:80...
* connect to 192.168.105.161 port 80 failed: Keine Route zum Zielrechner
* Failed to connect to 192.168.105.161 port 80: Keine Route zum Zielrechner
* Closing connection 0
curl: (7) Failed to connect to 192.168.105.161 port 80: Keine Route zum Zielrechner

    Here is the result of "resolvectl status" on the OMV-NAS:

    Has anybody an idea, whrere the problem is?


    Thanks in advance


    Matthias


    I found a solution here: Where to add static route ?.


    I add the configuration "/etc/netplan/30-openmediavault-enp3s0-route-openwrt.yaml" and put the same static routes inside, I store in the main router:



    Now I can reach the VLAN devices from OMV and from the container.


    I don't know, if that is a good solution or if there is a way to use the static routes from main router. But it works for me.


    Matthias

Jetzt mitmachen!

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

Benutzerkonto erstellen Anmelden