From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: "Marek Küthe" <m-k-mailling-list@mk16.de>
Cc: v@sess.ink, wireguard@lists.zx2c4.com
Subject: Re: AllowedIPs = ::/0 routes IPv4 - on Android?
Date: Tue, 24 Oct 2023 13:08:14 +0200 [thread overview]
Message-ID: <875y2wgtv7.fsf@ungleich.ch> (raw)
In-Reply-To: <20231024113755.6a786c71@parrot>
Hello Marek,
since when does ::/0 refer to IPv4 addresses? To my knowledge,
::/0 is the IPv6 all route and does not include any IPv4.
Best regards,
Nico
Marek Küthe <m-k-mailling-list@mk16.de> writes:
> [[PGP Signed Part:Undecided]]
> Hello Valentijn,
>
> ::/0 does not describe no IPv4 address, but all IP addresses. So when
> you write ::/0, all IPv4 addresses are routed through the tunnel. If
> you don't want IPv4 routes, you can simply omit them in AllowedIPs (so
> only put IPv6 addresses there, or only address which should go through
> the tunnel).
>
> Greetings
> Marek Küthe
>
> On Tue, 5 Sep 2023 16:04:34 +0200
> Valentijn Sessink <v@sess.ink> wrote:
>
>> Hi List,
>>
>> I have a WG endpoint configured with
>> AllowedIPs = ::/0
>> ... on an Android phone.
>>
>> To my surprise, I found out that this also tries to route IPv4 addresses
>> to the other WG side.
>>
>> I was able to change that with a single "bogus" IPv4 address,
>> "AllowedIPs = ::/0, 192.0.2.99/32"
>>
>> Is this a known feature? Android 13, WireGuard for Android
>> v1.0.20230707, (from AOSP).
>>
>> Best regards,
>>
>> Valentijn
--
Sustainable and modern Infrastructures by ungleich.ch
next prev parent reply other threads:[~2023-10-24 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 14:04 Valentijn Sessink
2023-10-24 9:37 ` Marek Küthe
2023-10-24 11:08 ` Nico Schottelius [this message]
2023-10-24 11:13 ` Valentijn Sessink
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=875y2wgtv7.fsf@ungleich.ch \
--to=nico.schottelius@ungleich.ch \
--cc=m-k-mailling-list@mk16.de \
--cc=v@sess.ink \
--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).