WireGuard VPN providers that support pfsense

gabacho4 · Feb 20, 2021, 5:50 PM

@bcruze I'm running a 5100 and see the counters increasing. No issues that I can see there. I also run the widget on the dashboard and it increments too.

bcruze · Feb 20, 2021, 5:52 PM

@gabacho4 said in WireGuard VPN providers that support pfsense:

@bcruze I'm running a 5100 and see the counters increasing. No issues that I can see there. I also run the widget on the dashboard and it increments too.

I am sorry I didn't ask that clearly.

are your in/out packets and
collisions stuck at the numbers both of my screen shots show?

gabacho4 · Feb 20, 2021, 5:58 PM

@bcruze nope. I only have 6 in/out errors and 6 collisions. I seem to get that on all my wireguard interfaces so either it's a bug that I don't really care about, or literally there are some kind of collisions that occur as the connection is being made. Regardless, the service works and works very well. I'm sure Netgate will clean up any issues with the 21.02.x updates.

p1erre · Feb 20, 2021, 5:59 PM

@bcruze There are a lot of Collisions and errors on your setup

here is my interface status

WG0MULLVAD Interface (opt12, wg0)
Status
up 
IPv4 Address
xx.xx.xx.xx 
Subnet mask IPv4
255.255.255.255 
Gateway IPv4
xx.xx.xx.xx
IPv6 Link Local
xxxxx%wg0 
IPv6 Address
xxxxx 
Subnet mask IPv6
64 
Gateway IPv6
xxxxx
MTU
1420 
Media
25GBase-ACC <full-duplex> 
In/out packets
3277492/1965393 (2.16 GiB/849.86 MiB) 
In/out packets (pass)
3277492/1965393 (2.16 GiB/849.86 MiB) 
In/out packets (block)
108/11 (14 KiB/0 B) 
In/out errors
6/6 
Collisions
6

bcruze · Feb 20, 2021, 6:02 PM

@p1erre said in WireGuard VPN providers that support pfsense:

@bcruze There are a lot of Collisions and errors on your setup

here is my interface status

WG0MULLVAD Interface (opt12, wg0)
Status
up 
IPv4 Address
xx.xx.xx.xx 
Subnet mask IPv4
255.255.255.255 
Gateway IPv4
xx.xx.xx.xx
IPv6 Link Local
xxxxx%wg0 
IPv6 Address
xxxxx 
Subnet mask IPv6
64 
Gateway IPv6
xxxxx
MTU
1420 
Media
25GBase-ACC <full-duplex> 
In/out packets
3277492/1965393 (2.16 GiB/849.86 MiB) 
In/out packets (pass)
3277492/1965393 (2.16 GiB/849.86 MiB) 
In/out packets (block)
108/11 (14 KiB/0 B) 
In/out errors
6/6 
Collisions
6

YES. but those numbers show up immediately upon the creation and connection of the session

you both confirmed the same as you can see just different numbers.

n8rfe · Feb 20, 2021, 9:32 PM

@p1erre said in WireGuard VPN providers that support pfsense:

Mullvad

Excellent find. Thanks for this. I am in the process of testing them.

beachbum2021 · Feb 21, 2021, 1:10 AM

@gabacho4 where do we get the public/private key from with their services?

bcruze · Feb 21, 2021, 1:10 AM

@beachbum2021 said in WireGuard VPN providers that support pfsense:

@gabacho4 where do we get the public/private key from with their services?

Click the download button scroll down and click wireguard

hypnosis4u2nv · Feb 21, 2021, 3:39 PM

I have Torguard up and running.

Griffo · Feb 22, 2021, 12:00 AM

@n8rfe I've used several succesfully. The only one that's a real pain is Nord as they regard their config as secret squirrel.

Mullvad
VPN.AC
ExpressVPN

dma_pf · Feb 23, 2021, 3:29 PM

I've been using IVPN for several years and have been happy with them. They do support Wireguard and I have transitioned my pfSense to use Wireguard exclusively with them. I've posted screenshots of how I got it configured in this post https://forum.netgate.com/topic/160378/wg-not-routing-or-sending-traffic

ErTnEc · Feb 25, 2021, 2:12 AM

@hypnosis4u2nv said in WireGuard VPN providers that support pfsense:

I have Torguard up and running.

Any chance you could share how you got this running? I've been trying to get this in place but the peer won't connect.

hypnosis4u2nv · Feb 25, 2021, 3:03 AM

@ertnec Go to the config generator, select tunnel type - wireguard, choose your server location and enter your VPN log in details.

Go to pfsense VPN->Wireguard->Add Tunnel. Check Enable interface, add description, and go down and Generate New Keys.

Go back and enter those keys in the Torguard config generator and hit generate config button. You should have a config printed out in the box. Copy the address under interface and plug that into address in pfsense wireguard tunnel. Listen port should be listed as 51820 so enter that in the tunnel. Click add peer on the bottom in the wireguard setup.

The peer configuration is being copied from the config that was generated and plugged into all applicable fields in the tunnel peer settings. Leave everything else blank.

Create and enable your Wireguard interface. Create a firewall rule under the wireguard interface to allow any.

Add your NAT rule for WAN.

Then add any policy based rules to the firewall.

Done.

ErTnEc · Feb 25, 2021, 4:42 PM

@hypnosis4u2nv said in WireGuard VPN providers that support pfsense:

@ertnec Go to the config generator, select tunnel type - wireguard, choose your server location and enter your VPN log in details.

Go to pfsense VPN->Wireguard->Add Tunnel. Check Enable interface, add description, and go down and Generate New Keys.

Go back and enter those keys in the Torguard config generator and hit generate config button. You should have a config printed out in the box. Copy the address under interface and plug that into address in pfsense wireguard tunnel. Listen port should be listed as 51820 so enter that in the tunnel. Click add peer on the bottom in the wireguard setup.

The peer configuration is being copied from the config that was generated and plugged into all applicable fields in the tunnel peer settings. Leave everything else blank.

Create and enable your Wireguard interface. Create a firewall rule under the wireguard interface to allow any.

Add your NAT rule for WAN.

Then add any policy based rules to the firewall.

Done.

You know what, I'm an idiot... It was working fine, I'd just not interpreted the output of wg correctly. Once I'd properly set it to the vlan which uses it (so just swapping over ovpnc1 for wg0 on the gateway interface), everything was spot on. Although what wasn't clear was that in order to get port forwarding working correctly, you need to first request/configure the range within TG itself, then generate a new config. I'd generated the config then requested the port forwards.

Compared to OpenVPN, peak speeds seem far more consistent (holding steady now at around 55mbps which is the upper limit of my current connection compared to ranging from 45-55), although CPU load has increased from an average of 40% to around 55%.

hypnosis4u2nv · Feb 25, 2021, 7:07 PM

@ertnec Glad you got it working. The only bugs I am seeing is that the traffic graph doesn't display any data and the RTT latency data is ridiculously low so probably wrong. Could be an issue if you're running a gateway group and it's choosing gateways based on latency.

gabacho4 · Feb 25, 2021, 7:13 PM

@hypnosis4u2nv the latency is low because the gateway is set to ping itself. You’ll want to go to System -> Routing, then edit the gateway and set it to ping an alternate ip like 8.8.8.8 or whatever. Them you’ll get a real gauge of your latency.

tigs · Feb 25, 2021, 7:27 PM

windscribe also has wireguard support.

ErTnEc · Feb 25, 2021, 8:39 PM

@hypnosis4u2nv said in WireGuard VPN providers that support pfsense:

@ertnec Glad you got it working. The only bugs I am seeing is that the traffic graph doesn't display any data and the RTT latency data is ridiculously low so probably wrong. Could be an issue if you're running a gateway group and it's choosing gateways based on latency.

Ahhh I never noticed the traffic graph reporting incorrectly for the interface where the tunnel is paired! Interesting

hypnosis4u2nv · Feb 25, 2021, 9:01 PM

@gabacho4 Thanks! Just added it and it displays correctly! Duh!

xxGBHxx · Feb 26, 2021, 1:56 AM

@n8rfe iVPN.net fully support it and even have a guide for pfSense they uploaded a few days ago,