18 Oct

BSNL-Softlayer issue

Seems like BSNL-NIB (AS9829) routing with Softlayer’s Singapore datacenter (AS36351) is messed up.
Example route between BSNL consumer connection (from Haryana, India) to Softlayer hosted site dot19.com

1 router2 (192.168.1.100) [AS8151/AS28513] 3.136 ms 3.874 ms 4.675 ms
2 117.200.48.1 (117.200.48.1) [AS9829] 29.088 ms 32.395 ms 35.773 ms
3 218.248.173.42 (218.248.173.42) [AS9829] 42.411 ms 44.746 ms 47.176 ms
4 218.248.255.70 (218.248.255.70) [AS9829] 92.977 ms 95.322 ms 97.758 ms
5 64.213.76.69 (64.213.76.69) [AS3043] 323.921 ms 324.594 ms 327.478 ms
6 ix-20-0.tcore2.LVW-LosAngeles.as6453.net (209.58.53.9) [AS6453] 333.339 ms 302.673 ms 303.992 ms
7 if-8-2-1-0.tcore1.PDI-PaloAlto.as6453.net (64.86.252.114) [AS6453] 419.641 ms 423.086 ms 424.411 ms
8 if-2-2.tcore2.PDI-PaloAlto.as6453.net (66.198.127.2) [AS6453] 425.475 ms 426.956 ms 430.239 ms
9 if-9-2.tcore1.TV2-Tokyo.as6453.net (180.87.180.18) [*] 436.026 ms 433.594 ms 434.911 ms
10 180.87.180.50 (180.87.180.50) [*] 439.543 ms 438.330 ms 441.001 ms
11 ae7.bbr01.eq01.tok01.networklayer.com (50.97.18.162) [AS36351] 471.290 ms 446.401 ms 472.233 ms
12 ae1.bbr01.eq01.sng02.networklayer.com (50.97.18.165) [AS36351] 477.914 ms 480.721 ms 485.605 ms
13 ae5.dar01.sr03.sng01.networklayer.com (50.97.18.197) [AS36351] 499.273 ms 502.262 ms 501.499 ms
14 po1.fcr01.sr03.sng01.networklayer.com (174.133.118.131) [AS36351] 489.251 ms po2.fcr01.sr03.sng01.networklayer.com (174.133.118.133) [AS36351] 496.491 ms 497.322 ms
15 * * *
16 * * *
17 * * *
18 * * *

Messed up routing tables of BSNL or lack of co-ordination between Tata Comm & Softlayer?

06 Oct

Messed up connectivity of root servers in India

Today I was showing a good friend – how root servers are working and how they are connected.
I was explaining him anycasting and gave example of k-root node which is hosted in Delhi by niXi i.e National Internet Exchange of India.
I was totally stunned to find traceroute result to anycasting based block of k-root-node hosted in Delhi from my BSNL connection.
Checkout traceroute here.

It seems like BSNL has gone totally wild in listening to announcements for 193.0.14.0/23 via ASN 25152 which is of  RIPE-NCC-K-ROOT nodes.
Instead of hearing block via nixi or direct connection with AS25152, BSNL is listening to AS 7018 which of At&t. Thus for a end user like me who is sitting in middle of village in Haryana, just 150Km’s away from k-root node, BSNL is routing traffic to UK on AboveNet network.
Next, I tried testing connectivity with rest of 3 root servers, and it seems like one other node – j-root servers with IP – 192.58.128.30.
J-Root node is also using anycasting (just like rest all root servers) and is hosted in Mumbai.
Here’s traceroute to j-root node.
As we see, it’s passing on traffic towards Paris via Tata Comm (AS4755 & AS6453). Here again BSNL should have listened annocement of 192.58.128.0/24 by AS 26415 which it should able to reach via niXi Mumbai exchange point, but it’s just messed up. This further gave me clue that Tata Comm is also not routing things properly.
Here’s a traceroute from IDEA Cellular 3G network which using Tata & Airtel for backbone internet connectivity.
and here is for J-root-node.
Well, clearly connectivity with 2 out of 4 root servers is screwed up in India.
Only i-root-node and f-root nodes seem OK.
With hope India will eventually have better connectivity, catch you later!