[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210430165238.GY2546@brightrain.aerifal.cx>
Date: Fri, 30 Apr 2021 12:52:38 -0400
From: Rich Felker <dalias@...c.org>
To: Bastian Bittorf <bb@....de>
Cc: musl@...ts.openwall.com
Subject: Re: getaddrinfo/AI_ADDRCONFIG with ipv6 disabled
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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
