Today I noticed some traffic on my blog from a link from Broadband forum. Here’s what poster wrote:
I made a thread a few days ago complaining about BSNL’s horrible routing. Well it looks like it has been fixed. I thank all the guys who made efforts to bring this to BSNL’s notice. Especially Anurag Bhatia who highlighted the issue with much detail on his blog
Softlayer connectivity problem and possible fix.
It’s late night here in India. I am having final 8th semester exams and as usual really bored! Though this time we have interesting subjects but still syllabus is pretty boring spreading across multiple books, notes and pdf’s. Anyways I will be out of college after June which sounds good.
Tonight, I found a routing glitch. Yes a routing glitch!! :)
These issues somehow keep my life in orbit and give a good understanding on how routing works over the Internet.
Just was looking at routing tables of BSNL. They have a significant address space in /10 - 117.192.0.0/10. Overall this /10 address space is divided into /18 and /20 subnets.
Let’s pick two of such subnets and observe routing tables from route-views:
117.192.0.0/18 117.192.0.0/20 Routing table for 117.192.0.0/18: * 117.192.0.0/18 193.0.0.56 0 3333 3356 6453 4755 9829 9829 9829 i * 194.85.102.33 0 3277 3216 6453 4755 9829 9829 9829 i * 194.
Finally back in village location.
Was just looking around and saw BSNL having really crazy routing. I looked around and saw this:
NIXI Looking Glass - show ip bgp neighbors 218.100.48.15 routes Router: NIXI Delhi (Noida) Command: show ip bgp neighbors 218.100.48.15 routes Total number of prefixes 0 Clearly BSNL is NOT announcing any prefix at NIXI Delhi at all. Thus if one has to send packets to BSNL in North area either it will be via transit (Tata/VSNL) or via any other peering NIXI exchange in Mumbai or Chennai.