Networking

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.

Back in India after amazing APRICOT 2013 at Singapore. It was nice to stay in East Asia for a while and look around. :)

Anyways, issue for today - I have been using Airtel DNS servers from quite sometime since BSNL has crappy DNS while Google gives issues with Akamai while OpenDNS doesn’t has any node in India yet.  

Today I noticed a NXDOMAIN redirection for a non-working domain and later investigated. It seems like Airtel is hijacking on NXDOMAIN queries now.

A quick blog post on a interesting issue coming up due to combined problem of CDN failure on Google Public DNS and bad Akamai performance due to Tata-NTT peering issue.

I was trying Zembra mail since there’s no more free Google Apps edition and one of my friend asked me to basic email on his domain up. It was more or less a straight task by installing Zembra with decent GUI.

An interesting evening here in village. From today sessional tests started at college and so does my blog posts too (to keep myself with positive energy!) ;)

 

Learned something new while troubleshooting. :)

I am used to getting latency of ~350ms with my server in Europe as I have mentioned in my past blog posts.

My connection > Server goes direct but return path goes via US and this is what increases latency. Today all of sudden I saw latency of 200ms with my server. 150ms less - that’s significant.

Yesterday it was reported across networking community that Google’s prefixes were having issue due to an Indonesian ISP Moratel AS23947.

Quick analysis

From data logged by routeviews it seems like it wasn’t exactly a prefix hijack. AS23947 did not originated prefixes but rather had a route leak leading to path leak of AS23947 > AS15169. 

Here’s a view of global routing table for Google’s prefix 216.239.32.0/24 at 15:57 GMT on 4th Nov: