Optical fiber FFTH 16Mbps -Speed

  • Thread starter Thread starter superasn
  • Start date Start date
  • Replies Replies 98
  • Views Views 19,910
Ah, seems like I've got a GPON device, not that I know in great detail the difference between EPON and GPON, from what I understand, GPON provides three Layer 2 networks: ATM for voice, Ethernet for data, and proprietary encapsulation for voice. EPON, on the other hand, employs a single Layer 2 network that uses IP to carry data, voice, and video. Now, I wonder why BSNL would employ two different technologies for FTTH. I'd have asked you to report your settings so that I could compare them with mine. Are you sure that there is no option to change the language ? Its highly unlikely that the guy who set your modem up would be knowing chinese.
 
Cool! Yeah, I'll probably contact them now for a test account where I can upload files to their server for download and distribution. Even if I can upload a 100 mb file to it in 5 mins I'm one happy camper. BTW learned so much about ISPs during this whole ordeal. Two days ago I would not even know the difference between an OLT from an ONT but now I've been repeating this stuff like a parrot all day long to 10 different engineers.. Routing, Graphs, Upstream, Tracert I know it all by heart now :D lol
It's an EPON remote device, that's what it says on it. The model number is AN5006-04.

@ superasn
Please keep us updated about the status of your problem.
 
Now, I wonder why BSNL would employ two different technologies for FTTH.

BSNL is like that. So is RIL, as it turns out.
 
@ superasn
Please keep us updated about the status of your problem.

A lot of people are looking into it right now but no progress :/ Apparently the CMD of BSNL has replied to me too (but I'm guessing it just some secretary or someone who is replying using his email).

Someone from Bangalore even logged into my comp via Teamviewer yest and did a lot of traceroute and other tests but last I heard from her is that "she isn't sure why there is so much latency in the network". At that moment I so wanted to link her to mgcarley's replies on how super inefficient their network is just to rub it in, but I refrained as long as they are co-operating :D

Anyway, lot of talk no result so far. But at least they're trying to fix it now. That is a good sign.
 
BSNL's network, despite being utilized at above recommended capacity, doesn't seem to be the problem - it seems to be their border gateways that are not configured correctly, and are sending US-bound traffic via Europe (causing high latency). This is what needs fixing. They've got connectivity to Global Crossing and Savvis and stuff, but they're sending only a small percentage of the traffic that way for reasons I can't even begin to guess.
 
A lot of people are looking into it right now but no progress :/ Apparently the CMD of BSNL has replied to me too (but I'm guessing it just some secretary or someone who is replying using his email).

Someone from Bangalore even logged into my comp via Teamviewer yest and did a lot of traceroute and other tests but last I heard from her is that "she isn't sure why there is so much latency in the network". At that moment I so wanted to link her to mgcarley's replies on how super inefficient their network is just to rub it in, but I refrained as long as they are co-operating :D

Anyway, lot of talk no result so far. But at least they're trying to fix it now. That is a good sign.

Basically BSNL doesn't have many routes to Tier 2 or Tier 3networks .. this makes its long latency ... even over a Fiber ..

try to ping to rcom.co.in which has a reliance site located in Mumbai .... over my ADSL line i get about 100 ms to respond ...

if u get the same responce time , think they have glued the ADSL traffic and Fiber traffic .. u can't do much about it .. seriously nothing can be done to it ...

In Europe , ISP's have a separate network for fiber to achieve those low latency ...
 


I don't think it is a DNS issue because when I hard code the IP address in my /etc/hosts file I still get slow speeds. The modem does not have any configuration page either (just one page in Chinese or Japenese and makes no sense whatsoever).
It's Simplified Chinese....pity I just started learning....anyway try and see if you can source an English firmware update from the makers ([email protected]). (Edit) If you need it....
 
BSNL's network, despite being utilized at above recommended capacity, doesn't seem to be the problem - it seems to be their border gateways that are not configured correctly, and are sending US-bound traffic via Europe (causing high latency). This is what needs fixing.

They've got connectivity to Global Crossing and Savvis and stuff, but they're sending only a small percentage of the traffic that way for reasons I can't even begin to guess.

I think there is no direct Undersea Cable to USA ... that the reason they re-route traffic through Europe.

if u try to ping to Los Angles .. traffic is through Satellite, Check it , there will no intermediate routes

Yeah u r correct they have connects to Global Crossing and some other Top European networks ...... mostly through TATA .. Even the european routes are worse ... Reliance is much better in that issue

I am not is puzzled to know that internal routing is such a worse. In a 300 ms response time ... i took about 180 ms to reached the external Gateway in chennai ...

And took about 50 ms to reach my local gateway ... this definately sick ....


traceroute 141.2.22.39
traceroute to 141.2.22.39 (141.2.22.39), 30 hops max, 40 byte packets using UDP
1 10.0.0.1 (10.0.0.1) 0.599 ms 0.552 ms 0.564 ms
2 117.199.240.1 (117.199.240.1) 54.275 ms 54.315 ms 55.732 ms
Unable to look up 218.248.172.170: Temporary failure in name resolution
3 218.248.172.170 55.411 ms 55.239 ms 56.287 ms
4 * 59.163.201.153.static.chennai.vsnl.net.in (59.163.201.153) 166.008 ms 165.821 ms
5 * * *
6 * * *
7 * * if-2-2.tcore2.MLV-Mumbai.as6453.net (180.87.38.2) 239.140 ms
8 if-6-2.tcore1.L78-London.as6453.net (80.231.130.5) 209.960 ms 208.246 ms 216.630 ms
9 Vlan704.icore1.LDN-London.as6453.net (80.231.130.10) 213.739 ms 231.163 ms 211.921 ms
10 te0-1-0-5.mpd21.lon13.atlas.cogentco.com (130.117.14.5) 211.814 ms te0-3-0-5.mpd22.lon13.atlas.cogentco.com (130.117.15.177) 212.952 ms te0-4-0-5.mpd22.lon13.atlas.cogentco.com (130.117.15.181) 219.832 ms
11 te0-0-0-0.mpd22.ams03.atlas.cogentco.com (130.117.50.165) 326.282 ms te0-3-0-0.mpd22.ams03.atlas.cogentco.com (130.117.1.205) 328.381 ms 154.54.60.202 (154.54.60.202) 334.656 ms
12 te0-2-0-4.mpd22.ams03.atlas.cogentco.com (130.117.49.62) 327.851 ms 335.775 ms 328.229 ms
13 149.6.138.206 (149.6.138.206) 316.808 ms 316.739 ms 315.872 ms
14 62.214.104.210 (62.214.104.210) 337.381 ms 149.6.138.206 (149.6.138.206) 302.195 ms 301.849 ms
15 62.214.104.210 (62.214.104.210) 397.504 ms 397.100 ms 62.214.110.78 (62.214.110.78) 327.437 ms
16 i3ED60B1E.versanet.de (62.214.11.30) 328.941 ms 329.300 ms 336.821 ms
17 i3ED60B1E.versanet.de (62.214.11.30) 328.622 ms 331.259 ms 331.430 ms
18 * * *
19 cb-jur-sammler-vc0.net.uni-frankfurt.de (141.2.252.48) 331.442 ms 337.238 ms *
20 cb-jur-sammler-vc0.net.uni-frankfurt.de (141.2.252.48) 340.822 ms 334.376 ms 334.356 ms
21 traminer.rz.uni-frankfurt.de (141.2.22.39) 321.719 ms 320.147 ms 327.634 ms
 
Basically BSNL doesn't have many routes to Tier 2 or Tier 3networks .. this makes its long latency ... even over a Fiber ..

BSNL *is* a Tier 2 network - Tata is the only provider with Tier 1 status in India. Furthermore, BSNL has some of the best peering (outside of India) - the rest for which it just relies on it's upstream (mainly Tata).

try to ping to rcom.co.in which has a reliance site located in Mumbai .... over my ADSL line i get about 100 ms to respond ...

Ouch. You should really look in to that if you're even within 1,000km of Mumbai. I get 6-7ms to rcom.co.in.

if u get the same responce time , think they have glued the ADSL traffic and Fiber traffic .. u can't do much about it .. seriously nothing can be done to it ...

In Europe , ISP's have a separate network for fiber to achieve those low latency ...

I hope you are only talking about the last mile (cabinet to user) and not suggesting that European ISPs utilize a completely separate network between the CO and the user!

European ISPs utilize the same fiber to get from the CO to the cabinets, from which only the cable between the home and the cabinet is different, and the Australian and NZ NBN networks currently being built are following that same standard: the new cabling being done merely replaces or supplements the copper portion of the network and plugs in to different equipment within that same cabinet.

Latency on DSL connections is usually an unavoidable result of DSL design: a line with error correction will introduce around 30ms of latency and without about 10-12ms, whereas with FTTx there is no changeover of modulation type required (ATM Ethernet) and so the latency is not there, otherwise both DSL and FTTx equipment (whether FTTB or FTTH) is interfacing with the same PON - it would be extremely cost INeffective not to, and telecom companies in Europe simply couldn't afford to (or the bean-counters wouldn't let them) have separate networks for different types of technology, especially when doing so isn't needed.

Source: My network designers are Swedish, I've lived in France and Finland and my FTTx equipment comes from a certain French company in the same brochure as their DSL equipment.

----------

I think there is no direct Undersea Cable to USA ... that the reason they re-route traffic through Europe.

if u try to ping to Los Angles .. traffic is through Satellite, Check it , there will no intermediate routes


What's wrong with you? There are plenty of undersea cables to the USA. Satellites do not have the capacity to handle the kind of traffic South-East Asia sends in that direction. MY traffic from Mumbai traverses one of these cables, but the traffic from this BSNL user doesn't for reasons only BSNL knows, and traffic to the US would end up in the THOUSANDS of milliseconds, not hundreds if it were.

Yeah u r correct they have connects to Global Crossing and some other Top European networks ...... mostly through TATA .. Even the european routes are worse ... Reliance is much better in that issue

GBLX is American. They also connect to Level3, which is also American (and the two have now merged, but networks and ASNs remain separate). Tata has significantly more capacity than Reliance (nearly 10x as much just in India), and any ISP in India will tell you that Reliance is the worst wholesale provider in India.

I am not is puzzled to know that internal routing is such a worse. In a 300 ms response time ... i took about 180 ms to reached the external Gateway in chennai ...

And took about 50 ms to reach my local gateway ... this definately sick ....


If you're getting 50 to your local gateway and 180ms to Chennai, something is seriously wrong with your connection. I'm in Mumbai and I'm getting 33-36ms to 59.163.201.153.static.chennai.vsnl.net.in. Granted, I'm not on ADSL but if I were it *should* be in the 50-60 range, tops.

Also, the routing problem described earlier in the thread was with Tata, not BSNL - which, from where I sit seems to be largely resolved.
 
And took about 50 ms to reach my local gateway ... this definately sick ....


There is an issue with the Chennai gateway currently which connects via VSNL (it's pathetic, it took me 3 hours to switch to a better gateway) - here's my results to the same IP address :

Tracing route to traminer.rz.uni-frankfurt.de [141.2.22.39]
over a maximum of 30 hops:

1
 

Back