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

    Wireguard and interfaces

    Scheduled Pinned Locked Moved WireGuard
    11 Posts 5 Posters 1.3k 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.
    • KOMK
      KOM
      last edited by

      I'm playing with Wireguard and trying to see if I can replace a road-warrior OpenVPN config with Wireguard. So far, not much luck and no logging.

      One thing that confuses me is that both docs and some videos I've watched recommend that you create an interface for your Wireguard tunnel. When I create a tunnel, a WireGuard tab appears in the Rules page. If I then create an interface and link it to the tunnel, I end up with two WireGuard tabs in Rules.

      Is this normal?

      cmcdonaldC D 2 Replies Last reply Reply Quote 0
      • cmcdonaldC
        cmcdonald Netgate Developer @KOM
        last edited by

        @kom can you post a screenshot?

        Need help fast? https://www.netgate.com/support

        KOMK 1 Reply Last reply Reply Quote 0
        • KOMK
          KOM @cmcdonald
          last edited by

          @vbman213

          Here I have just created a tunnel. Note that Rules now has a WireGuard tab.
          pfwg1.png

          Here I am assigning the wg0 tunnel to OPT1
          pfwg2.png

          Here I have enabled the OPT1 interface and renamed it to WIREGUARD
          pfwg3.png

          I now have two Wireguard tabs under Rules
          pfwg4.png

          dotdashD 1 Reply Last reply Reply Quote 0
          • dotdashD
            dotdash @KOM
            last edited by

            @kom said in Wireguard and interfaces:

            I now have two Wireguard tabs under Rules

            One is for WireGuard, generally. Like the OpenVPN and IPSec tabs.
            The other is for the interface you created. To avoid confusion, I'd call the interface something else. Like roadwg.

            KOMK chudakC 2 Replies Last reply Reply Quote 0
            • KOMK
              KOM @dotdash
              last edited by KOM

              @dotdash Strange that I haven't seen these dual-tabs in any of the guides or videos I've seen. Oh well, whatever. It doesn't matter now since I couldn't get the Wireguard site to site link working and we already have a good OpenVPN config.

              1 Reply Last reply Reply Quote 0
              • D
                dma_pf @KOM
                last edited by

                @kom said in Wireguard and interfaces:

                I end up with two WireGuard tabs in Rules.
                Is this normal?

                Yes this would be expected. See this post: https://forum.netgate.com/topic/161601/purpose-of-wireguard-tab-and-wg0

                This might help you in setting up the road warrior tunnel: https://docs.netgate.com/pfsense/en/latest/recipes/wireguard-ra.html text

                1 Reply Last reply Reply Quote 0
                • chudakC
                  chudak @dotdash
                  last edited by

                  @dotdash

                  I never assigned an interface for OpenVPN

                  What if you don't assign one for Wireguard? What will you miss out ?

                  Thx

                  cmcdonaldC 1 Reply Last reply Reply Quote 0
                  • cmcdonaldC
                    cmcdonald Netgate Developer @chudak
                    last edited by

                    @chudak generally if you’re running a routed site to site tunnel, you’d want to assign interfaces on both ends so you can do gateway monitoring across the tunnel, policy based routing, etc. if you’re setting up WireGuard for remote access, it really doesn’t make much sense to define an interface.

                    Need help fast? https://www.netgate.com/support

                    chudakC 1 Reply Last reply Reply Quote 2
                    • chudakC
                      chudak @cmcdonald
                      last edited by

                      @rcmcdonald91

                      Thank you !

                      KOMK 1 Reply Last reply Reply Quote 0
                      • KOMK
                        KOM @chudak
                        last edited by

                        @chudak I think I read somewhere here that the default Wireguard tab allows you to define rules that are global across all defined wg tunnels, where the interfaces allow you to define rules for just that specific tunnel that's linked to the interface.

                        KOMK 1 Reply Last reply Reply Quote 1
                        • KOMK
                          KOM @KOM
                          last edited by

                          I finally got it working. I wanted a road warrior config between my home pfSense and work. It took me awhile to realize that, while you don't need to define an interface on the work (server) side, you do on the home (client) side plus the usual firewall rule and outbound NAT rule to direct the traffic out the wireguard interface.

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