possible that this is various AWS customers making iptables/firewall mistakes? "block that pesky rfc1918 172/12 space!!"
On Tue, Oct 1, 2019 at 8:51 AM Stephane Bortzmeyer <[email protected]> wrote: > > On Mon, Sep 30, 2019 at 11:38:25PM -0700, > Mehmet Akcin <[email protected]> wrote > a message of 131 lines which said: > > > Here you go > > The two RIPE Atlas probes in the AT&T prefix seem able to reach AWS: > > % blaeu-traceroute --protocol TCP --size=0 --port=80 --first_hop=64 --format > --prefix 172.0.0.0/12 --requested 10 52.21.66.90 > Measurement #22932983 Traceroute 52.21.66.90 from prefix 172.0.0.0/12 uses 2 > probes > 2 probes reported > Test #22932983 done at 2019-10-01T07:46:00Z > From: 172.10.12.5 7018 ATT-INTERNET4 - AT&T Services, Inc., US > Source address: 172.10.12.5 > Probe ID: 11203 > 64 52.21.66.90 14618 AMAZON-AES - Amazon.com, Inc., US [11.43, > 11.158, 10.806] > > From: 172.8.16.48 7018 ATT-INTERNET4 - AT&T Services, Inc., US > Source address: 192.168.1.73 > Probe ID: 51354 > 64 52.21.66.90 14618 AMAZON-AES - Amazon.com, Inc., US [22.301, > 21.612, 21.615] >
