Using Wireguard to access my OMV share drives

I've been using OMV for several years now and had previously used Wireguard successfully to access my share drives. I believe this was on v5 and using Wireguard in docker? I honestly can't remember as it has been a few years. I was able to access my shared drives on Windows, Android, and OSX.

Fast forward to today and I'm on v6 (current SysInf says 6..9.16-1) and am using the Wireguard plugin. I set up a simple, as is, Tunnel and Client with no extra options/modifications. I added the Client to my Android tablet using the QR code and created a .conf file to set up my OSX laptop. Both of these are able to connect to my server remotely (I've tested on my neighbor's wifi, a public wifi, and my phone as a hotspot) and am able to connect on both devices in all cases. However, once connected, I can't use any of my docker containers or see any of my share drives - not even the main OMV interface.

I've read through the forums on this as well as reddit and tried a few things around AllowedIPs and custom configs but I'm flying pretty blind there. None of this seemed to make a difference. I'm not 100% sure what I can post from the config file without sharing sensitive info but I can say that only 2 lines seem to be specific to my setup outside of the keys and the endpoint (currently served by netgear's dynamic DNS that I use to access several containers remotely like Jellyfin) are:

Address = looks like an internal address x.192.x.x/24

and AllowedIPs = 0.0.0.0/0

Any help here would be much appreciated!

Got it - I knew I was behind on the upgrade but everything had been running so smoothly I wasn't quite ready to roll those dice yet. I'm upgrading now following this:

Post

RE: Is there a guide to in place upgrade?

Contributions wanted:

1. Backup the OS drive (this is allways a good idea, not only for upgrades)
2. Make sure, you have enough free space on your os drive
3. Check any installed plugins if they have been ported to OMV6
   If you are using plugins which have not been / will not be ported, get rid of the plugins except unionfs / mergefolderfs. These two will automatically be be converted to the newer mergerfs plugin
   (Many plugins can be replaced by docker containers. Do this before upgrading)
4. If you installed

…

Zoki

Mar 8th 2022

OK, upgrade went through without a hitch - even my snapraid config carried over which is great! All my containers seem to be up and running and all my SMB shares are there for all the other random stuff around my house that uses them. Yay!

But I still can't get my wireguard config to work - seems like the same issue. I've tried both my android tablet and my macbook. Both connect to through wireguard just fine but I can't get any containers to work nor can I see the SMB shares. Boo. Any thoughts? Can I check anything on my clients or any logs on the server or anything?

Same tunnel and client for both - no changes made from default outside of naming them.

Also, though I tried using the server name initially I didn't expect it to work as I had read about a few DNS issues without some changes from default. So I tried everything through the server's IP - 192.168.1.200.

OK - created a separate client for the laptop as well as making sure the tablet wasn't connected but still no dice.

I also read some random thread about adding the server's specific IP to AllowedIPs which seems silly to do give the 0.0.0.0/0 but it supposedly worked for this guy. It did not work for me.

OK, now we're getting somewhere!

So rx is showing 0 B while tx slowly climbs a KiB at a time which explains why I can't see anything, not even the OMV gui.

I'm currently using a netgear DDNS at x.mynetgear.com which I've checked and is resolving correctly to my google fiber assigned IP for my house. (followed the instructions here - https://wiki.omv-extras.org/do…v7:omv7_plugins:wireguard). I have a netgear Orbi router and have the 51820 port forwarded to my OMV server. All my other forwarded ports are working correctly.

Yeah, those match and services like jellyfin are working great.

I also checked to make sure I was using the right network interface on the server side and am using the only one listed at Network>Interfaces.

OK, added those to DNS for my tablet - couldn't figure out how to save it client side so I just deleted the config, added it in the OMV interface, then re-added with the QR code. Unfortunately no change.

Sorry, yes - android tablet (samsung).

But good news - I fixed it! I was double checking my router config and noticed the port forwarding was set to both TDP and UDP on 51820. On a whim I changed it to UDP only and amazingly it worked!

Tablet working fine, all containers and SMB shares. OSX laptop can't see the SMB shares yet through finder but I'm messing with that.

Actually I just got that working as well, likely due to adding that DNS? I had to manually connect to the server vs just finding it in the network section but all appears to be working now.

I guess the TDP/UDP dual router port forward was defaulting to TDP or something? Never had an issue with that before but glad we cracked the code on this setup.

Thank you for all your help!