<![CDATA[Connecting From LAN to VPN Clients]]>I have a number of offsite devices that can connect to the VPN without problems (Tun)

They each get an address from the pool 192.168.100.0/24

My lan has the pool 192.168.10.0/24

My remote devices and see the LAN network without any problems.

On occasion we need to change the devices configuration done via a web browser.

If we ping the VPN Client we get no route to host.
But the VPN Client can ping us.

Basically VPN to Lan is good.
LAN to VPN is bad.

I’m thinking I need a outbound nat route.
This is new to me and I know just enough to be dangerous

]]>https://forum.netgate.com/topic/140324/connecting-from-lan-to-vpn-clientsRSS for NodeSun, 15 Mar 2026 01:42:36 GMTTue, 05 Feb 2019 18:22:40 GMT60<![CDATA[Reply to Connecting From LAN to VPN Clients on Tue, 05 Feb 2019 19:00:40 GMT]]>Routing table is empty.
I’ll try and grab some screenshot.
Config and firewall is just from the wizard.

]]>https://forum.netgate.com/post/822446https://forum.netgate.com/post/822446Tue, 05 Feb 2019 19:00:40 GMT<![CDATA[Reply to Connecting From LAN to VPN Clients on Tue, 05 Feb 2019 18:52:47 GMT]]>No you don't need any NAT.
Show your config, routing table and firewall rules.
Your LAN devices use pfSense as gateway?

-Rico

]]>https://forum.netgate.com/post/822439https://forum.netgate.com/post/822439Tue, 05 Feb 2019 18:52:47 GMT