And a blog post after a while. Last few months went busy with RPKI. After my last post about RPKI and the fact that India was lacking a little bit on RPKI ROA front, we started with a major push by a set of like-minded folks like us. For now, Indian signed table has jumped from 12% since Aug to 32% now in Oct. Detailed graphs and other data can be found here on the public Grafana instance.
In terms of absolute percentage, India now has the highest number of absolute signed prefixes in this region. 13972 Indian prefixes have a valid ROA and nearest to that is Taiwan at 6824. Though 13972 results in just 32% of the Indian table while 6824 results in 91% of Taiwanese table. So a long way to go for us.
If you are a network operator in India and reading this, consider joining our RPKI webinar which is planned at 3 pm (IST) on 18th Nov 2020. You can register for the event here. Or buzz me to talk about RPKI!
Besides RPKI push I also caught up with Covid19 along with family members. Luckily for us, it went fine and wasn’t that painful. The impact was mild and everyone has recovered. Phew!
I hope readers of this blog post are well.
TraceroutePing in Smokeping
Coming to the topic for today’s blog post. I recently came across this excellent Smokeping plugin which solves a very interesting problem. There are often nodes we see in the traceroute/MTR which is either not routed or simply block ICMP/TCP/UDP packets which are addressed to them. This can include routers which have a pretty harsh firewall dropping everything addressed to them as well as cases where we have IX or any other non-routed IP in the traceroute. It becomes tricky to measure latency to those. Someone used the simple idea of incremental TTLs as used in traceroute to get a reply from these middle nodes of “TTL time exceeded error” and based on that a way to plot latency.
Let’s look at a real-world case: One of ISP serving my home is IAXN AS134316 and they peer with my ex-employers network Spectra AS10029 at Extreme IX in Delhi. Let’s see how traceroute to Spectra’s anycast DNS looks from my home.
traceroute -P icmp 22.214.171.124 traceroute to 126.96.36.199 (188.8.131.52), 64 hops max, 72 byte packets 1 router01.rtk.anuragbhatia.com (172.16.0.1) 2.818 ms 1.876 ms 4.274 ms 2 10.10.26.6 (10.10.26.6) 4.258 ms 4.301 ms 5.953 ms 3 10.10.26.5 (10.10.26.5) 5.490 ms 5.916 ms 5.257 ms 4 10.10.26.29 (10.10.26.29) 11.349 ms 9.246 ms 9.430 ms 5 as10029.del.extreme-ix.net (184.108.40.206) 10.628 ms 8.802 ms 9.609 ms 6 resolver1.anycast.spectranet.in (220.127.116.11) 8.446 ms 9.113 ms 10.699 ms
Now hop 5 here is likely Spectra’s Delhi router’s interface which has Extreme IX IP – 18.104.22.168. Let’s see what we get when we ping it.
ping -c 5 22.214.171.124 PING 126.96.36.199 (188.8.131.52): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 --- 184.108.40.206 ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss
I cannot ping it. Let’s look at the trace to it to see where it drops.
traceroute -P icmp 220.127.116.11 traceroute to 18.104.22.168 (22.214.171.124), 64 hops max, 72 byte packets 1 router01.rtk.anuragbhatia.com (172.16.0.1) 3.196 ms 1.790 ms 4.421 ms 2 10.10.26.6 (10.10.26.6) 5.514 ms 3.624 ms 5.323 ms 3 10.10.26.5 (10.10.26.5) 5.252 ms 4.043 ms 3.671 ms 4 * * * 5 * * * 6 nsg-static-126.96.36.199-airtel.com (188.8.131.52) 14.221 ms 10.963 ms 11.574 ms 7 184.108.40.206 (220.127.116.11) 146.531 ms 147.899 ms 146.065 ms 8 * * * 9 * * * 10 * * *
Now, this is an interesting and not very unexpected result. Basically, my ISP – IAXN AS134316 does not has any route in it’s routing table for 18.104.22.168 and hence passing it to default route towards it’s upstream Airtel. BGP wise IAXN is not supposed to have any route belonging to IX peering IP anyways and that’s expected. Likely their router which peers with Extreme IX is different from the router which serves me and is possibly missing sharing of connected routes via IGP and hence the unexpected path. As soon as traffic hits Airtel router with a full routing table & no default route, it drops it.
In this setup, I cannot reach Spectra’s interface connected to the Extreme IX (22.214.171.124) directly if I try to send packets to it. But I do know from the first trace that it comes in middle when I try to send packets to 126.96.36.199. This option can be used where packets can be sent with incremental TTL and latency can be measured and even graphed. This concept can be used even if there’s a use of private IPs before the destination.
So this goes to my Probe config
+ TraceroutePing binary = /usr/bin/traceroute # mandatory binaryv6 = /usr/bin/traceroute6 forks = 5 offset = 50% step = 300 timeout = 15
and this goes to my Target’s config
++SpectraExtremeIXInterface probe = TraceroutePing menu = Spectra via Extreme IX title = Spectra via Extreme IX host = 188.8.131.52 desthost = 184.108.40.206 maxttl = 15 minttl = 5 pings = 5 wait = 3
How it works?
A reminder on working on traceroute!
Remember the concept of TTL in IP routing. TTL is time to live and basically whenever the router passes the packets, it decreases TTL by 1 and when TTL reaches 0, the router just drops it. This ensures loops aren’t as dangerous in layer 3 as we see in layer 2. Now when a router drops packets with TTL 0, it replies back to the source saying “TTL exceeded” and the reply packets have the router’s source IP address. That way traceroute can send 1st packet with TTL 1, 1st router in the chain gets it, reduces TTL by 1 and (now that TTL is 0) drops it with a reply from its source IP. Next, another packet is sent with TTL 2 and so on.
Note: Thanks to networking folks from OVH Cloud who replied me with this probe on Twitter. It wasn’t what I was looking for but quite fascinating and useful!
Time to go back into the routing world! 🙂