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

    No handshake via Mullvad

    Scheduled Pinned Locked Moved WireGuard
    3 Posts 1 Posters 298 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.
    • T
      TeeNetGate1
      last edited by

      I have a new 4200. I am trying to setup for a friend. I am replicating my workflow with a 3100. In that, years ago, I followed this video tutorial to not only build it but setup failover which has been very useful.

      I am using my friend's mullvad account to create the tunnels and peers but I never get a handshake. I went into the control panel to look at the config to address this concern and it shows the IP of 0.0.0.0 & ::.

      I have changed the mullvad servers multiple times. I have verifed these settings match my personal config, except for the private / public keys.

      On the 3100, the wireguard package build is 0.2.1 whereas on the 4200 it is 0.2.2_1. There are no updates for either side.

      Setting up the tunnels and peers, should just handshake before I start to route traffic right? This is a clean 4200 never used, and I have reset the device to defaults more than once, with no change to the experience.

      What is causing my mystery?

      T 1 Reply Last reply Reply Quote 0
      • T
        TeeNetGate1 @TeeNetGate1
        last edited by

        @TeeNetGate1 said in No handshake via Mullvad:

        I have a new 4200. I am trying to setup for a friend. I am replicating my workflow with a 3100. In that, years ago, I followed this video tutorial to not only build it but setup failover which has been very useful.

        I am using my friend's mullvad account to create the tunnels and peers but I never get a handshake. I went into the control panel to look at the config to address this concern and it shows the IP of 0.0.0.0 & ::.

        I have changed the mullvad servers multiple times. I have verifed these settings match my personal config, except for the private / public keys.

        On the 3100, the wireguard package build is 0.2.1 whereas on the 4200 it is 0.2.2_1. There are no updates for either side.

        Setting up the tunnels and peers, should just handshake before I start to route traffic right? This is a clean 4200 never used, and I have reset the device to defaults more than once, with no change to the experience.

        What is causing my mystery?

        I also did not do any config of this via console / cli, all was done via the Gui.

        T 1 Reply Last reply Reply Quote 0
        • T
          TeeNetGate1 @TeeNetGate1
          last edited by

          @TeeNetGate1 Adding in more testing, from pfsense I can ping the endpoint IPv4 & v6. But still not handshake.

          I took a server I know works, from the 3100, but it does not work.

          I have added in an interface IP, which i can ping and this does not work.

          Do I have a lemon of a pfsense box?

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