You are here

Limit on number of Wireguard Tunnels?

3 posts / 0 new
Last post
AB1OC
Limit on number of Wireguard Tunnels?
Is there a limit on the number of Wireguard tunnels that a non-supernode router can terminate? Specifically, I am trying to determine if there is a limit on the number of server tunnels that a single node can terminate. If there is a limit, does it pertain to the number of configured server tunnels or the number of actively connected server tunnels? We are runnring the latest official build (OLSR+Babel v3.25.8.0). Thank you,
 
w6bi
w6bi's picture
Wireguard Tunnel Servers
I have 24 tunnels configured, 14 of which are currently active.  I recently uncovered an issue with such a configuration, which was resolved in the most recent nightly builds.  Recommended!
And it depends on the hardware;  don't attempt it with an older hAP ac Lite, but rather with an ac2 or ac3.  They have faster/better CPUs and more RAM.
And your Internet bandwidth is a consideration.  OLSR broadcasts run constantly; the more tunnels you support, the more of your Internet bandwidth is consumed, both incoming and outgoing.   Babel-only would be substantially less, as it broadcasts network config info only when it detects a change.

Hope this helps.

73

Orv W6BI
 
AB1OC
Limit on number of Wireguard Tunnels?

Thank you, Orv. I went to the latest nightly build (OLSR+Bable) and I have been able to turn up 37 tunnels with 34 being active. This is as it should be in the setup here. The terminating node is a VM with plenty of CPU, memory, and network capacity.

I also tried the latest nightly build on our Supernode here but the build had problems estabishing and maintaining several of our Supernode tunnels so I rolled back to the latest official build there.

Thank you for your help.

Fred AB1OC

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer