Routing problem with specific dynamic mtnl ip prefix 182.60.0.0/20

  • Thread starter Thread starter Orion Pax
  • Start date Start date
  • Replies Replies 16
  • Views Views 126
I was looking through the communities of the routes (as I have nothing better to do), and I noticed the following:
Community with Cogent on path: 174:22013 (This is a US-originated route, with region stating as LAX.)
Community with Tata on path: 6453:1000, 1300 & 1303. (LAX as well)

For both, it means that these ISPs first learned this route from LAX, which means any route to anywhere will hit LAX to reach BSNL. The question is why...
 
Only BSNL and God knows why they receive these Tier 1 handoffs from the US rather than the nearest Singapore or for AS6453 via BOM or MAA. @Anurag Bhatia has already mentioned this in IBF or maybe in his blog if I remember correctly.

@Lolita_Magnum Do you think we can report this handoff issue to NIB or the BSNL BM team? Aren’t they aware of this already? Or is it more like if everything is working they prefer not to touch anything? Cause outbound of these T1 is more optimal in BSNL
 
Last edited:
Hard to say without a more in-depth look, but yes, checking with BSNL would be a start. That is if they bother helping.

The simplest no-headache solution if the only concern is AWS is to just get the premium network option.
If money's tight, then the alternative would be to use Cloudflare WARP with AWS.
 
This has the same problem. Its only saving grace is Jio, which is ensuring on some routes the routing is not ruined.
 
You must log in or register to reply here.
Back