From: Rich Felker <dalias@libc.org>
To: Bastian Bittorf <bb@npl.de>
Cc: musl@lists.openwall.com
Subject: Re: [musl] getaddrinfo/AI_ADDRCONFIG with ipv6 disabled
Date: Fri, 30 Apr 2021 12:52:38 -0400 [thread overview]
Message-ID: <20210430165238.GY2546@brightrain.aerifal.cx> (raw)
In-Reply-To: <20210430164033.lc7xu2c3dln3tni7@email>
On Fri, Apr 30, 2021 at 04:40:33PM +0000, Bastian Bittorf wrote:
> On Fri, Apr 30, 2021 at 08:38:04AM -0400, Rich Felker wrote:
> > Someone should probably also ping OpenWRT about why they're using this
> > arcane mechanism to block IPv6 to localhost.
>
> at least I can see:
> https://git.openwrt.org/?p=openwrt/svn-archive/archive.git;a=blob;f=target/linux/generic/patches-3.19/670-ipv6-allow-rejecting-with-source-address-failed-policy.patch;h=f32458df30ad466d4e3ac8224cbec1bd074b43ec;hb=35d90ba52069c96afd1a74600b91499e5feed0e0
>
> I was last refreshed on Tue Mar 30 22:01:27 2021 +0100
> and says:
>
> "RFC6204 L-14 requires rejecting traffic from invalid addresses with
> ICMPv6 Destination Unreachable, Code 5 (Source address failed ingress/
> egress policy) on the LAN side, so add an appropriate rule for that."
>
> But that is just guessing...
Presumably that would be for traffic originating from another host
OpenWRT is forwarding for (blocking it from spoofing ::1 on the wire?)
not for traffic originating on the OpenWRT box itself (where ::1
should work). I'm worried that if we just "fix" this issue on the musl
side, OpenWRT is just wrongly going to conclude there's no IPv6
coonnectivity rather than that they have a configuration error
breaking it..
Rich
next prev parent reply other threads:[~2021-04-30 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 2:44 Bob Richmond
2021-04-30 0:13 ` [musl] " Rich Felker
2021-04-30 12:38 ` Rich Felker
2021-04-30 16:40 ` Bastian Bittorf
2021-04-30 16:52 ` Rich Felker [this message]
2021-04-30 17:59 ` Julian Squires
2021-04-30 16:59 ` Jeffrey Walton
2021-04-30 18:49 ` Markus Wichmann
2021-04-30 19:50 ` Rich Felker
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=20210430165238.GY2546@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=bb@npl.de \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).