OPNsense Forum

English Forums => Virtual private networks => Topic started by: smithberry on September 30, 2020, 12:00:14 PM

Title: Wireguard - Problems with LAN access
Post by: smithberry on September 30, 2020, 12:00:14 PM
Hi guys,

I've been trying to get my Wireguard VPN to work the way I want it to for a long time now. Maybe I understand something wrong.

I have a roadwarrior scenario, which means that I have an OPNsense firewall where Wireguard runs as plugin. Behind the OPNsense is a network with a Windows Server 2019 and several Windows clients.

The network is structured as follows:
Fritzbox with IP 10.15.0.1 to WAN of the OPNsense firewall (IP 10.15.0.2). The Fritzbox is also used for DynDNS (MyFritz), because of the DS-Lite problem. I then use Wireguard through a socat tunnel installed on a vServer.
The OPNsense is set as Exposed Host in the Fritzbox. Everything works fine so far.

The LAN is in the address range 10.15.1.0/24. The IP addresses are assigned via DHCP, except for the Windows server and a Windows client. The Windows Server has 10.15.1.10 and the Windows Client has 10.15.1.11.

DHCP Server is a PiHole with the address 10.15.1.2. The names of the Windows Client and the Windows Server are entered there, so that the name resolution in the LAN works. This is also no problem.

The tunnel network is in the range 10.0.0.0/24.

Now my 2 problems:

I find dozens of HowTos but my problems are not solved. Is my way of thinking wrong, or am I going about things the wrong way, or are my WireguardVPN requirements abnormal?

Title: Re: Wireguard - Problems with LAN access
Post by: Scanline on October 01, 2020, 10:11:45 PM
Hi,

I'm just a hobby user, so keep that in mind when you read my answer :)

Do you have CGNAT, or what is the deal with your VPS?

1.) That's not really a problem of opnsense I am afraid. What you could do is NAT between the two networks, but that should be avoided if possible. Putting both on the same network (bridging) is also possible, but you probably get some unwanted overhead traffic through your wireguard interface.

2.) I don't understand that point. What name resolution doesn't work? You said DNS requests are answered by PiHole, but not resolved?

So far I don't see anything specific to wireguard.