Jump to content
Not connected, Your IP: 216.73.216.108
rEpymK0hWF

pfSense WireGuard + AirVPN: tunnel comes up but no handshake (keys correct)

Recommended Posts

I’m trying to set up an AirVPN WireGuard tunnel on pfSense, but I cannot get a handshake, despite the configuration appearing correct.

Environment

  • pfSense (current release)
  • WireGuard package installed
  • Existing WireGuard tunnel with another provider works correctly (so pfSense + WG itself is functional)

What I’ve done
  • Generated the WireGuard configuration using AirVPN’s Config Generator
  • Created the WireGuard tunnel in pfSense using the provided:
        Private key
        Interface address (/32 as given)
        DNS (also tested without relying on tunnel DNS)
  • Added the peer with:
Correct public key
Endpoint IP and port from AirVPN
Allowed IPs as provided by AirVPN
  • Assigned the WireGuard interface
  • Created firewall rules allowing outbound traffic
  • NAT configured as expected (same approach as my working WG tunnel)

Symptoms
  • Tunnel shows as up
  • No handshake occurs
  • No RX/TX traffic on the WireGuard status page
  • Keys definitely match (regenerated multiple times)
  • Interface address added (though handshake should occur even without it)

What makes this confusing
  • Another WireGuard provider works perfectly on the same pfSense box
  • Same WAN, same firewall/NAT logic
  • AirVPN’s UI no longer shows the older “Devices → WireGuard” workflow, only the config generator
  • The same AirVPN config works when tested with wg-quick on Linux

What I’m wondering
  • Is there anything AirVPN-specific that pfSense requires (MTU, keepalive, endpoint handling)?
  • Any known issues with AirVPN WireGuard peers and pfSense?
  • Does AirVPN require a specific Allowed IPs or gateway configuration that differs from other providers?

If anyone has AirVPN + WireGuard working on pfSense, I’d really appreciate insight into what I might be missing.

Thank you for reading my post. 

Share this post


Link to post

The other provider you use listens for connections on what port?  Personally I've had ISPs that block wireguard on the ports that AirVPN uses but not on port 80, for example.

Share this post


Link to post
5 hours ago, go558a83nk said:

The other provider you use listens for connections on what port?  Personally I've had ISPs that block wireguard on the ports that AirVPN uses but not on port 80, for example.


Thank you for your feedback.

I am using another VPN provider and have set up three wire-guard tunnels. It works great.

I have decided to try Air-VPN.

They all (my current VPN and Air-VPN) use similar listening ports. 

The Air-VPN tunnel peer does not handshake.  

Finally, I have been able to use Air-VPN wire-guard to connect from my Linux box without issues. The Linux box is behind the Pfsense firewall.  The problem arises when I try to implement the connection on my Pfsense firewall/router. 
 

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image

×
×
  • Create New...