Multiple Wireguard Tunnels

[anon1701 0]

I have (finally) got he Wireguard setup to AirVPN working (thanks to those that answered) - it was essentially fat fingered syndrome on my part + a bit of a misunderstanding. All good.

So second question - can I do multiple tunnels.
If we look at the AirVPN config file:

[Interface]
Address = 10.xx.yy.zz/10, ipv6 address
PrivateKey = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
DNS = 10.128.0.1, fd7d:76ee:e68f:a993::1

[Peer]
PublicKey = BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
PresharedKey = CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Endpoint = 146.70.94.2:1637
AllowedIPs = 0.0.0.0/0, ::/0
PersistentKeepalive = 15

The bit that has me slightly worried is the Address under Interface. Its the same in all the AirVPN Config files. Is this likley to cause an issue with having two tunnels on the same network?

[SurprisedItWorks 55]

Have you tried having each config set up with a different AirVPN "device"? That may give you the disjoint subnets you need.

[anon1701 0]

Thats a thought
[Interface]
Address = 10.aaa.bbb.ccc/10 - which is different.
PrivateKey = 
DNS = 10.128.0.1

[Peer]
PublicKey = 
PresharedKey = 
Endpoint = 213.152.161.180:1637
AllowedIPs = 0.0.0.0/0, ::/0
PersistentKeepalive = 15

Works - thank you
Any idea why AirVPN use a /10 rather than something a lot smaller - its only a tunnel

[SurprisedItWorks 55]

No idea. Perhaps one of the more experienced network guys here can enlighten us. 

[go558a83nk 389]

1 hour ago, Aardvark56 said:

Thats a thought
[Interface]
Address = 10.aaa.bbb.ccc/10 - which is different.
PrivateKey = 
DNS = 10.128.0.1

[Peer]
PublicKey = 
PresharedKey = 
Endpoint = 213.152.161.180:1637
AllowedIPs = 0.0.0.0/0, ::/0
PersistentKeepalive = 15

Works - thank you
Any idea why AirVPN use a /10 rather than something a lot smaller - its only a tunnel

I've used /32 for multiple pfsense clients and it works fine.  Not sure why /10 is in the configs.

[anon1701 0]

I just tried changing to /24 rather than /10
The second gateway now comes up, whereas before it just stayed down due to a routing issue causing a monitor issue

So I went further and changed one tunnel  to /29 and the other to /26 (due to unfortunate choice of .223 by AirVPN which is a broadcast address for anything smaller
Still works