Posts

Do connected interface ping?

And an interesting day full of bit frustrating drama. Today was “External viva” for Major Project at college. It went good with external teacher but “internal ones” tend to cause un-necessary issues. Quite a few people put personal egos and frustration on top priority to an extent that they violate their own points for which they are arguing. They go completely unethical in way they deal with world.

I am saying this with full responsibility for couple of teachers from my college who have completely lost some “fundamentals of life” as taught in childhood to most of us. Some key principles like staying cool & calm, being humble, making best possible use of time and just being good with everyone. In last 4 years they haven’t learn how to give respect & talk with sense and they expect students to be learning “technology” from them? What an absurd!

Lost sense of "engineering"

It’s late evening here in Radaur and I am sitting in my room with open door looking outside in dark. I wonder if darkness outside is more then darkness I see in our system. No, I am not referring to any routing glitch or bandwidth chock point but even more fundamental issue that is “Lost sense of Engineering” in current education age. It’s pretty hot weather out in my room. I will start this blog post with two interesting real life experiences from last few years.

Routes leaks by Indian ISPs for NIXI's routes

Interesting days as always. Recently I was handed over “Alumni form” from college. 
Mixed feelings. This brings me to conclusion that I somewhat missed college life but anyways that’s small price I paid for my high obsession with some long term ideas. (ok may be that explains why I don’t have a Facebook account? Stop asking me about it!)

Hard to come to any conclusion at this stage. 

Anyways post for today…

Tanzania Telecom leaking Telia routes to Tata

Last night I was looking at routing tables and saw a interesting case where for a specific route.

Here’s what I got from Tata’s AS6453 looking glass:

Router: gin-ldn-core4  
Site: UK, London, LDN  
Command: show ip bgp 117.219.227.229

BGP routing table entry for 117.219.224.0/20  
Bestpath Modifiers: deterministic-med  
Paths: (4 available, best #4)  
Multipath: eBGP  
17 18 19

33765 1299 3549 9829, (received-only)  
ix-3-1-2.core4.LDN-London. from ix-3-1-2.core4.LDN-London. (ix-3-1-2.core4.LDN-London.)  
Origin IGP, valid, external

4755 9829  
mlv-tcore2. (metric 3605) from l78-tcore2. (66.110.10.234)  
Origin IGP, valid, internal  
Community:  
Originator: 66.110.10.215

4755 9829  
mlv-tcore2. (metric 3605) from l78-tcore1. (66.110.10.237)  
Origin IGP, valid, internal  
Community:  
Originator: 66.110.10.215

4755 9829  
mlv-tcore2. (metric 3605) from ldn-mcore3. (ldn-mcore3.)  
Origin IGP, valid, internal, best  
Community:  
Originator: 66.110.10.215

The first route in table seems pretty weird. AS path is 33765 1299 3549 9829 i.e clearly AS33765 sitting in middle of AS6453 and AS1299. This must be a route leak since Tata AS6453 and Telia AS1299 are way too bigger then Tanzania telecom and hence there’s no possibility of Tata transitting via Tanzania telecom. Though issue seems for just one specific route for BSNL which Tanzania telecom is learning from Telia, which further is getting from Global Crossing AS3549 (one of upstreams of BSNL). 

IRINN & APNIC inetnum range confusion

Last week I saw an interesting post at APNIC mailing list about IRINN (recently formed NIR in Indian region). 

Poster Jimmy was concerned about IRINN’s netname

inetnum: 0.0.0.0 - 255.255.255.255  
netname: IRINN-BROADCAST-ADDRESSES  
descr: Broadcast addresses  
descr: These addresses cannot (should not) be routed on the Internet.  
country: IN  
admin-c: IH1-IN  
tech-c: IH1-IN  
status: ALLOCATED PORTABLE  
remarks: send spam and abuse report to info@irinn.in  
mnt-by: IRINN-HM  
mnt-irt: IRT-IRINNHM-IN  
mnt-lower: IRINN-HM  
changed: hostmaster2@irinn.in 20130420  
source: IRINN

As per first two lines entire IPv4 address space i.e 0.0.0.0/0 (ranging from 0.0.0.0 to 255.255.255.255) was put as IRINN-Broadcast while expected was IANA broadcast (since IANA sits on top in this RIR & NIR hierarchy).

Creating a cable for fast USB charging

When I was in US last time, I picked a nice charger with it’s own backup from Amazon. It’s PowerGen charger with a storage capacity of 8400mAh with two USB ports for output (one with 2Amps output and other with 600mA with 5V standard USB).

IMG_20130411_015748

This is a amazing product since 8400mAh is really huge amount power. My phone’s battery has a capacity of 1750mAh and theoretically speaking this can charge battery from 0 to full around 4 times. In practical experience I have tried for around 3 times during long flights. Never really needed to go beyond that point. The charging cable which came with this charger has something special - It’s a “charging only” cable without any data connection capability. The charging only cable carries only “e_lectrical connectivity_” via + and - wires without any data pins (D+ and D- shorted). The advantage is that charging speed with this cable was really fast and I really enjoyed using it with external charger as well as my iPad’s charger which has a 2A output (which brings 2A x 5V = 10W power). In theory these charging only cables give very fast charging because they don’t put USB data connection. A standard USB port on computer has power limits and device is signaled to pull more power via “shorted data pins”. Usually device is connected to 600mA or even less in data+charging mode, while such shorting brings power to max of port which is usually 1A for most of ports (and 2Amps for iPad charger). Unfortunately connector of cable which came with my powergen charger went pretty loose. Tonight I decided to make an extra data cable which was lying around into “charging only” cable by shorting it’s D+ and D- mins. It was pretty easy except that actual wires are really thin and I had slightly hard time in removing insulation without breaking them off.    

Transit at IXP & next-hop-self

And college started after pretty good holi holidays. Again having bit painful time due to hot weather and this is just start of summers. Well all I can hope is that there won’t be voltage issues in village again (like last time). And just to make sure on that part - I have put 2 RTI’s asking Power department about their preparation details. :)

Anyways coming on blog post topic for the day - the effect of “next-hop-self” at an IXP when there are peers as well as transit customers of a network. Just to be clear in start - this post will stick to technical side of it and without going into IXP policy side of it.

Dark spot in Global IPv6 routing

Fest time at college - Good since I get lot of free time to spend around looking at routing tables. It’s always interesting since last week was full of some major submarine cable cuts and has huge impact on Indian networks.

Anyways, an interesting issue to post today about Global IPv6 routing . There are “dark spots” in global IPv6 routing because of peering dispute between multiple tier 1 ISPs involving Hurricane Electric (AS6939) & Cogent Communications (AS174).  What’s happening here is that both tier 1 providers failed to reach on agreement to keep peering up in case of IPv6. This has resulted in parts of global IPv6 internet where packets from one network (and it’s downstream) can’t reach other network or their downsteam singled hommed networks. 

SMW4 Cable outage

Today a friend from Pakistan informed about SMW4 outage. He reported about issues in Pakistan.

It seems like SMW4 is damaged near Egypt and that is what causing high load on East Asian routes giving pretty high latency.

I am at my home and sitting BSNL’s network and latency with Europe has jumped terribly to 700-800ms. Right now I do not see a direct route to Europe and it’s rather taking East Asia > US > Europe routes right now on other cable networks.

BSNL routing tables and upstreams

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:

  1. 117.192.0.0/18
  2. 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.85.40.15 0 3267 174 6453 4755 9829 9829 9829 i  
* 129.250.0.11 6 0 2914 6453 6453 4755 9829 9829 9829 i  
* 128.223.253.10 0 3582 3701 3356 6453 4755 9829 9829 9829 i  
* 4.69.184.193 0 0 3356 6453 4755 9829 9829 9829 i  
* 209.124.176.223 0 101 101 3356 6453 4755 9829 9829 9829 i  
* 69.31.111.244 3 0 4436 2914 6453 6453 4755 9829 9829 9829 i  
* 207.46.32.34 0 8075 6453 4755 9829 9829 9829 i  
* 66.59.190.221 0 6539 6453 4755 9829 9829 9829 i  
* 12.0.1.63 0 7018 6453 4755 9829 9829 9829 i  
* 208.74.64.40 0 19214 2828 6453 4755 9829 9829 9829 i  
* 203.181.248.168 0 7660 2516 6453 4755 9829 9829 9829 i  
* 66.185.128.48 111 0 1668 6453 4755 9829 9829 9829 i  
* 134.222.87.1 0 286 6453 4755 9829 9829 9829 i  
* 157.130.10.233 0 701 6453 4755 9829 9829 9829 i  
* 114.31.199.1 0 0 4826 6939 1299 6453 4755 9829 9829 9829 i  
* 89.149.178.10 10 0 3257 6453 4755 9829 9829 9829 i  
* 154.11.98.225 0 0 852 3561 6453 4755 9829 9829 9829 i  
* 202.249.2.86 0 7500 2497 6453 4755 9829 9829 9829 i  
* 154.11.11.113 0 0 852 3561 6453 4755 9829 9829 9829 i  
* 144.228.241.130 0 1239 6453 4755 9829 9829 9829 i  
* 217.75.96.60 0 0 16150 1299 6453 4755 9829 9829 9829 i  
* 207.172.6.20 0 0 6079 3356 6453 4755 9829 9829 9829 i  
* 206.24.210.102 0 3561 6453 4755 9829 9829 9829 i  
* 195.66.232.239 0 5459 6453 4755 9829 9829 9829 i  
* 208.51.134.254 2523 0 3549 6453 4755 9829 9829 9829 i  
* 207.172.6.1 0 0 6079 3356 6453 4755 9829 9829 9829 i  
* 216.218.252.164 0 6939 1299 6453 4755 9829 9829 9829 i  
* 203.62.252.186 0 1221 4637 6453 4755 9829 9829 9829 i  
*> 66.110.0.86 0 6453 4755 9829 9829 9829 i  
* 164.128.32.11 0 3303 6453 4755 9829 9829 9829 i  
* 202.232.0.2 0 2497 6453 4755 9829 9829 9829 i

Routing table for 117.192.0.0/20: