ANSWERED pfsense wireguard and multiple airvpn tunnels

[krel lac 0]

Hi,

I wanted to have several airpn tunnel/peer sessions to have some load balancing and redundancy using a gateway group.

I am having problem setting up two airvpn generated wireguard tunnels combo (for example ch3.x.x.x and no3.x.x.x) in pfsense. Individually tunnels do work and can be configured easy, e.g. tunnel/peer combo the way those are generated using web config configurator, nat and firewall rules, gateway group - all is working fine.

Once I add 2nd airvpn wireguard tunnel/peer combo, pfsense does not accept the config (not much meaningful details in pfsense logs either). If I add 2nd wireguard config as a peer to the 1st tunnel the pfsense is says "the public is already in use...". 

Seems that I cannot add several individual airpn tunnel/peer sessions. I did test the pfsense with one airvpn tunnel/peer session and added a 3rd party vpn wireguard conf and there was no issues whatsoever. Both airvpn and 3rd party vpn worked as I wanted (have some load balancing and redundancy using a gateway group).

I might be doing something wrong, but how can I run 2 or more airvpn wireguard tunnel/peer session that terminate in different airvpn hosted countries (eg, ch, no, us, sg...)

KR
krel

[go558a83nk 379]

are you using different keys for each tunnel?  you create different keys in the devices page of your client area.  then you create configs selecting the "device" you want to use.

you must use different keys otherwise the tunnels are trying to use the same IP address space.  

[krel lac 0]

Hi,

my bed - in the pfsense tunnel section config when adding the tunnel I used the same port in "Listen Port" section and as the port was already used by the 1st config it did not work for the 2nd config... 

So I deleted the "listen port" for each tunnel and now ports are auto generated by pfsense and are always different.

All tunnels are up and running.