Anyone on Asianet Broadband Fiber here?

[steam]

@philip i have a found a bridge mode setting in the modem page. I also found something peculiar. High number of error and abandon. I'm not entirely sure what it is. @varkey @Sammy Any ideas?

 

[Sammy]

@steam You should ask for a replacement modem/ONT. Did you get a Hathway branded one or Asianet branded one?

 

[steam]

@Sammy I got a genexis modem. Seems sketchy enough haha!

 

[varkey]

@steam Do you see better performance after the ONT device is rebooted? Also, please check the ping times to the ONT, while you are actively using the internet, perhaps do a speed test or download a file or play a video on youtube. There appears to be a lot of jitter as well.

Anyway, these ISP provided network devices are mostly crap, I'd recommend in getting a decent wireless router, the TP-Link Archer C6 is good for the price, well balanced.

Since its PON based, unless they have over-provisioned the link, you shouldn't see much last mile issues, however, if the issue is further upstream like congestion at their main gateway or upstream providers (due to them paying for much less than the requirement), then nothing we do at our end would help.

 

[steam]

@varkey when I restart it does become stable but only for a very short duration. (Under 1 minute) and goes back to being the mess it is.

Oddly enough, the network is very stable in the early morning hours with 2 ms jitter and 17 ms latency to Google DNS. The issue starts after 11am when (I'm speculating here) everyone starts using their networks for whatever reason

 

[varkey]

I see. In that case, it is unlikely to be the ONT device. It might just be congestion with increased traffic in your city/town.

 

---

[steam]

The current latency of network (6.40 am). Also attached a traceroute. The router has not been restarted. It's been on since yesterday.

@varkey Do you think this can be solved at their end? They're testing my patience at this point.

Guess i'll just hold on to it until Sunday and if the problem persists I'll cancel the connection. Also, word of advice to people on the lookout for fiber connection: STEER CLEAR OF ASIANET. Their service is less reliable than some dial up connections from 2005.

 

[vu3knb]

@varkey when I restart it does become stable but only for a very short duration. (Under 1 minute) and goes back to being the mess it is.

Oddly enough, the network is very stable in the early morning hours with 2 ms jitter and 17 ms latency to Google DNS. The issue starts after 11am when (I'm speculating here) everyone starts using their networks for whatever reason

Asianet is following KeralaVision I guess. I had the post "11am" trauma with KV in March and April. My remote work from home server never used to respond after 11 am till 5pm or so. Disconnected KV and moved to BSNL FTTH , all my issues got sorted. Thanks to BSNL !!

 

[varkey]

@steam This definitely looks like packet loss and increased latency due to congestion. They'd need to upgrade capacity to fix this, and it sure wouldn't be a quick fix.

Where are you located? It could be a local area congestion too. I mean, Asianet seems to sub divide into multiple regions based on their website.

 

[steam]

Near Tvm medical college. So a literal hotspot. I'm doomed.

 

[steam]

Asianet is following KeralaVision I guess. I had the post "11am" trauma with KV in March and April. My remote work from home server never used to respond after 11 am till 5pm or so. Disconnected KV and moved to BSNL FTTH , all my issues got sorted. Thanks to BSNL !!

Hello!
Could you please post a ping test to google dns?
I will literally phone up bsnl right now and change connection if it's better lol.

 

[varkey]

BSNL is way better 😉

root@bumblebee:~# ping -c 10 google.com
PING google.com (172.217.163.174): 56 data bytes
64 bytes from 172.217.163.174: seq=0 ttl=56 time=17.759 ms
64 bytes from 172.217.163.174: seq=1 ttl=56 time=17.799 ms
64 bytes from 172.217.163.174: seq=2 ttl=56 time=18.094 ms
64 bytes from 172.217.163.174: seq=3 ttl=56 time=18.069 ms
64 bytes from 172.217.163.174: seq=4 ttl=56 time=17.842 ms
64 bytes from 172.217.163.174: seq=5 ttl=56 time=16.979 ms
64 bytes from 172.217.163.174: seq=6 ttl=56 time=17.436 ms
64 bytes from 172.217.163.174: seq=7 ttl=56 time=17.501 ms
64 bytes from 172.217.163.174: seq=8 ttl=56 time=17.457 ms
64 bytes from 172.217.163.174: seq=9 ttl=56 time=17.989 ms

--- google.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 16.979/17.692/18.094 ms
root@bumblebee:~# ping -c 10 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=14.340 ms
64 bytes from 8.8.8.8: seq=1 ttl=56 time=14.207 ms
64 bytes from 8.8.8.8: seq=2 ttl=56 time=13.943 ms
64 bytes from 8.8.8.8: seq=3 ttl=56 time=13.267 ms
64 bytes from 8.8.8.8: seq=4 ttl=56 time=13.544 ms
64 bytes from 8.8.8.8: seq=5 ttl=56 time=13.532 ms
64 bytes from 8.8.8.8: seq=6 ttl=56 time=13.695 ms
64 bytes from 8.8.8.8: seq=7 ttl=56 time=13.841 ms
64 bytes from 8.8.8.8: seq=8 ttl=56 time=14.247 ms
64 bytes from 8.8.8.8: seq=9 ttl=56 time=13.297 ms

--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 13.267/13.791/14.340 ms
root@bumblebee:~#

 

[Ameen]

It's 15ms for Google.

 

[Ameen]

22 ms for 1.1.1.1

 

[steam]

@varkey Yep. Convinced.

Lesson learned.

Edit: @Ameen Thank you!