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

    WG "full tunnel" (0.0.0.0/0) Not working. Local access works, but cannot get to wan addresses

    Scheduled Pinned Locked Moved WireGuard
    5 Posts 2 Posters 372 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.
    • L
      LVLAaron 0
      last edited by

      https://docs.netgate.com/pfsense/en/latest/recipes/wireguard-ra.html

      I have followed this and have 3 clients connected.

      When using allowed IP's (192.168.2.0/24, 10.3.2.0/24 - My local subnet, and wg subnet) I can get to my network devices just fine.

      If I change my clients allowed IP's to 0.0.0.0/0 - I can still get to my local devices, but I cannot get to any WAN addresses.

      Running latest OS

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @LVLAaron 0
        last edited by

        @LVLAaron-0 said in WG "full tunnel" (0.0.0.0/0) Not working. Local access works, but cannot get to wan addresses:

        If I change my clients allowed IP's to 0.0.0.0/0 - I can still get to my local devices, but I cannot get to any WAN addresses.

        Then the whole upstream traffic is directed to the remote site.
        So you need an outbound NAT rule for this traffic at the remote WAN interface to masquerade it.

        L 1 Reply Last reply Reply Quote 0
        • L
          LVLAaron 0 @viragomann
          last edited by

          @viragomann

          8a4fb048-48f5-4f6e-b7bc-71e8d2ab9d88-image.png

          Here's the NAT I have... same problem... Suggestions?

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @LVLAaron 0
            last edited by

            @LVLAaron-0
            The destination has to be "any".
            "WAN subnets" is only the subnet of your WAN IP.

            L 1 Reply Last reply Reply Quote 0
            • L
              LVLAaron 0 @viragomann
              last edited by

              @viragomann

              I got it. The "WireGuard Networks" alias wasn't defined/working... Changed it to the address of my WG network and things are working. Thanks!

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