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

    Pfsense Wireguard to VPS - No handshake

    Scheduled Pinned Locked Moved WireGuard
    4 Posts 2 Posters 894 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.
    • O
      Owen82
      last edited by

      Hi All, I need some help to get a wireguard tunnel to a cloud server. I have followed several different guides but I never get a handshake. I have unticked the "save configuration" option and removed & installed the Wireguard package between guides.

      no handshake.png

      I do not anything helpful in Status>System Logs>System>General

      I have given set a specific interface and given it the same static ip as assigned by the 'server' for the client (10.13.13.2)

      I have the following FW rules:
      Wireguard default Int:
      Firewall_ Rules_ WireGuard.png

      Dedicated WG_VPN Int:
      Firewall_ Rules_ WG_VPN.png

      I can connect with android phone using the Wireguard app without any problems, so I'm pretty certain it's my pfsense config. I've run out of ideas - can anyone help?

      Bob.DigB 1 Reply Last reply Reply Quote 0
      • Bob.DigB
        Bob.Dig LAYER 8 @Owen82
        last edited by Bob.Dig

        @Owen82 Allowed IPs have to include the other side (peer).
        MTU looks not optimal.

        O 1 Reply Last reply Reply Quote 0
        • O
          Owen82 @Bob.Dig
          last edited by

          @Bob-Dig Thanks for taking the time to try to help, I tried adding the peer subnet, still no handshake and then tried just adding 10.13.13.1/32 - no dice.

          I had heard that the tunnel will only be created if there is traffic for it, is that true? I tried a ping to 10.13.13.1 just in case (failed).

          I tried again with a ping whilst doing a packet capture on the WG_VPN Int and there was no traffic at all, no sure what's going on.

          Does it matter that there is no route for the 10.13.13.1 address? Is this somehow handled internally with WG?
          5f0b636d-1fd9-4fff-a8bb-c299f39793a6-image.png

          Bob.DigB 1 Reply Last reply Reply Quote 0
          • Bob.DigB
            Bob.Dig LAYER 8 @Owen82
            last edited by Bob.Dig

            @Owen82 They both should be in it.

            Remove any rules you have except allow anything for testing. And set keep alive with 25 seconds for testing. Set a port in the VPS as well.

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