Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Found an amazing tool for exporting WireGuard peers! (No more struggling)

    Scheduled Pinned Locked Moved WireGuard
    46 Posts 12 Posters 10.2k Views 14 Watching
    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.
    • H
      hockeyfreak @chpalmer
      last edited by hockeyfreak

      @chpalmer It wasn't there this morning either. I reinstalled with no issues. A couple of questions, if someone has time, though.

      What does this mean when it says Rep:pending?
      745e6885-74a1-4114-a33d-d6f170c83df9-image.png

      Also, I have my home IP address in the endpoint conf file, but in the status in PFSense has two wildly different IPs as the endpoint for each device. Just curious why that is? Also, I use it at work on a government network, and when I put my noip.com forwarding address in the endpoint, it doesn't work. I guess somehow they are blocking it because of the port number?
      eacff849-7992-48b4-bd51-6cd8d82008c3-image.png

      Thanks for your time!

      chpalmerC 1 Reply Last reply
      Reply Quote 0
      • chpalmerC
        chpalmer @hockeyfreak
        last edited by

        @hockeyfreak said in Found an amazing tool for exporting WireGuard peers! (No more struggling):

        I have my home IP address in the endpoint conf file, but in the status in PFSense has two wildly different IPs as the endpoint for each device. Just curious why that is? Also, I use it at work on a government network, and when I put my noip.com forwarding address in the endpoint, it doesn't work. I guess somehow they are blocking it because of the port number?

        Yes they can block it a number of ways. Every employer that Ive worked for government or not has always had a policy against such things. You might want to review your employers version.. My guess is a government agency is not going to be happy about attempts to use their network for such.

        Triggering snowflakes one by one..
        Primary- Intel(R) Pentium(R) CPU G4400 @ 3.30GHz on an M470 WG box. pfsense+ 26.07

        H 1 Reply Last reply
        Reply Quote 0
        • H
          hockeyfreak @chpalmer
          last edited by hockeyfreak

          @chpalmer It's actually a "Guest" network, so it's a lot less controlled than our employee network, which I regularly get blocked from many sites like youtube and other social media sites. I cannot use a VPN on the employee network, and they strictly control the devices that can log into it. The guest network is open, you just have to create a login from a employee networked computer and use it on the Guest network, then you can use your personal devices. I'm sure they monitor it, but I assume with a VPN like Wireguard all they can see is encrypted traffic and how much. I'm not doing anything illicet or subversive, but I still don't want them sniffing my home network or personal websites I visit.

          I guess I'm just wondering how it makes a difference if I use "example.ddns.net:51820" as opposed to "111.222.33.44:51820". Just curious.

          3um3le3ee3 1 Reply Last reply
          Reply Quote 0
          • 3um3le3ee3
            3um3le3ee @hockeyfreak
            last edited by

            @hockeyfreak Thanks, that's really good to hear, especially that it got you working after a week of fighting it.

            Tutorial / video: No, I’m not very good at that kind of thing, so hopefully someone will take up the challenge. If you have questions about a setting in the meantime, ask here and I’ll answer.

            Donations: Thanks for the offer, but please don’t worry about it. I built this to make setting up and using WireGuard as simple as possible, so that keeping your connection private isn’t a struggle. Hearing that it worked for you is thanks enough.

            Missing after the 2.9.0 upgrade: WG Suite isn't in the Netgate package repository; you install it yourself with pkg add. The upgrade only reinstalls packages from the official repo, so it drops anything installed by hand. You'll need to reinstall it after each pfSense upgrade, as you did. Your tunnels and peers live in the pfSense config, so they survive. Most of my testing has been on 2.8.1, so if anything behaves oddly on 2.9.0, let me know.

            Rep: Pending: That's the IP reputation check. When geolocation is turned on in Settings, a scheduled job looks up the address each peer is connecting from and flags it if it belongs to a known VPN, proxy, Tor exit, hosting provider and so on. "Pending" just means that address hasn't been checked yet. It changes to Clean or to the flags it found after the next run. It's informational only and doesn't block anything.

            Different endpoint IPs in Status: The two endpoints mean different things. The Endpoint in your .conf is where the device connects to, i.e. your home address. The Endpoint in pfSense's status is where the device is connecting from, i.e. its own public IP. That's your mobile carrier's address for the phone and the work network's address for the laptop. Each device shows a different one, and they change as you move between networks.

            Hostname vs IP: Once connected, there's no difference. The client looks up example.ddns.net once, gets your IP, and from then on uses the IP. So if the IP works but the hostname doesn't, it's almost certainly DNS. A lot of managed networks block dynamic-DNS domains (no-ip, DuckDNS etc.) as a category, so the lookup fails and the tunnel never starts. A quick test: on the guest network, try 111.222.33.44:51820 in place of the hostname.

            • If the IP works, the network's DNS is the problem.
            • If neither works, they're blocking outbound UDP, or that port.

            One thing to know with a raw IP: if your ISP changes your home address, the config stops working until you update it. The hostname avoids that.

            On privacy: you're mostly right. They can't see what's inside the tunnel, though they can see that you're connected to your home IP, and how much data goes through it. Same point @chpalmer made, though: if the guest network has an acceptable-use policy, worth a quick read before relying on it.

            WG Suite on GitHub

            H 1 Reply Last reply
            Reply Quote 0
            • H
              hockeyfreak @3um3le3ee
              last edited by

              @3um3le3ee Thanks for your answers!!

              1 Reply Last reply
              Reply Quote 0
              • 3um3le3ee3
                3um3le3ee
                last edited by 3um3le3ee

                WG Suite 1.3.0 is out. It’s the biggest release so far.

                What’s new

                Portal sign-in with passkeys or single sign-on. Peers can sign in with Entra ID, Google Workspace, Okta, Authentik, Keycloak or any OIDC provider, alongside TOTP.
                Device requests. Peers can ask for access on another device from their portal, and you approve or decline it.
                Self-service key replacement. The old key is only revoked once the new one has connected.
                Group policies. Bind a profile to a group and every member stays in line with it.
                Adopt and import peers. Bring existing VPN > WireGuard peers under WG Suite without reconnecting them, or import a wg0.conf from wg-easy, PiVPN or wireguard-ui.
                Configuration history. See what any config revision changed and restore it.
                Public listener. Serve only the peer-facing pages on their own port, so they can face the internet while the web interface stays on your LAN.
                Health endpoint for Uptime Kuma, Nagios and Prometheus, including a check that the HA backup matches the primary.
                Three privilege tiers: View, Peer operator and Admin.
                Searchable help for every page and option, plus translation support.

                On the security side, HA sync now pins the backup’s TLS key, secrets are sealed per node, and the WebSocket daemon runs unprivileged with per-peer tokens.

                Full changelog and docs: WG Suite on GitHub

                Tested on CE 2.8.1. Bug reports, feedback and translations are very welcome. Please use the GitHub issue forms, and report anything security-related privately as described in SECURITY.md.

                keyserK 1 Reply Last reply
                Reply Quote 0
                • keyserK
                  keyser Rebel Alliance @3um3le3ee
                  last edited by

                  @3um3le3ee This is really getting interesting. What a package you are putting together here. Keep up the good work👏
                  We just need it as an official pfSense package so It's in the official repo and gets updated automatically with pfSense updates.

                  Love the no fuss of using the official appliances :-)

                  1 Reply Last reply
                  Reply Quote 1
                  • 3um3le3ee3
                    3um3le3ee
                    last edited by

                    Hello everyone,

                    I want to apologize for the confusion with the installation instructions in the latest release. My original intention was to set up a signing key and provide a SHA256SUM to ensure everything was fully secure out of the gate.

                    However, since I'm developing and maintaining this in my spare time, I just haven't gotten around to getting all of that set up yet. I will definitely get it sorted out eventually, but time is pretty scarce at the moment.

                    To keep things working smoothly for everyone in the meantime, I've reverted the installation instructions back to the original curl terminal command.

                    Sorry for any inconvenience or confusion this caused, and thanks for your patience!

                    1 Reply Last reply
                    Reply Quote 0
                    • 3um3le3ee3
                      3um3le3ee
                      last edited by

                      @keyser Thank you so much! I really appreciate your continued support and encouragement across all these posts—it means a lot to have you cheering the project on.

                      Getting this into the official pfSense repository is definitely the ultimate goal. Having it update automatically alongside pfSense would be the ideal setup for everyone. Since I'm developing and maintaining this entirely in my spare time, I'm taking it one step at a time right now to make sure the core features are completely rock-solid first.

                      Once things are a bit more polished and I have the time to navigate the submission process, I'll definitely look into getting it upstreamed to Netgate. Thanks again for sticking with the project!

                      1 Reply Last reply
                      Reply Quote 0
                      • P
                        pfSense_fireball
                        last edited by

                        Wow, I just have to say this package has turned into something truly amazing! this really needs to be added to the official pfSense repository.

                        @3um3le3ee, you’ve made this an absolute must-have for anyone running WireGuard! 👍

                        1 Reply Last reply
                        Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better 💗

                        Register Login
                        • First post
                          Last post
                        Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
                        Privacy Policy · Cookie Policy