surfshark guide for pfsense wireguard
-
Thank you kindly! I’ll give this a go and will report back. I’m used to PiVPN where it’s just install, create a profile, scan the QR code and done! lol
-
@rtorres actually they do have a guide for pfsense with wireguard but you have to ask support for it
-
Also you can only have one concurrent connection via WireGuard to them with pfSense.
-
@yucca1960 Whoever gets should post it online somewhere to have a general guide
-
What do you mean by this? I would have liked my whole pfSense rig to be passing all my home network + VPN on the go.
Nothing fancy just home network wide VPN and on the go cellphone VPN.
Hopefully this can be accomplished.
-
@flat4 said in surfshark guide for pfsense wireguard:
@yucca1960 Whoever gets should post it online somewhere to have a general guide
I just got the guide for WireGuard!! :)
Where can I host? The original link I got from the CSR at SurfShark is:
https://v2uploads.zopim.io/p/2/L/p2LbwLkvfQoSdzOl6VEltzQA6StiZqrs/6994fa408e6b3087ac699037647c2fa0c3dfa783.pdf -
@rtorres said in surfshark guide for pfsense wireguard:
https://v2uploads.zopim.io/p/2/L/p2LbwLkvfQoSdzOl6VEltzQA6StiZqrs/6994fa408e6b3087ac699037647c2fa0c3dfa783.pdf
You can attach pdf's to posts, as long as they are not too big.. But the link should be fine.
-
I tried to upload the pdf but was too big. Also you can use the ivpn guide for pfsense wireguard and add the kill switch, it does work perfectly
-
@rtorres said in surfshark guide for pfsense wireguard:
Hopefully this can be accomplished.
Sure, I said you only can have one connection to them.
-
@rtorres said in surfshark guide for pfsense wireguard:
I just got the guide for WireGuard!! :)
Wonder why they say:
Go to Interfaces > LAN and set the MSS to 1412
I think this is bad advice. Also those guides want you to disable your WAN-connection entirely which is not a good idea, PBR is the way.
-
@Bob-Dig can you explain what PBR means? Thanks
-
@yucca1960
Pro Bull Ridingbut that's not it
-
I am under the impression now that surfshark isn't working well with pfSense in general. Lately I only tested with one tunnel and that still made problems after some time (going down after 10-30 minutes and coming up again), even with MTU 1420.
But can it be, is WireGuard in FreeBSD so much different than in linux because I have no problems using OpenWRT with them.
-
@Bob-Dig Surfshark has been working great for me, MTU 1420 and all no down time what so ever.
As bad idea as people would think, I have 4 instances going on with Surfshark - San Jose, San Francisco, Los Angeles and Las Vegas.
Although I have been getting a lot of high latency for San Francisco - even though I live about an hour away...
Which location are you connecting to? Maybe I can give it a try and report back :)
-
@rtorres said in surfshark guide for pfsense wireguard:
Which location are you connecting to?
Germany, aren't you tired right now?
My testing, with only one tunnel, could have been flawed. On the other hand, it is what I have seen long before, so I have my doubts. For me, it is not working well with pfSense and good enough with OpenWRT, all virtualized.
Have you watched your tunnels closely for some time? Maybe Surfshark doesn't like me.
-
I just realized that there is a even worse explanation to this: I don't have a "VPN-killswitch" for OpenWRT. And the guide on surfshark for OpenWRT is just trash (confirmed)!
That means, I don't see problems on OpenWRT because I have leaks!
@rtorres Now my question to you, have you done any "leak protection" for your setup on pfSense? -
@Bob-Dig LOL YES! But insomnia always wins so I'm always up ALL night!
I watch them literally every morning, spot check during the day, and at night.
I make it a ritual to constantly check because I have Wireguard on my devices to 'remote' to my pfSense to take advantage of pfBlockerNG and Surfshark/IVPN VPN services.
I did not include ANY kill switches like IVPN suggests (not too sure if the Surfshark had that on their guide). I only included static routes and rules to allow from VPN server to WAN - although IDK if this is needed since this was part of the kill switch.
I am constantly checking on dnsleaktest.com for any leaks.. but so far so good, only the DNS I specified have been popping up. But I am thinking of just removing VPN DNS servers and hosting it 'in-house.'
I will add Germany to my list and monitor. I am curious as IVPN has been behaving but I see Surfshark has been a bit crazy with latency and packet loss...
I get a good 1.21Gbps - 1.25Gbps, I pay my ISP for 1.2Gbps.. so I call it good! :)
I have about 8 VPN connections on my pfSense and make sure I have a monitor IP on them to check latency and all that good stuff:
-
@rtorres said in surfshark guide for pfsense wireguard:
I did not include ANY kill switches like IVPN suggests (not too sure if the Surfshark had that on their guide).
So there is one option in pfSense you really should tick: Skip rules when gateway is down (SystemAdvancedMiscellaneous)
For my setup, it looks like BERLIN has continuous problems but also I have not seen the same flakiness now having a "Killswitch" for OpenWRT. So for me it could still be a problem in pfSense.
-
Yes, I have a very good tutorial in PDF format specifically created for surfshark wireguard on Pfsense.
Apparently you can't attach files here so I put it on my Google drive.
[Bad link removed]
-
Your link is restricted, I can't open it.
