Can't access LAN IP of Access Point via Wireguard connection

Started by Heiko910, November 29, 2022, 02:28:22 AM

Previous topic - Next topic
Hi there,
Thanks for having me.
I am a total noob to Opnsense and Wireguard, but i have successfully managed to setup an Opnsense router for my LAN and I established a Wireguard tunnel from an android client to my LAN.
I can access my Nas that is part of the local area network and i can even access the Opnsense router via the wireguard tunnel.
For some reason I cannot access one specific IP address in this Lan which happens to be the WebUI of my access point in the house. (192.168.1.254 in case that matters)
I have tried to ping that IP from the android device and i get a response immediately.
Does anyone have any idea why I can easily access all devices within that Subnet but i can access that AP?
Thanks in advance,
Heiko

Does this access point have a default gateway configured pointing to your OPNsense?
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

I think it does but so does my NAS.
I can access everything from a Wireguard client except this AP.


Mybe the AP will not respond to http/https (?) requests from foreign subnets. Some devices (or the desired service of those) have an option to explicity permit those requests.
i am not an expert... just trying to help...

Quote from: pmhausen on November 29, 2022, 07:52:17 AM
Does this access point have a default gateway configured pointing to your OPNsense?

Hey PMHAUSEN,
You fixed it.
You asked about the default gateway in the Access Point. I checked this morning. The default gateway was set to 0.0.0.0.
I changed it to the IP of the gateway and now I can access it via Wireguard.
Thanks again.
Problem solved!

Quote from: tiermutter on November 29, 2022, 08:32:59 AM
Mybe the AP will not respond to http/https (?) requests from foreign subnets. Some devices (or the desired service of those) have an option to explicity permit those requests.

I compared openwrt and found that this problem can be solved by setting snat
firewall - nat - outbound:
Select - Hybrid outbound NAT rule generation
Add rule - interface: lan, tcp/ip: ipv4, source address: wg net, destination address: lan net, translation/target: lan address