Slow speed on BSNL Fiber

  • Thread starter Thread starter Xtinction
  • Start date Start date
  • Replies Replies 81
  • Views Views 10,270
I already had the WLAN security config the way it is mentioned in that PDF. So I got curious and changed it to WPA2 only last night. Everything was fine, no change. So I reverted to my previous config again and went to sleep. Now today the Shield would connect but couldn't detect internet. These ONTs are just something else. :ROFLMAO:
 
1600604630094.png


1600605074511.png

1600605812824.webp


Guys I'm from Jammu, I took this connection in April, and from April-Sept both download and upload connection were consistent (40Mbps).

Earlier: With Lan Connection: Around 60Mbps; With Wifi: ~40-50Mbps (Upload&Download almost same)

Since a week I'm experiencing very low download speed, is there any fault in my device(except temperature).

Earlier: With Lan Connection: Around 7Mbps; With Wifi: ~5Mbps (Upload reaching 40Mbps in both Lan & Wifi)

I'm registering complaint on self-care bsnl, but it is getting mark as resolved within few hours. Can any Jammu citizen shed some light on this or anyone who knows how to get this fixed. Thank you
 
Last edited:
So many problems of slow download speed, since BSNL has introduced the 3 new plans. This is a lack of preparedness from BSNL before trying to hit 6s in every ball. Hope things get normal quickly.
 
Am on 117.194.73.xxx now and ping to 8.8.8.8 is
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=48ms TTL=116
Reply from 8.8.8.8: bytes=32 time=48ms TTL=116
Reply from 8.8.8.8: bytes=32 time=48ms TTL=116
Reply from 8.8.8.8: bytes=32 time=48ms TTL=116
Before rebooting I was on 117.194.211.xxx and ping was
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=59ms TTL=112
Reply from 8.8.8.8: bytes=32 time=63ms TTL=112
Reply from 8.8.8.8: bytes=32 time=59ms TTL=112
Reply from 8.8.8.8: bytes=32 time=60ms TTL=112
Same with 1.1.1.1
Before

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=83ms TTL=49
Reply from 1.1.1.1: bytes=32 time=92ms TTL=49
Reply from 1.1.1.1: bytes=32 time=84ms TTL=49
Reply from 1.1.1.1: bytes=32 time=83ms TTL=49
After

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=56ms TTL=56
Reply from 1.1.1.1: bytes=32 time=56ms TTL=56
Reply from 1.1.1.1: bytes=32 time=56ms TTL=56
Reply from 1.1.1.1: bytes=32 time=56ms TTL=56
Been observing this pattern since the past few days. Some IP ranges have better latency.
 
Back