This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] All-Probe Traceroute + detect RFC1918 addresses
- Previous message (by thread): [atlas] All-Probe Traceroute + detect RFC1918 addresses
- Next message (by thread): [atlas] Controller kicking out probe with no clear reason?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeroen Massar
jeroen at massar.ch
Sat Sep 18 00:09:51 CEST 2021
> On 20210917, at 21:20, Bjørn Mork <bjorn at mork.no> wrote: > [..] >> Leaking packets from addresse that do not belong to you does. > > Yes. And the point is that you cannot tell if there is a leakage unless > you are able to detect the network borders. Which you can't by counting > traceroute hops. In the example I gave it is all quite obvious actually... as there are multiple ASNs in the path and then RFC1918... Noting again, that seeing RFC1918 a few hops away is a clear indicator that there is likely a possibility to spoof as they don't even bother to filter the obvious. Greets, Jeroen
- Previous message (by thread): [atlas] All-Probe Traceroute + detect RFC1918 addresses
- Next message (by thread): [atlas] Controller kicking out probe with no clear reason?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]