Maximum active (Mullvad) VPN connections with WireGuard?

[K3ttle]

Hello,


I tried creating a new VPN connection using Mullvad (let's call it vpn1). I went through the same process I used to create my current working Mullvad connection (let's call it vpn0).

Whenever I assign an endpoint peer under 'VPN > WireGuard > Local' to the new config, the Interface assignment under 'Interfaces > Assignments' changes from the new WireGuard interface to my LAN interface.

However, if I disable vpn0 under 'VPN > WireGuard > Local', the new interface assignment flicks back to what it should be.

Is this expected behavior? Am I an idiot? Any advice appreciated.

[Koloa]

This may or may not help you...

One thing to keep in mind is that for each Mullvad connection you'll likely need to have a different Wireguard key, and, as you probably know, Mullvad only permits 5 total per Mullvad account. 

In my case, I have several Mullvad connections set up, each using their own wgX interface assignment, but, each connection has its own key, and, I believe in all cases, each has a different tunnel address.  There was a bit of trial and error in my getting everything to work right, but, I followed the guide on the OPNsense Docs site and it mostly got me where I needed to go.

I haven't experienced what you describe, though.

[K3ttle]

Hey thanks for the response. Can confirm I'm using a different key and endpoint IP.

I've started from scratch countless times now. Very strange behavior, and very frustrating