Wireguard suddenly refuses to handshake
-
@xxgbhxx I may have too also. I can't keep wrestling with this. I've wasted endless time trying to find out what's wrong, only to find out it's a bad implementation of the WireGuard package. I was running myself crazy, wondering if it was some problem with my ISP, or some arcane config setting. Unbelievable.
-
@n3ivi0 guess that's why it is marked EXPERIMENTAL :-)
-
This post is deleted! -
@sly1337 Wireguard on FreeBSD has been an unmitigated disaster but at least it's going to be kernel native for v14 and written in conjunction with JD.
But we need to remember the absolutely dire implementation that led to that situation that had been funded by Netgate and then grossly mismanaged. So much so it led to a very public argument between the author of Wireshark and Netgate.
We shouldn't be surprised almost 2 years later it's still in a shambles really.
-
This post is deleted! -
@xxgbhxx v14 of which? FreeBSD, got it.
-
@sly1337 Yeah. But more experimental in the "breaks out of the dungeon in your mountain lair, rampages through the village" kind of experimental. I just wish it worked. My pfSense box is configured perfect. I'd hate to have to go to Opnsense just to get a working implementation of Wireguard.
-
I think I found the solution for 0.1.6_2. Once your tunnel is setup with peers, you have your tun_wg0 Interface, and the Mullvad Gateway has been created, you have to temporarily switch Default Gateway over to the WAN. If you do this, the handshake will complete. I don't know why this works. I have tried switching to multiple peers. Each time, set Default Gateway to WAN, let the handshake complete, then switch it back to Mullvad Gateway and you're good to go. If anybody has any notion of what is causing this, speak up. I have a basic setup, like the Netgate website recommends. Nothing fancy. Basic firewall outbound NAT and rules.
-
@n3ivi0 said in Wireguard suddenly refuses to handshake:
Each time, set Default Gateway to WAN, let the handshake complete, then switch it back to Mullvad Gateway and you're good to go.
It is warned about almost everywhere that you shouldn't make WG the default gateway, never. Make your WAN the default gateway and then use policy based routing for actually routing stuff to the WG gateway.
-
@bob-dig Thank you. That was indeed the problem. I got some bad guidance from another guide. I went back and doublechecked the Mullvad guide for pfSense: https://mullvad.net/en/help/pfsense-with-wireguard/
It has recently been updated. And that's what they recommended to do. Fixed my firewall, and I'm back in black.
Thanks again for the tip.
-
Went months without issue then would drop the connection and wouldn't reconnect. I rebooted the pfSense and the MT-1300 and no luck. I rebuilt the VPN's on both sides, changed keys and no luck. Sometimes I'd wait a couple hours and it would connect again for a few hours or as long as 20 hours.
I changed the port to 51281 on both sides and it's been up for 2 days.
