OPNsense Forum

English Forums => Virtual private networks => Topic started by: sebasdt on December 11, 2023, 10:29:10 AM

Title: [self fixed] new wireguard instance not able to access lan.
Post by: sebasdt on December 11, 2023, 10:29:10 AM
Hi all,

So I've been trying to get wireguard working properly and even followed the official documentation.

My WG clients are receiving handshakes back but are not able to access any device on LAN.
weirdly enough opnsense gui can be accessed and any gateways can be pinged...
for wireguard i've enabled the interface for

In the wireguard logs, I see this:

Error  wireguard
/usr/local/opnsense/scripts/Wireguard/wg-service-control.php: The command '/sbin/route -q -n add -'inet' '10.59.59.1/24' -interface 'wg1'' returned exit code '1', the output was ''

It seems like to me opnsense isnt able to create a route to lan...


anyway here are some screenshots from the configs.
https://imgur.com/a/pFz8wze

EDIT:
Turns out! I totally forgot my internal dns was behind a VIP and in loadbalance mode, somehow Wireguard doesnt like it while on pfsense it did work.
and so didnt have dns XD what a stupid mistake...
Title: Re: [self fixed] new wireguard instance not able to access lan.
Post by: rollspulpfiction on June 15, 2024, 03:39:38 PM
Hi sebasdt,

I'm getting the same error message since updating to 24.1.8. It was not a problem in previous versions and Wireguard had been working fine since January. What did you have to do in Opnsense to fix this issue?

Thank you!