Huge packet-loss on the route and spotty link

  • Thread starter Thread starter pufl
  • Start date Start date
  • Replies Replies 21
  • Views Views 2,453
Messages
8
Location
TS
ISP
BSNL
I have finally bit the bullet and have subscribed to the 40Mbps 645 plan with plans to upgrade if things work-out. They have finally laid the cable and gave the fiber connection a day ago with the AONT-100 GPON ONU in Hyderabad. The modem configure to be in bridge mode fronted by Nighthawk X6S on its latest firmware. The connection is over Ipv4 backed by Google DNS and I get allocated the 117.200.x.x IP range. While I do seem to get the promised 40Mbps up/down on speedtest and fast.com, my connection is quite spotty with disconnect blips happening every 3-5 seconds. This makes any Facetime call / RDP session almost unusable which, quite frustrating. Even a remote teamviewer connection is spotty, with disconnects/reconnects every few seconds. I have run ping tests on various AWS regions, and I saw 2-3 seconds of good RTT followed by 2-3 seconds of very high RTTs ranging from around 300ms in DigitalOcean BLR, to around 2000ms for a node based in New York city.

I have set MTU to 1460 which seems to be the sweet spot based on my pings to google DNS. I was thinking of why so many disconnect blips a.k.a packet drops (?) are happening on my connections. I ran MTR on a bunch of nodes and regions, and it doesnt look good so far with a ton of packet loss on its path. Almost all my out-of-country mtr requestes get routed through NCR region (218.248.235.141, 218.248.235.142, 218.248.235.xxx) and that is where there is a obscene level of packet loss happening.

Please help!

My questions:

Does this happen to folks in Hyderabad and other parts of the country experience this as well ?
Am I all interpreting this wrong ?
What could be done and how can I approach this issue with BSNL ?

I am attaching all the screen shots I have for context.

cc: @varkey @Ameen @JB700 @Realme @popcorn @Dark_Nate
 

Attachments

  • MtrBos.webp
    MtrBos.webp
    76 KB · Views: 302
  • MtrBsnlMaa.webp
    MtrBsnlMaa.webp
    43.2 KB · Views: 266
  • MtrBsnlNcr.webp
    MtrBsnlNcr.webp
    48 KB · Views: 266
  • MtrCloudflareDns.webp
    MtrCloudflareDns.webp
    68.8 KB · Views: 310
  • MtrGoogleDns.webp
    MtrGoogleDns.webp
    52.1 KB · Views: 257
  • MtrLA.webp
    MtrLA.webp
    82.9 KB · Views: 242
  • MtrLon.webp
    MtrLon.webp
    75.9 KB · Views: 260
  • MtrMum.webp
    MtrMum.webp
    68.4 KB · Views: 262
  • MtrQuadGermany.webp
    MtrQuadGermany.webp
    76.9 KB · Views: 285
  • MtrSIN.webp
    MtrSIN.webp
    60.3 KB · Views: 257
Attaching ping responses to various steam nodes
 

Attachments

  • MtrVodaMaa.webp
    MtrVodaMaa.webp
    59.8 KB · Views: 246
  • PingDC.webp
    PingDC.webp
    97.2 KB · Views: 240
  • PingDubai.webp
    PingDubai.webp
    112.6 KB · Views: 253
  • PingEurope.webp
    PingEurope.webp
    111.7 KB · Views: 253
  • PingSeattle.webp
    PingSeattle.webp
    94 KB · Views: 286
  • PingSIN.webp
    PingSIN.webp
    142.6 KB · Views: 250
loss at intermediate hops are fine because you won't be directly contacting these servers ( 218.248.235.x)

The pings you are getting are around what you should be getting . I'm getting ~50ms ping to 218.248.235.141 which means the servers are likely not located in NCR but likely somewhere in South India.

According to Complete IP Address Details for 218.248.235.141 it seems to be in Bangalore but geolocation isn't always accurate.

I will try to read further into your traceroutes.

Edit 1:

This time I used RIPE Atlas, 218.248.235.141 does seem to be in Bangalore

 
Last edited:
This is what mtr to 23.36.39.156 gives me from ACT

Code:
$ mtr 23.36.39.156 -w
Start: 2020-07-23T20:22:32+0530
HOST: desktop                                            Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- _gateway                                            0.0%    10    0.3   0.2   0.2   0.3   0.0
  2.|-- broadband.actcorp.in                                0.0%    10    1.2   1.4   1.2   2.3   0.3
  3.|-- broadband.actcorp.in                               40.0%    10    1.6   4.9   1.6  21.1   7.9
  4.|-- 14.141.145.5.static-Bangalore.vsnl.net.in           0.0%    10    1.9   3.5   1.9  16.5   4.6
  5.|-- 172.31.29.245                                       0.0%    10   19.5  19.0  18.4  20.2   0.7
  6.|-- ix-ae-0-100.tcore1.mlv-mumbai.as6453.net            0.0%    10   13.6  14.5  13.3  16.2   1.1
  7.|-- if-ae-5-2.tcore1.wyn-marseille.as6453.net          10.0%    10  136.4 136.6 136.0 138.2   0.9
  8.|-- if-ae-8-1600.tcore1.pye-paris.as6453.net           90.0%    10  135.9 135.9 135.9 135.9   0.0
  9.|-- if-ae-11-2.tcore1.pvu-paris.as6453.net              0.0%    10  140.4 140.6 140.4 141.4   0.3
 10.|-- 80.231.153.202                                      0.0%    10  135.2 137.3 135.2 153.1   5.6
 11.|-- et-0-0-1.cr1-bos1.ip4.gtt.net                       0.0%    10  229.6 217.0 214.9 229.6   4.5
 12.|-- ip4.gtt.net                                         0.0%    10  216.3 253.9 215.1 412.2  66.2
 13.|-- a23-36-39-156.deploy.static.akamaitechnologies.com  0.0%    10  203.1 203.3 203.1 203.5   0.1
 
@pufl I would suggest starting diagnosing at your end first before going to the ISP.

Try connecting your PC directly to ONT and use the ONT for temporarily creating the PPPoE connection. This will let you know that the issue is either in the ONT or on the BSNL network
 
@JB700 Fair enough, I have the ONT currently configured in bridge mode (the bsnl guy did it) and now I cant access its UI anymore on 192.168.1.251. You think plugging in the ONT directly into my machine give me that access ?

Also, what should I specifically be looking at once am in their interface you think ?
 


@pufl You'll have to use static IP settings in Windows on your desktop and put default gateway as 192.168.1.251 then you should be able to access your ONT.

Once you are in ONT, you should enable NAT if its disabled, go to WAN section of ONT and set it to PPPoE and enter your creds. On BSNL you will also need to enter your VLAN I think, it could be configured already on the ONT by BSNL.
 
it seems like people who are all having the private ip gateways facing this issue.
 
Here is the another one. same issue with private gateway but having a public ip. i think this problem persist in BSNL for a long time (from the month of march). Hope there is upgradration going on in bsnl end region by region
 

Back