Show Posts
1
Virtual private networks / [self fixed] new wireguard instance not able to access lan.
« 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:
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...
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:
Code: [Select]
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...