Hi everyone!
I have done upgrade to the OPNsense 24.1.1-amd64 and I noticed some problems with Wireguard VPN service:
- Peer setup interface is blocking adding peer with the same public key - this is new problem with 24.1.1
- Wireguard widget and diagnostic page shows wrong peer for service instance. In my example it shows the same peer for two wg instances wg1 and wg3 even though they are configured for different peers. This problem started somewhere in earlier OPNsense version
- When changing peer for wg instance, routing is sometimes stuck with old peer even after instance restart and whole wg service restart. Only full reboot fixes the problem. This problem was present for a while, would need to test more the newest release.
Why this is problematic? Well in the case of the first issue, it prevents me from adding more peers endpoints for vpn service as in my case they all have the same public key. This also prevents modification of existing peers, so for now I have not found any workaround (I don't really want to remove existing peers and be left with just one).
Second problem is for most parts just cosmetic but it shows that there is some issue with diagnostic page and Wireguard widget.
Last issue can be really annoying when trying to change peer endpoint for wg instance. It really would be great if changing peer did refresh routing.
For now the most pressing issue for me is the inability to add peers with the same public key in wg peer setup. If anyone can suggest some workaround or fix I would be really greatful.
Best regards.
#1 is issued by https://github.com/opnsense/core/issues/7110 and fixed in https://github.com/opnsense/core/issues/7213 and/or https://github.com/opnsense/core/issues/7229
for 2 and 3 you could possible more details and raise an issue at github?