7.24.4 WireGuard still a bit screwed up? spurious "allowed-address match other peers"

All routers involved running 7.24.4.

Traffic seen (/tool sniffer) going out wg1 interface from router"A" towards router"B".

Traffic NOT seen (/tool sniffer) arriving on router"B".

Router"B" /interface/wireguard/peer/print showing "allowed-address match other peers". (Manual inspection, repeatedly, resize window, change print options, etc, etc, finds NO overlap of allowed-addresses).

Restart Router"B", problem went away!

Obviously, I cannot reproduce this.

But it looks like not all of the WireGuard disaster from early 7.24 (ref: V7.24 WireGuard peer is never reinstalled into the data plane after disable/enable ) has been fixed :person_facepalming:

I'm just guessing, but maybe what you're seeing is the effect of the fact that (fully) matching prefixes overwrite each other in the internal data structure of wireguard. They don't just "cover" (i.e. one is prioritized over the other) but overwrite each other fully.

This means that if another peer's entry overwrote your previous one, it's not enough to delete that peer for the overwritten one to reapoear, but the re-insertion has to be forced. The simplest is to change the allowed-addresses to something harmless then back.

I apologise, I don't understand what you're saying.

If it helps, no changes had been made in some days (at least) in the allowed-address fields, nor in any other way to the WireGuard configurations. This seems to be some persisting bug in the 7.2x ROS series' WireGuard implementations :frowning:

And, what got me to look at this at all, this morning, was the fact that abruptly certain very specific traffic wasn't flowing correctly. After the reboot (with no configuration changes having been made) the traffic flowed again.

No idea, then. It might have been a connection tracking anomaly over the path - that's known to upset wireguard, and the time needed for a reboot often allows the offending entry to time out (or if it's on the router itself, it's purged.)

I don't think this has a lot to do with the enable/disable bug. RouterOS doesn't reconfigure wireguard if there's no change.