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

    Wireguard not starting

    Scheduled Pinned Locked Moved WireGuard
    12 Posts 2 Posters 845 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
      LaUs3r @fabianorbatista
      last edited by

      @fabianorbatista , I suggest you provide more information. With that no one will be able to help you.
      I shared my experience some days ago in a sort of guide I put here in the forum. Maybe this helps you.

      1 Reply Last reply Reply Quote 0
      • F
        fabianorbatista
        last edited by

        Hello
        What more information do you need?

        1 Reply Last reply Reply Quote 0
        • F
          fabianorbatista
          last edited by

          I followed the manual you created step by step and still the service does not start and does not generate error logs.

          L 1 Reply Last reply Reply Quote 0
          • L
            LaUs3r @fabianorbatista
            last edited by LaUs3r

            @fabianorbatista , let's start with the problem statement:
            Does Wireguard package not install, the service not start or the handshake not happen?

            If you want help, please provide more info.
            And pfSense does generate logs: depending on the issue, you just need to look at the right spot.
            Start with Status > system logs

            In addition, at what step did the guide not work?

            1 Reply Last reply Reply Quote 0
            • F
              fabianorbatista
              last edited by

              As described in my first message, the service does not start, listing the socket looks like the image above, as if something was listening on the port but it does not show the Wireguard service, the only error log I got was this one from the gateway like the print above. When I leave the WAN with the none option in IPv6, this gateway error disappears.

              L 1 Reply Last reply Reply Quote 0
              • L
                LaUs3r @fabianorbatista
                last edited by LaUs3r

                What gives you

                sudo netstat -nlp | grep :51820
                

                or

                sudo lsof -n -i :51820 | grep LISTEN
                

                Can you post a screenshot of your interfaces and NAT outbound rules?
                I assume that you are using ipv4 for the wireguard tunnel right?
                Also, the current wireguard version is 0.2.9 and not 0.2.1. Can you confirm that you have the latest version?

                1 Reply Last reply Reply Quote 0
                • F
                  fabianorbatista
                  last edited by

                  The netstat -nlp | grep command: 51820 the p parameter requires more arguments as shown in the print below
                  5fe1ec90-d5d2-4620-9e84-2a6122809d90-image.png

                  d4ffd2df-a2c4-49c1-9e98-87c075f30b8e-image.png

                  The lsof command does not exist in pfsense
                  7ad60257-cfeb-4673-ac48-fdbcb256bb4b-image.png

                  I assume that you are using ipv4 for the wireguard tunnel right?
                  Yes

                  The wireguard version installed on my pfsense is not yet updated
                  535a4885-9798-463c-a4fd-ccfa06fe38c2-image.png

                  L 1 Reply Last reply Reply Quote 0
                  • L
                    LaUs3r @fabianorbatista
                    last edited by

                    ok. so I just checked with my pfSense and I don't see any info with the netstat command (just like you).
                    What I see in Diagnostics > Sockets is the same info as in your 1 screenshot:

                    8b740de0-3350-4ef1-88c2-66793c4decbf-image.png

                    Can you please try the following:

                    1. verify in VPN > WireGuard > Settings that "Enable is checked

                    c1b5a656-f4cf-410c-8932-744b375e6b93-image.png

                    1. verify that you have assigned an interface to the network port in Interfaces > Interface Assignments

                    ef4d242f-8cc9-4915-a352-9eb9e7bb1017-image.png

                    As for the wireguard package version. I just realized that the version is different on my pfSense Plus. Regulard pfSense has 0.2.1 meaning yours is up-to-date.

                    I also found some posts where users reported that removing the wireguard package WITHOUT keeping the configuration and then reinstall the package, did the trick.

                    b636a67a-fef8-449c-bc8e-5899e8c4dd44-image.png
                    --> "Keep Configuration" needs to be unckecked

                    1 Reply Last reply Reply Quote 0
                    • F
                      fabianorbatista
                      last edited by

                      Sorry for the delay in the information below.

                      4d5e3825-4dd1-401b-a31a-31f09178c056-image.png

                      Yes, it is marked to enable
                      2860835c-f312-450e-a9be-5271009d2f4d-image.png

                      I have already reinstalled Wireguard with the "Keep Configuration" option disabled and the problem persists

                      1 Reply Last reply Reply Quote 0
                      • F
                        fabianorbatista
                        last edited by

                        The interface is Assignments
                        189523b0-5297-4078-891f-d751287352fa-image.png

                        L 1 Reply Last reply Reply Quote 0
                        • L
                          LaUs3r @fabianorbatista
                          last edited by LaUs3r

                          ok, maybe let's take a step back. You wrote that it works once you disable IPv6 in your WAN interface.

                          Are you using IPv6 at all? If yes, have you configure IPv6 for your wireguard tunnel?

                          Maybe it's worth checking out the video from Chris McDonald: https://www.youtube.com/watch?v=wYe7FzZ_0X8
                          Chris is the maintainer of the wireguard package for pfSense. In this video he shows the config for a wireguard tunnel for IPv4 AND IPv6

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