Once upon a time, Mirjam Kuehne <mir@ripe.net> said:
Dear colleagues,
Related to the discussion about 128.0/16, we did some measurements. The details can be found on RIPE Labs:
https://labs.ripe.net/Members/emileaben/the-curious-case-of-128.0-16
Kind regards, Mirjam Kuehne RIPE NCC
Using RIPE's traceroute web interface, I can see that Sprint is filtering 128.0.0.0/16: from 128.0.0.1 traceroute to 216.180.54.1 (216.180.54.1), 30 hops max, 40 byte packets 1 gw.nik-guest.nikrtr.ripe.net (193.0.0.234) 0.803 ms 1.005 ms 1.061 ms 2 ams16-core-1.gigabiteth8-1-0.swip.net (195.69.145.139) 0.551 ms 0.466 ms 0.641 ms 3 ams-core-1.tengige0-0-0-6.tele2.net (130.244.49.198) 3.378 ms 3.467 ms 3.624 ms 4 nyc9-core-1.pos8-0-0.tele2.net (130.244.218.214) 76.618 ms 76.683 ms 76.746 ms 5 * * * from 193.0.0.232 traceroute to 216.180.54.1 (216.180.54.1), 30 hops max, 40 byte packets 1 gw.nik-guest.nikrtr.ripe.net (193.0.0.234) 0.466 ms 0.514 ms 0.608 ms 2 ams16-core-1.gigabiteth8-1-0.swip.net (195.69.145.139) 0.684 ms 0.581 ms 0.563 ms 3 ams-core-1.tengige0-0-0-6.tele2.net (130.244.49.198) 3.890 ms 3.919 ms 3.912 ms 4 nyc9-core-1.pos8-0-0.tele2.net (130.244.218.214) 76.292 ms 76.317 ms 76.304 ms 5 144.223.26.73 (144.223.26.73) 76.639 ms 76.475 ms 76.511 ms (and on to my IP) I believe that Sprint is using Cisco, not Juniper. This is either a manual filter or there is another (unidentified) issue with some Cisco configurations. I've opened a ticket with Sprint, although I don't know how far it will go, since I'm getting a MySQL syntax error trying to view the ticket in their web interface (somebody must not understand SQL injection security issues). -- Chris Adams <cmadams@hiwaay.net> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.