BSNL FTTH Static IP User

dhogaivannan

dhogaivannan

Messages
22
Location
Erode
ISP
BSNL FTTH
As said above, I'm paying like ~100rs extra per month for my FTTH. I thought routing would be fixed after getting a Static IP but alas, it has good route randomly in day basis. Is there anyway to notify BSNL to provide better permanent routing for given static IP address? If so, where should I get touch with or file a ticket about this?

PS: Looks like my upload speed are fixed to ~40mbps for last few weeks
 
You'd need to get it escalated to the L2/L3 network team, but there is no direct way to do that I suppose. You could try opening a complaint ticket and escalating it through Twitter. Also maybe get it escalated through the exchange.

Personally, atleast in Kerala I find BSNLs routing pretty good actually. I get sub 20 ms response times to Google, sub 50 ms to Singapore.
 
Routing is pretty bad from tn, can you please send me your speed test results to Vodafone Mumbai as well as for sg, I'm getting 90+ ms to sg usually it's around 55-60
 
I only have remote access atm, here are the pings to various IP addresses.

Code: 
root@LEDE:~# ping -c 4 speedtest-sgp1.digitalocean.com
PING speedtest-sgp1.digitalocean.com (159.89.192.182): 56 data bytes
64 bytes from 159.89.192.182: seq=0 ttl=56 time=45.652 ms
64 bytes from 159.89.192.182: seq=1 ttl=56 time=45.673 ms
64 bytes from 159.89.192.182: seq=2 ttl=56 time=46.079 ms
64 bytes from 159.89.192.182: seq=3 ttl=56 time=45.413 ms

--- speedtest-sgp1.digitalocean.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 45.413/45.704/46.079 ms

root@LEDE:~# ping -c 4 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: seq=0 ttl=57 time=14.504 ms
64 bytes from 1.1.1.1: seq=1 ttl=57 time=13.772 ms
64 bytes from 1.1.1.1: seq=2 ttl=57 time=14.040 ms
64 bytes from 1.1.1.1: seq=3 ttl=57 time=14.384 ms

--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 13.772/14.175/14.504 ms

root@LEDE:~# ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=56 time=17.042 ms
64 bytes from 8.8.8.8: seq=1 ttl=56 time=16.308 ms
64 bytes from 8.8.8.8: seq=2 ttl=56 time=16.500 ms
64 bytes from 8.8.8.8: seq=3 ttl=56 time=16.815 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 16.308/16.666/17.042 ms

root@LEDE:~# ping -c 4 google.com
PING google.com (216.58.200.142): 56 data bytes
64 bytes from 216.58.200.142: seq=0 ttl=56 time=15.272 ms
64 bytes from 216.58.200.142: seq=1 ttl=56 time=15.447 ms
64 bytes from 216.58.200.142: seq=2 ttl=56 time=15.712 ms
64 bytes from 216.58.200.142: seq=3 ttl=56 time=15.044 ms

--- google.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 15.044/15.368/15.712 ms

root@LEDE:~# ping -c 4 speedtest.singapore.linode.com
PING speedtest.singapore.linode.com (139.162.23.4): 56 data bytes
64 bytes from 139.162.23.4: seq=0 ttl=55 time=44.938 ms
64 bytes from 139.162.23.4: seq=1 ttl=55 time=45.319 ms
64 bytes from 139.162.23.4: seq=2 ttl=55 time=45.468 ms
64 bytes from 139.162.23.4: seq=3 ttl=55 time=44.910 ms

--- speedtest.singapore.linode.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 44.910/45.158/45.468 ms
root@LEDE:~#
 

Code: 
root@LEDE:~# ping -c 4 185.10.83.10
PING 185.10.83.10 (185.10.83.10): 56 data bytes
64 bytes from 185.10.83.10: seq=0 ttl=48 time=189.374 ms
64 bytes from 185.10.83.10: seq=1 ttl=48 time=189.461 ms
64 bytes from 185.10.83.10: seq=2 ttl=48 time=189.510 ms
64 bytes from 185.10.83.10: seq=3 ttl=48 time=189.831 ms

--- 185.10.83.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 189.374/189.544/189.831 ms
root@LEDE:~#

@airforce ^^
 
After a power failure, got an IP address from a different subnet, the pings have slightly gone up.

Code: 
root@LEDE:~# ping -c 4 185.10.83.10
PING 185.10.83.10 (185.10.83.10): 56 data bytes
64 bytes from 185.10.83.10: seq=0 ttl=54 time=195.403 ms
64 bytes from 185.10.83.10: seq=1 ttl=54 time=195.577 ms
64 bytes from 185.10.83.10: seq=2 ttl=54 time=195.894 ms
64 bytes from 185.10.83.10: seq=3 ttl=54 time=195.938 ms

--- 185.10.83.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 195.403/195.703/195.938 ms

root@LEDE:~# mtr -w 185.10.83.10
Start: Mon Jun  3 17:32:15 2019
HOST: LEDE                                       Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.212.172.1                                0.0%    10    2.1   1.9   1.2   3.1   0.3
  2.|-- static.ill.218.248.125.2/24.bsnl.in         0.0%    10    2.1  89.1   2.1 163.6  72.8
  3.|-- 218.248.255.6                              60.0%    10    2.1   2.0   1.7   2.6   0.0
  4.|-- 115.110.161.85.static.vsnl.net.in           0.0%    10   14.6  15.9  14.2  27.6   4.0
  5.|-- 172.31.47.5                                 0.0%    10   42.4  41.8  41.4  42.4   0.0
  6.|-- ix-ae-0-100.tcore2.mlv-mumbai.as6453.net    0.0%    10   72.0  72.0  71.6  72.5   0.0
  7.|-- ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0
  8.|-- if-ae-5-2.tcore1.wyn-marseille.as6453.net   0.0%    10  182.9 183.3 182.8 183.8   0.0
  9.|-- if-ae-30-2.tcore1.fnm-frankfurt.as6453.net  0.0%    10  186.3 186.7 186.2 187.9   0.0
 10.|-- if-ina-2.tcore1.fr0-frankfurt.as6453.net    0.0%    10  183.9 187.4 182.8 209.4   8.6
 11.|-- if-ae-45-2.tcore1.fr0-frankfurt.as6453.net  0.0%    10  186.1 185.9 185.4 186.5   0.0
 12.|-- te0-0-0-0-pr2.fra.router.colt.net           0.0%    10  154.6 154.7 154.0 156.3   0.5
 13.|-- xe11-3-0-sar8.mad.router.colt.net           0.0%    10  187.9 198.8 187.2 262.8  24.8
 14.|-- xe11-3-0-sar8.mad.router.colt.net           0.0%    10  208.2 196.0 187.2 214.7  11.1
 15.|-- 213.27.224.226                              0.0%    10  193.2 192.6 192.2 193.2   0.0
 16.|-- 10.83.10.185.in-addr.arpa.ghofi.net         0.0%    10  196.0 195.6 195.0 196.2   0.0
root@LEDE:~#
 
Here's my traceroute from Win10 on BSNL FTTH in Pune, if it matters:

Code: 
PS C:\WINDOWS\system32> tracert 185.10.83.10

Tracing route to 10.83.10.185.in-addr.arpa.ghofi.net [185.10.83.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     1 ms    <1 ms    <1 ms  192.168.1.254
  3     2 ms     2 ms     2 ms  103.77.240.1
  4     1 ms     2 ms     1 ms  218.248.164.97
  5     4 ms     2 ms     4 ms  218.248.164.122
  6     *        *        6 ms  218.248.235.157
  7     *        *        *     Request timed out.
  8     6 ms     6 ms     6 ms  aes-static-041.105.144.59.airtel.in [59.144.105.41]
  9   124 ms   125 ms   130 ms  182.79.178.58
 10   134 ms   129 ms   128 ms  182.79.141.205
 11   129 ms   128 ms   129 ms  182.79.242.28
 12   127 ms   127 ms   126 ms  182.79.149.99
 13   127 ms   127 ms   127 ms  linx-ge7-0-oscar.lon.router.colt.net [195.66.224.49]
 14   150 ms   151 ms   171 ms  xe11-3-0-sar8.MAD.router.colt.net [212.74.66.86]
 15   150 ms   149 ms   149 ms  xe11-3-0-sar8.MAD.router.colt.net [212.74.66.86]
 16   158 ms   158 ms   158 ms  213.27.224.226
 17   160 ms   160 ms   160 ms  10.83.10.185.in-addr.arpa.ghofi.net [185.10.83.10]

Trace complete.
 
@varkey @vishalrao thanks a lot , we r having 130 customers in bsnl FTTH in our town. Started October last year . So many issues faced but improved a lot . Especially voice service unstable all the time, our SSA nib jto unlce is very stubborn old school who doesn't care about what customer facing , he will keep on telling what he knows
 

Similar threads

thorbhau
Airtel is not giving static ip
Replies
14
Views
1,830
Brahmastra
S
Airtel Xstream Static IP to host websites
Replies
3
Views
993
utkarshy
bnee
How to configure Bsnl ftth Voip on softphone? Unable to ping SIP in cmd.
Replies
7
Views
3,600
local_testnet
Y
BSNL FTTH Syrotech bridge mode - working configuration
2
Replies
28
Views
4,891
!!..PD..!!
Top