netdev - Re: [PATCH net] net: icmp6: add icmp_errors_use_inbound

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200402.175502.2304965794103611918.davem@davemloft.net>
Date:   Thu, 02 Apr 2020 17:55:02 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     code@...stallard.me.uk
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net] net: icmp6: add icmp_errors_use_inbound_ifaddr
 sysctl for IPv6

From: Tim Stallard <code@...stallard.me.uk>
Date: Wed,  1 Apr 2020 00:17:06 +0100

> In practice, this causes issues with IPv6 path MTU discovery in networks
> where unroutable linknets are used, and packets from these linknets are
> discarded by upstream providers' BCP38 filters, dropping all Packet
> Too Big errors. Traceroutes are also broken in this scenario.

But now traceroute6 is going to output confusing output by default
again in the scenerios described in the Fixes: commit.

Why don't we see if, explicitly, a source address was configured on
the route rather than us using a default saddr?  And in that case go
back to the old behavior.