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

    Wireguard Surfshark Dedicated Server

    Scheduled Pinned Locked Moved WireGuard
    2 Posts 2 Posters 485 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.
    • M
      mThirteen
      last edited by

      I would like to setup wireguard tunnel between my pfsense box and my dedicated server provided by surfshark and route all LAN traffic through it.
      All the information the provided is as follows:

      Use this configuration with WireGuard client

      [Interface]
      Address = x.x.x.x/16
      PrivateKey = *****************************
      DNS = xx.xxx.xx.xx, xx.xx.xx.xx
      [Peer]
      PublicKey = ************************************
      AllowedIPs = 0.0.0.0/0
      Endpoint = xx.xx.xx.xx : 51820

      I am new to both pfsense and wireguard and surfshark has not provided much help apart from the masked details above
      I have found several tutorials online (none of them specifically focused on surfshark dedicated IP) and i tried to make it work without luck.

      Any pointers ??

      JustAnotherUserJ 1 Reply Last reply Reply Quote 0
      • JustAnotherUserJ
        JustAnotherUser @mThirteen
        last edited by JustAnotherUser

        @mThirteen

        Your WG VPN may be up and running fine and you just don't know it...

        From each device: ping the far end WG tunnel IP. If you can ping the tunnel IPs, your VPN is working fine.

        If your VPN is working fine but there's still no traffic through it, it's probably because:

        1. You didn't set up the static routes.

        2. You have OpenVPN entries on your pfSense box that are interfering. The Wireguard module is a little bit broken in that OpenVPN entries (even disabled ones), mess up WG.

        I fixed this issue by deleting all of my OVPN entries.

        Others have fixed this issue by deleting the WG peers and tunnels and re-installing them.

        I highly suggest you backup your pfSense before deleting anything.

        One other thing you may try is to explicitly add your tunnel's far end IP in the Allowed IPs (/32). With 0.0.0.0, it shouldn't matter but the WG module is a little flaky and this might fix it:

        [Peer]
        PublicKey = ************************************
        AllowedIPs = x.x.x.x/32
        AllowedIPs = 0.0.0.0/0

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