os-wireguard rejects new tunnel definition with duplicate key message

[noci2012]

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

• [v] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
• [v] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
• [v] The title contains the plugin to which this issue belongs

Describe the bug
Setup: Some endpoints get a choice to either connect to internal LAN or public LAN or IOT LAN from outside.
the OpnSense fw has wg1, wg2, wg3 for this.
The endpoints have a single PrivateKey. this is no problem on a different linux (and on a previous firewall[ also linux based]).
The keys need to be unique per interface.
Currently the web interface does not take the interface into consideration when checking for duplicate keys.

To Reproduce
Steps to reproduce the behavior:

1. goto VPN/Wireguard/peers/wg1
2. add a client
3. goto VPN/Wireguard/peers/wg2
4. add a client with the same public key.
5. See error
   Expected behavior
   Only display the editor within the same interface. (no new device with duplicate key on wg1 when adding on wg1).

Screenshots
N/A

Relevant log files
N/A

Additional context
It is an oversight.

Environment
OpnSense 24.7 (24.7.12_4)

[fichtner]

If this is the initial 24.7 you may want to grab an update first.

[noci2012]

This is a last update for 24.7 (24.7.12_4) I upgraded to that one to test for updates on this.
There is a good reason for this check for a single interface. The requirement does not extend to a different wireguard interface.

[fichtner]

Thanks for the clarification.

[noci2012]

(BTW, this condition exists as entries are created outside of OpnSense and added to OpnSense firewall.
Peer generator is not used.