Philip Homburg writes:
> As far as I know, this a well known Juniper bug where their routers
> forward errors ICMPs without checking whether the source address is
> link local.
Thinking about this... Is there any reason except formalities why you
shouldn't forward those packets? The won't gener
On 2021/09/15 19:06 , Gert Doering wrote:
On Wed, Sep 15, 2021 at 06:58:50PM +0200, Philip Homburg wrote:
My router at home gets a lot of error icmps with link local source, from
quite a few hops away...
*wake up* IPv4 "link local" (169.254.*) or IPv6 LLA (fe80::)?
IPv6 link local
The lat
On 9/15/21 11:32 AM, Jeroen Massar via ripe-atlas wrote:
Hi Folks,
Has anybody ever run a all-probe traceroute and then to detect any RFC1918
addresses in there? (though many probes will have locally some RFC1918)
Since probes are running measurements to many targets already, the full
dat
Hi,
On Wed, Sep 15, 2021 at 06:58:50PM +0200, Philip Homburg wrote:
> My router at home gets a lot of error icmps with link local source, from
> quite a few hops away...
*wake up* IPv4 "link local" (169.254.*) or IPv6 LLA (fe80::)?
The latter would make me very curious what sort of intermediat
On 2021/09/15 17:32 , Jeroen Massar via ripe-atlas wrote:
Has anybody ever run a all-probe traceroute and then to detect any RFC1918
addresses in there? (though many probes will have locally some RFC1918)
Atlas performs quite a few traceroutes on all probes. For example,
https://atlas.ripe.ne
Hi Folks,
Has anybody ever run a all-probe traceroute and then to detect any RFC1918
addresses in there? (though many probes will have locally some RFC1918)
We got CAIDAs spoofer project, but that primarily afaik checks that by doing
connections, not by checking ICMP returns.
I just saw toward
