Bug in Wireguard Peer AllowedAddress
Hi @Alex_vd_B
Thanks for posting in our business forum.
In Controller mode.
It would only be a problem in standalone mode. Yet, the 192.168.0.1/16 = 192.168.0.0/16.
The system in standalone aims to avoid any overlap created and gives a warning when it is triggered. That's a generic mechanism.
I think that's the reason why you see the error in standalone mode. Yet, you can set up 192.168.0.1/16 and save it, and will change to 192.168.0.0/16. In fact, it still works.
I think this is an overall mechanism in standalone mode.
@Clive_A Thank you for responding.
Indeed, standalone, and indeed after entering 192.168.0.1/16 it is accepted and then modified to 192.168.0.0/16. But then it does not seem to work (see another topic).
I am greeted with the following, which strongly suggests it is an ERROR in stead of a warning. Also the OK button does not work, something I would expect to work it is was only a warning message.
Indeed 192.168.x.y/16 with either x or y not zero does work, but given my struggles I already forgave myself thinking this is a bug.
If it is intended to save it this way, may I suggest a different way of reporting the warning to the user and/or documenting it. Thanks.
