Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    I would love to connect, but it won't let me

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 2 Posters 343 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mms
      last edited by

      Hi,
      Simple question...

      I'm running pfsense in my office with 3 interfaces assigned:

      • WAN public fixed IP (provided by DHCP from ISP)
      • LAN 192.168.1.1
      • WG 10.200.1.1 (WireGuard tunnel)

      I have a laptop (win11) running WireGuard application to VPN connect to pfsense, that is configured to tunnel all traffic (AllowedIPs = 0.0.0.0/0).
      WireGuard application runs on start, and the tunnel is always active, so I dont forget when connecting to Wi-Fi networks.

      When I'm away, connecting to any external Wi-Fi network, it works perfectly, both the internet access, and the remote access to services on the LAN (such as a file server, and access to pfsense webconfig itself).
      However, then the laptop is on office, connected to the Wi-Fi network, getting an IP (192.168.1.73) assigned by pfsense DHCP server, only the internet access works, but I dont get access to the services on the LAN (unless if I disable the tunnel).
      Why?

      Regards, M.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        It's probably a routing conflict. The laptop has an IP and gateway in the LAN subnet and that must be routed outside the tunnel but at the same time the WG server is sending it routes to the LAN subnet via the tunnel.
        I would expect to see some routing error logged somewhere.

        Putting the WIFI on a different subnet would workaround it.

        You could also block access to the WG server from the LAN so the tunnel cannot connect when you're on that subnet.

        Steve

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.