Wireguard Plugin settings no longer working in OMV7

  • Hi - my Wireguards settings from OMV6 are no lnger working in OMV7.


    It used to be super simple to setup Wireguard for split traffic. All I had to do is tick Restrict on Server side and add my relevant Remote Network range to the WG-Client profile and it worked.


    With OMV7 I cannot get the same setup to work with Wireguard.

    To even reach the WG-Network client at all I need to amend the Client-Profile to include the Local (!) (not the Remote) network range. Still I cannot in any configuration reach the other Local hosts.


    I tried every configuration option in the OMV Plugin. Maybe anyone has some ideas?


    Here is my configuration:


    Remote Client_E1 on 192.168.1.0/24 ----INTERNET---[local network: 192.168.9.0/24 Wireguard Server_Host 1------Host 2----Host 3]


    I want to be able to connect via SSH and Webbrowser from E1 to Host1 and all hosts on the local network (Host 2 and Host 3)

    OMV6 settings is simple:

    Server: Restric [X]

    Client profile: Allowed IPs: 192.168.1.0/24

    -> worked fine


    OMV7 settings :

    I cannot access any hosts on the local network, other than the wireguard host itself.


    I tried the following settings:


    1)

    Server side:

    Restrict [X]

    Restrict routing to VPN subnet only [ ]

    Restrict routing to Local subnet only [ ]


    WG Client profile: Allowed IPs: 192.168.1.0/24 (this setting used to work in OMV6)

    -> no server is reachable at all


    2)

    Server side:

    Restric [X]

    Restrict routing to VPN subnet only [X}

    Restrict routing to Local subnet only [ ]


    WG Client profile: Allowed IPs: 192.168.9.0/24

    -> only the Wireguard server is reachable but no other host in the destination network is reachable


    3)

    Server side:

    Restric [X]

    Restrict routing to VPN subnet only [X]

    Restrict routing to Local subnet only [X]


    WG Client profile: Allowed IPs: 192.168.9.0/24

    -> only the Wireguard server is reachable but no other host in the destination network is reachable


    4)

    Server side:

    Restric [ ]

    Restrict routing to VPN subnet only [ ]

    Restrict routing to Local subnet only [ ]


    WG Client profile: Allowed IPs: 192.168.9.0/24

    -> only the Wireguard server is reachable but no other host in the destination network is reachable

    OMV6 HP t630

    OMV6 Xeon / i5 - SCSI PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD)

    • Official Post

    Upgrading from OMV6 to OMV7 sometimes modifies the network interface name. That could break the Wireguard configuration coming from OMV6. Check if the network interface you have configured in the Wireguard tunnel matches the server's network interface in the Network>Interfaces tab.

  • Thanks Chente - that fixed the issue.

    Strange - no device was assigned to Wireguard but I could still connect, just no traffic was going through.

    OMV6 HP t630

    OMV6 Xeon / i5 - SCSI PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD)

    • Official Post

    Thanks Chente - that fixed the issue.

    Strange - no device was assigned to Wireguard but I could still connect, just no traffic was going through.

    The client may show that it has established the tunnel, but that does not mean that there is communication with the server.


    I'm glad you solved it.

  • chente

    Added the Label resolved

Participate now!

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