From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: "Daniel Gröber" <dxld@darkboxed.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard uses incorrect interface - routing issue
Date: Sat, 22 Jun 2024 11:22:28 +0200 [thread overview]
Message-ID: <87zfrdgwmj.fsf@ungleich.ch> (raw)
In-Reply-To: <20240621122926.2xzt7ulno5oczqcv@House.clients.dxld.at> ("Daniel =?utf-8?Q?Gr=C3=B6ber=22's?= message of "Fri, 21 Jun 2024 14:29:26 +0200")
[-- Attachment #1: Type: text/plain, Size: 2427 bytes --]
Good morning Daniel,
Daniel Gröber <dxld@darkboxed.org> 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" <Jason@zx2c4.com>,
> "David S. Miller" <davem@davemloft.net>,
> Eric Dumazet <edumazet@google.com>,
> Jakub Kicinski <kuba@kernel.org>,
> Paolo Abeni <pabeni@redhat.com>,
> 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
[-- Attachment #2.1: Type: text/plain, Size: 62 bytes --]
--
Sustainable and modern Infrastructures by ungleich.ch
[-- Attachment #2.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
next prev parent reply other threads:[~2024-06-22 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 11:13 Nico Schottelius
2024-06-21 11:24 ` Nico Schottelius
2024-06-21 12:29 ` Daniel Gröber
2024-06-22 9:22 ` Nico Schottelius [this message]
2024-06-21 14:42 ` Diyaa Alkanakre
2024-06-21 15:18 ` Daniel Gröber
2024-06-21 15:38 ` Nico Schottelius
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfrdgwmj.fsf@ungleich.ch \
--to=nico.schottelius@ungleich.ch \
--cc=dxld@darkboxed.org \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).