Good morning Daniel, Daniel Gröber writes: >> wireguard still uses the wrong interface: >> >> 11:20:13.115154 eth0 Out IP 192.168.1.149.60031 > 194.187.90.23.4000: UDP, length 148 > > I haven't looked at the details yet but this smells like the same route > caching issue I found a while ago: > https://lists.zx2c4.com/pipermail/wireguard/2023-July/008111.html > > Does up/down'ing the interface make the problem go away? IIRC that will > re-initialize the udp socket and thus clear the route chache. Up & down does *not* fix it, however a *reboot* did. I've the feeling that this is a race condition together with bird running on the machine. I suspect the following is happening: - machine starts - ip rule is used to move traffic into table 42 (part of the container startup) - table 42 is populated by bird with static routes (part of bird startup) -- at this stage wireguard works - bird establishes iBGP sessions and receives alternate routes for the target in the main routing table - wireguard restart is triggered and from that moment on wireguard uses the route from the main table -- at this stage wireguard is broken/takes the route from the main table This is so far a theory, I'll need to verify that, maybe a simple test script as you suggested makes sense. > FYI Nico: It may be time to escalate these bugs to the network subsystem > maintainers on netdev@vger.kernel.org since Jason is not reading this list > anymore AFAICT. That is a very good point and I shall do so next week! > get_maintainer.pl spits out this list of emails to send To: > > Jason A. Donenfeld" , > "David S. Miller" , > Eric Dumazet , > Jakub Kicinski , > Paolo Abeni , > wireguard@lists.zx2c4.com, > netdev@vger.kernel.org, > linux-kernel@vger.kernel.org Thanks for looking up! > Do add me to CC as well. Before sending I'd recommend working out an > ip-netns based reproducer script -- makes it harder to ignore the report as > "ugh, too much work" ;) Understood and ... > Let me know if you need help with that, ... would certainly appreciate that. You are on matrix, too, aren't you? I'm @nico:ungleich.ch, might be easier for coordination. Best regards from sunny Glarus, Nico