This week I presented in bdNOG 4 on “Misused top ASNs”. It was a study we at Hurricane Electric did to see how many times AS1, AS2 and AS3 appeared in global routing table between 2010 and 2015. This highlights cases where AS1, AS2 or AS3 appeared as a result of wrong prepend. My presentation is embedded below: Overall bdNOG 4 had been a great experience. It’s good to see a nice NOG community actively sharing technical know-how, sharing experiences, and much more.
There seems be an ongoing route leak by AS49505 (Selectel, Russia) for K root server. K root server’s IP: 188.8.131.52 Origin Network: AS25152 Here’s trace from Airtel Looking Glass, Delhi PoP Mon Oct 26 16:21:18 GMT+05:30 2015 traceroute 184.108.40.206 Mon Oct 26 16:21:22.053 IST Type escape sequence to abort. Tracing the route to 220.127.116.11 1 \* 18.104.22.168 19 msec 4 msec 2 22.214.171.124 14 msec 3 msec 1 msec 3 14.
K root in Noida seems to be not getting enough traffic from quite sometime and connectivity does seems bit broken. This is a blog post following up to Dyn’s excellent and detailed post about how TIC leaked the world famous 126.96.36.199/24 address space used by AS25152. It was good to read this post from RIPE NCC written by my friend Emile (and thanks to him for crediting me to signal about traffic hitting outside!
Yesterday I was driving and radio was pretty boring. Next, I connected cell phone to car’s stereo (I use a PT-750 to wirelessly connected my devices to car’s audio system). Next I tuned into Gaana.com app and experience was overall good. The way whole setup was working itself is a wonder - wireless profiles keeping layer 3 link (IP address of device) consistent and handovers happening on layer 1. On top of that a while world of backbone routing across AS9498 backbone the hosting provider’s network of the app.
And my post on 1st April. Don’t take it as April fool post ;) Multiple times NIXI’s AS24029 has been reported as acting like transit ASN for multiple networks. I have analysed it in past and this is very much because of route leaks by few specific networks. I have explained difference in peering Vs transit routes and their handling previously on my blog. In short: A network is supposed to re-announce it’s peering and transit routes only to customer and not to any other peer or upstream.