net/wireguard: Local Configuration - Maximum number of instances reached

[astuckey123]

plugins/net/wireguard/src/opnsense/mvc/app/models/OPNsense/Wireguard/Server.xml

Line 20 in f8f3975

<MaximumValue>19</MaximumValue>

It looks like we are hard-coding the maximum number of WG local configurations to 20.
Can this be increased, or the limitation be removed altogether?
I haven't been able to find any evidence so far on an actual limitation within WG itself (could be lack of googling skill here too, so happy to stand corrected)

[OPNsense-bot]

Thank you for creating an issue.
Since the ticket doesn't seem to be using one of our templates, we're marking this issue as low priority until further notice.

For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.

The easiest option to gain traction is to close this ticket and open a new one using one of our templates.

[mimugmail]

You know that you dont need acseparate instance for every s2s? Cant imagine you need more than 5 :)

I came from early days where WireGuard itself was unstable

[astuckey123]

You know that you dont need acseparate instance for every s2s? Cant imagine you need more than 5 :)

I came from early days where WireGuard itself was unstable

Lots of BGP and OSPF international overlay networking over multiple clouds and on-prem sites where they each need their own interfaces and policies, but you are right, can probably squeeze some things into single WG local's.

[mimugmail]

Cool :) next version wont come with any limits. Maybe you want to Share your setup in a blogpost. Always nice to see how others are using OPNsense :)