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

    Can't create Static Route to Wireguard peer subnet

    Scheduled Pinned Locked Moved WireGuard
    3 Posts 1 Posters 443 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.
    • V
      vasily
      last edited by

      This post is deleted!
      V 1 Reply Last reply Reply Quote 0
      • V
        vasily @vasily
        last edited by

        Turns out I forgot to check "Enable" on the Wireguard interface from this section https://docs.netgate.com/pfsense/en/latest/recipes/wireguard-s2s.html#assign-interface

        Once it was enabled I didn't get that error when creating the static route. Now my LAN behind the pfSense can ping both the Wireguard subnet and the peer subnet. I can't ping the subnet behind pfSense from the peer yet however. Hopefully will figure that out soon.

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

          Turns out I had missed yet another piece of the tutorial. It asked to set interface group membership to only unassigned tunnels and then says to apply the firewall rule to the individual interfaces not the WireGuard interface group. I had set them to not be in the group but then still set my allow all rule on the group and not the individual interface! Once I fixed that error everything seems to be talking as it should. Hopefully my stupidity helps someone else googling the same problem years from now.

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