horizonrays
Newbie
@ anurag ! as for port change !
there has been 8 diversion and 3 port changes by now , and i see no improvement !!
there has been 8 diversion and 3 port changes by now , and i see no improvement !!
BSNL Broadband routing problem seems to have been resolved
- Thread starter fabulous_chicken
- Start date
- Replies 47
- Views 17,630
horizonrays
Newbie
NEW UPDATE !
I went to meed sdo of my exchange and there multiple ports were checked and interstingly all ports had same problem , all ports faced ping drop upto 50% . and this problem is only faced by NIB 1 users and ports.
though sdo had no clue why it's happening , he said that it's happening because of some strike within bsnl.
to remedy this he said , kindly meet engineer at head exchange and ask him to configure new profile for NIB 2 . Then your problem will be resolved .
So i have question to my fellow member is anyone here who is on 59.xxx.xxx.xxx/NIB 1 . Are they too facing this problem ? Or it's just my local area ?
I went to meed sdo of my exchange and there multiple ports were checked and interstingly all ports had same problem , all ports faced ping drop upto 50% . and this problem is only faced by NIB 1 users and ports.
though sdo had no clue why it's happening , he said that it's happening because of some strike within bsnl.
to remedy this he said , kindly meet engineer at head exchange and ask him to configure new profile for NIB 2 . Then your problem will be resolved .
So i have question to my fellow member is anyone here who is on 59.xxx.xxx.xxx/NIB 1 . Are they too facing this problem ? Or it's just my local area ?
Routing issue is far from being resolved. I am barely getting 120 KBps on a 4 Mbps line
Tracing route to google.com [74.125.236.162] over a maximum of 30 hops:
1 4 ms 3 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 14 ms 11 ms 12 ms 117.194.64.1
4 11 ms 13 ms 9 ms 218.248.162.70
5 66 ms 65 ms 65 ms 218.248.255.10
6 * * 133 ms 59.163.207.81.static.chennai.vsnl.net.in [59.163.207.81]
7 131 ms * 131 ms 172.29.251.34
8 * * * Request timed out.
9 131 ms 141 ms 133 ms 115.114.142.137.static-Chennai.vsnl.net.in [115.114.142.137]
10 131 ms 133 ms 134 ms 121.240.1.50
11 133 ms 131 ms 132 ms 72.14.233.204
12 136 ms * 137 ms 209.85.240.145
13 134 ms 133 ms 133 ms maa03s16-in-f2.1e100.net [74.125.236.162]
Trace complete.
Tracing route to google.com [74.125.236.162] over a maximum of 30 hops:
1 4 ms 3 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 14 ms 11 ms 12 ms 117.194.64.1
4 11 ms 13 ms 9 ms 218.248.162.70
5 66 ms 65 ms 65 ms 218.248.255.10
6 * * 133 ms 59.163.207.81.static.chennai.vsnl.net.in [59.163.207.81]
7 131 ms * 131 ms 172.29.251.34
8 * * * Request timed out.
9 131 ms 141 ms 133 ms 115.114.142.137.static-Chennai.vsnl.net.in [115.114.142.137]
10 131 ms 133 ms 134 ms 121.240.1.50
11 133 ms 131 ms 132 ms 72.14.233.204
12 136 ms * 137 ms 209.85.240.145
13 134 ms 133 ms 133 ms maa03s16-in-f2.1e100.net [74.125.236.162]
Trace complete.
horizonrays
Newbie
@probuddha , you are on NIB 1 server or you are on nib 2 server .
as far as i know and have tested , NIB 2 is has having less routing problem than NIB 1 .
as far as i know and have tested , NIB 2 is has having less routing problem than NIB 1 .
zerosleeping
Regular
Tracing route to www.google.com [74.125.236.212]over a maximum of 30 hops: 1 46 ms 46 ms 46 ms 59.92.240.1 2 53 ms 54 ms 53 ms 218.248.255.66 3 88 ms 87 ms 90 ms 59.163.206.177.static.chennai.vsnl.net.in [59.163.206.177] 4 88 ms 89 ms 88 ms 121.240.1.50 5 88 ms 88 ms 89 ms 72.14.232.110 6 89 ms 89 ms 88 ms 209.85.240.147 7 89 ms 89 ms 89 ms maa03s17-in-f20.1e100.net [74.125.236.212]Trace complete.
On NIB-1
On NIB-1
horizonrays
Newbie
@zerosleeping , where are you from man ?
because here i am facing this issue for ages , even people at exchange on nib server are having same problem
because here i am facing this issue for ages , even people at exchange on nib server are having same problem
I am from 117.xxx ..so whatever that means, NIB II I guesshorizonrays said:
I have been having this routing issues for years now and the BSNL people either don't know how to resolve it or are just a bunch of lazy a***s doing nothing. I would have dumped BSNL long back, if I had another option in our area...but unfortunately I don't, so I am stuck with these idiots
BSNL is completely F***d UP right now, this is how their routing looks
C:>tracert youtube.com
Tracing route to youtube.com [74.125.236.64] over a maximum of 30 hops:
1 2 ms 1 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 27 ms 23 ms 23 ms 117.194.64.1
4 23 ms 21 ms 26 ms 218.248.162.70
5 407 ms 835 ms 936 ms 218.248.255.22
6 1119 ms 89 ms 125 ms 59.163.206.181.static.chennai.vsnl.net.in [59.163.206.181]
7 * * * Request timed out.
8 * * * Request timed out.
9 87 ms * 88 ms 115.114.142.137.static-Chennai.vsnl.net.in [115.114.142.137]
10 110 ms 89 ms 88 ms 121.240.1.50
11 87 ms 89 ms * 72.14.232.110
12 * 94 ms 91 ms 209.85.249.235
13 434 ms 124 ms * maa03s05-in-f0.1e100.net [74.125.236.64]
14 95 ms * 190 ms maa03s05-in-f0.1e100.net [74.125.236.64]
Trace complete.
I either have to give up my work...or move to a new place where there are other options available than BS-Anal
C:>tracert youtube.com
Tracing route to youtube.com [74.125.236.64] over a maximum of 30 hops:
1 2 ms 1 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 27 ms 23 ms 23 ms 117.194.64.1
4 23 ms 21 ms 26 ms 218.248.162.70
5 407 ms 835 ms 936 ms 218.248.255.22
6 1119 ms 89 ms 125 ms 59.163.206.181.static.chennai.vsnl.net.in [59.163.206.181]
7 * * * Request timed out.
8 * * * Request timed out.
9 87 ms * 88 ms 115.114.142.137.static-Chennai.vsnl.net.in [115.114.142.137]
10 110 ms 89 ms 88 ms 121.240.1.50
11 87 ms 89 ms * 72.14.232.110
12 * 94 ms 91 ms 209.85.249.235
13 434 ms 124 ms * maa03s05-in-f0.1e100.net [74.125.236.64]
14 95 ms * 190 ms maa03s05-in-f0.1e100.net [74.125.236.64]
Trace complete.
I either have to give up my work...or move to a new place where there are other options available than BS-Anal