Thread: CONNECTION PROBLEMS + Reconnecting in Bridged Mode changes latency ? WHY ?

1st off - horrible latency fluctuations at random times during the day, slow speeds, sites not opening, torrent speeds awful, download/upload clogging/choking connection at these times, peak hour internet unusable, 2-8am period mostly unusable, 7am-8am 300-400ms above normal, packet loss, outages.

what's going on ?

underwater cable break ?
bsnl server monkey died inside a router ?

Why does disconnecting and reconnecting the BSNL BB connection affect latency so much ?

Same dns server, no other change, but latencies change every time i reconnect.

Does reconnecting choose a different routing path ?

Also; is anyone else finding random congestion/high latency/pings/packet loss at random times during the day ?

I'm getting 500ms right now and it's 5pm - hardly peak time anywhere.
What's going on ?

I called BSNL BB and the call center people are clueless about this issue.

Here's a screenshot showing how reconnecting affects latencies - the window on the left is to a US server and the window on the right is to an Australian server.


Uploaded with ImageShack.us



Next up : huge amount of connection choking at the slightest connection bandwidth usage - i just tried to upload the images above and my connection gets horribly choked - latencies shoot up to 500-600ms above normal (when this continues you see packet losses)
pings to a US server during upload to imageshack :

Code:

Reply from 63.241.193.18: bytes=32 time=437ms TTL=244
Reply from 63.241.193.18: bytes=32 time=437ms TTL=244
Reply from 63.241.193.18: bytes=32 time=437ms TTL=244
Reply from 63.241.193.18: bytes=32 time=437ms TTL=244
Reply from 63.241.193.18: bytes=32 time=437ms TTL=244
Reply from 63.241.193.18: bytes=32 time=421ms TTL=244
Reply from 63.241.193.18: bytes=32 time=515ms TTL=244
Reply from 63.241.193.18: bytes=32 time=687ms TTL=244
Reply from 63.241.193.18: bytes=32 time=1172ms TTL=244
Reply from 63.241.193.18: bytes=32 time=1999ms TTL=244
Reply from 63.241.193.18: bytes=32 time=2312ms TTL=244
Reply from 63.241.193.18: bytes=32 time=2077ms TTL=244
Reply from 63.241.193.18: bytes=32 time=484ms TTL=244
Reply from 63.241.193.18: bytes=32 time=468ms TTL=244
Reply from 63.241.193.18: bytes=32 time=468ms TTL=244
Reply from 63.241.193.18: bytes=32 time=484ms TTL=244
Reply from 63.241.193.18: bytes=32 time=484ms TTL=244
Reply from 63.241.193.18: bytes=32 time=484ms TTL=244
Reply from 63.241.193.18: bytes=32 time=484ms TTL=244
Reply from 63.241.193.18: bytes=32 time=484ms TTL=244
Reply from 63.241.193.18: bytes=32 time=500ms TTL=244
Reply from 63.241.193.18: bytes=32 time=500ms TTL=244
Reply from 63.241.193.18: bytes=32 time=499ms TTL=244
Reply from 63.241.193.18: bytes=32 time=484ms TTL=244
Reply from 63.241.193.18: bytes=32 time=500ms TTL=244
Reply from 63.241.193.18: bytes=32 time=484ms TTL=244

pings to a Australian server during upload to imageshack :

Code:

Reply from 202.6.141.219: bytes=32 time=452ms TTL=51
Reply from 202.6.141.219: bytes=32 time=452ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=452ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=436ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=624ms TTL=51
Reply from 202.6.141.219: bytes=32 time=953ms TTL=51
Reply from 202.6.141.219: bytes=32 time=1625ms TTL=51
Reply from 202.6.141.219: bytes=32 time=2281ms TTL=51
Reply from 202.6.141.219: bytes=32 time=2468ms TTL=51
Reply from 202.6.141.219: bytes=32 time=640ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=437ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=452ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=437ms TTL=51
Reply from 202.6.141.219: bytes=32 time=453ms TTL=51
Reply from 202.6.141.219: bytes=32 time=452ms TTL=51
Reply from 202.6.141.219: bytes=32 time=452ms TTL=51

traceroute to cnet.com (a server in west coast USA)

Code:

C:\>tracert www.cnet.com
Tracing route to gtm-rb-tron-xw.cnet-basic-performance.akadns.net [216.239.122.164]
over a maximum of 30 hops:
  1    12 ms    13 ms    12 ms  59.93.192.1
  2    46 ms    47 ms    47 ms  218.248.255.86
  3   173 ms   169 ms   169 ms  121.244.68.57.static-lvsb.vsnl.net.in[121.244.68.57]
  4   178 ms   177 ms   173 ms  203.197.33.130.static.vsnl.net.in [203.197.33.130]
  5   392 ms   394 ms   391 ms  59.163.16.134.static.vsnl.net.in [59.163.16.134]
  6   389 ms   402 ms   402 ms  if-11-0-7.mcore4.PDI-PaloAlto.as6453.net [207.45.213.153]
  7   411 ms     *      554 ms  if-3-0-0.mcore5.LAA-LosAngeles.as6453.net [216.6.86.10]
  8   419 ms   413 ms   413 ms  Vlan1147.icore2.LAA-LosAngeles.as6453.net [216.6.12.21]
  9   412 ms   412 ms   412 ms  192.205.35.129
 10   521 ms   517 ms   512 ms  cr2.la2ca.ip.att.net [12.122.129.30]
 11   523 ms   516 ms   519 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 12   518 ms   522 ms   522 ms  gar10.dlstx.ip.att.net [12.122.138.121]
 13   521 ms   505 ms   501 ms  12.87.121.22
 14   511 ms   518 ms   521 ms  c18-rb-gtm1-tron-xw-lb.cnet.com [216.239.122.164]
Trace complete.
C:\>

before anyone asks :
1) splitter is fine, same issue if i connect directly
2) line is fine, had lineman check and replace wires last month
3) changes dns servers is useless (+/- 10ms difference when i do)
4) no virus/trojan etc
5) modem is brand new (getting same problem with old bsnl modem)
6) problem happens at different times during the day.

PLEASE ADVISE
I AM FED UP WITH BSNL
IS THERE ANY WAY TO FIX THIS BULLSHIT

any one good with networking that can help me with this please

Try a complaint to Consumer Forum. This may bring any difference or atleast they will refund you your money for not giving you good connection.

Originally Posted by meetdilip

Try a complaint to Consumer Forum. This may bring any difference or atleast they will refund you your money for giving you good connection.

well the problem isn't really a local issue - it's affecting everyone in India using BSNL with the 59 series IP.

I'm just suprised with BSNL's total lack of status reporting and information - it's pretty obvious something very major is wrong.

And I actually want to fix the issue, monetary compensation really won't help.

O and about talking to the nodal/divisional manager - THEY NEVER EVEN PICK UP THE PHONE.

I am also getting pathetic connection in Kolkata in UL750.Shifting to Reliance the next week.I have suffered too much , but not more.

By disconnecting and reconnecting you may get a different gateway that is why change in latency.There may be hardware upgrade or maintenance activity going on.Me also got the same problem usually i get ping time around 90 ms to chennai or mumbai servers but when the problem occurred in my area the ping time was above 250 ms.But, the problem was solved automatically.No my ping times are as usual at around 90 ms.
After the problem over I am getting new gateway Ip. From this I concluded that there had been a hardware upgrade in the central office level.