Wireguard instance update error - Invalid integer value.

[SFC]

After upgrading to 24.1_1 I noticed that when I attempt to update my wireguard instance (for example to change the peer if my vpn provider has a server go offline), when I click save it spits out the error message "Invalid integer value." and instance is highlighted in red (image attached).

[Moonshine]

Yep, this is a little brutal if you need to re-configure wg0.   Seems like a new validation rule needs tweaking.  Hope it gets in the next update... soon. :'(

EDIT:  Looks like a fix is coming.  https://github.com/opnsense/core/commit/ca04a7943fdf4c87f1c73990f0447796410de457

[newsense]

Nope, I'm afraid the eagle has landed in 24.1.1 and is not what you're expecting.

Ad only allowed the integer to start from 0 but the fix doesn't take into account you might want to start counting in double digits from 00..09.


Fastest way to get a straight answer would be to comment in that GH issue - I doubt however this will be seen as a bug to fix.