*** CGN3ACSMR - League of Legends – latency: firmware release pending

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Retired Moderator RogersAliciaG
Retired Moderator
Posts: 235

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

Hi @bngan2

 

First I would like to say Welcome to the community! Smiley Happy

 

Thank you for reaching out to us, the firmware/software update should be updated automatically within 48 hours from the time the modem came online. 

 

If you still do not have the update after 72 hours you can PM @CommunityHelps and provide the following information:


-Cable account reference number(12 digits beginning with “2”)


-MAC address of modem (12 digits found on the back of your Hitron modem)


Thank you for your patience.

 

RogersAliciaG

I Plan to Stick Around
Posts: 10

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

"Note that the average ping time to the modem drops from an average of 5 to 6 ms down to 1 ms.  Its not perfect as there are still random high ping times in the double digits, but its still a very good improvement."

Just curious, does rogers plan on fixing this issue fully? This SHOULD be perfect and is a pretty big issue. I would like to atleast know there are still plans to fix this further.

I've Been Here Awhile
Posts: 4

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

Could you please help me diagnose my problem. I recently went from teksavvy to rogers. Before at teksavvy I barely had lag and when i did it was mostly from league of legends server side.

 

I usually game with a dual band gaming router which I have connected to the modem/router from rogers. I get unbearable lag around afternoon and 8-12 ish pm.

 

This is unusual because this has never happened before. My firmware for my router is up to date and im connected to the least populated channel.

 

I have tried turning on QOS services on my asus router and forwarded all ports of league of legends to no success. Is it possible that my bandwith is being throttled?

 

Please if you could help me diagnose that would be great help. I will also submit a support ticket to rito.

Resident Expert
Resident Expert
Posts: 6,144

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

Can you check the product sticker at the back of the modem and let us know which modem it is.  If its one of the new Hitron modems it will be a CGN3, CGN3AC, or CGN3ACSMR.  If its a CNG3ACSMR, can you log into the modem and on the Status page which is the first page that comes up, check the software version.  The previous version is 4.4.8.14.  The update version in 4.5.8.16.  It takes 48 to 72 hours to update to that firmware version.  4.5.8.16 resolves connect / disconnect issues with League of Legends and other online games, issues with VOIP devices and VPNs and just about any other latency intolerant application.  The jury is still out for PS3s and PS4s.  If you look at the very first post in the following thread, you can see the difference in the latency for ping tests to the modem, before and after version 4.5.8.16 loads.

 

http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/thread-id/2532...

 

Just to check, are you running the modem in Bridge mode, with the Asus router running in full router mode?  You most likely do not need or can't use QOS.  For speeds above 100 Mb/s, with a recent Asus router, you should ensure that the Hardware Acceleration is enabled.  This is actually Broadcom's Cut Through Forwarding (CTF) which is incompatible with various functions such as QOS, traffic monitoring and any other function that requires the router processor to process the data for any purpose.  CTF basically forwards the data at the chip level, WAN port to local LAN port.  When it is disabled you lose the fast path through the router and take a second hit on throughput due to the processing of the data.  Assuming that your router has a Hardware Acceleration function which can be enabled, (LAN.... SWITCH CONTROL..... Hardware Acceleration) ensure that this is on. 

 

The  other possibility to look at is the cable signal levels.  Can you log into the modem, navigate to the STATUS.... DOCSIS WAN page, copy the Downstream and Upstream tables and paste them into the thread.  That will allow us to ensure that the signal levels are within their normal operating range.  Even so, if you happen to be on a busy node, there is a good change that the node is not able to service the number of customers that are using it with higher data rates.  That usually requires further investigation to come to that conclusion.

 



I've Been Here Awhile
Posts: 4

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

Thanks for the reply. This is the CNG3ACSMR modem and the products firmware version is 4.5.8.16. 

 

I am not sure if I'm running the modem in bridge mode or not but through the gateway I have disabled the wireless option. Nvm I just checked and it was not in bridge mode. Can this be causing lag? 

 

DOCSIS WAN

This menu displays both upstream and downstream signal parameters

 
Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1645000000256QAM2.600938.605
2591000000256QAM4.100140.946
3597000000256QAM3.600240.366
4603000000256QAM3.700340.366
5609000000256QAM3.700440.366
6615000000256QAM3.700540.366
7621000000256QAM3.600638.605
8633000000256QAM3.300740.946
9639000000256QAM3.100838.983
10651000000256QAM2.0001038.605
11657000000256QAM2.0001138.983
12663000000256QAM1.5001238.983
13669000000256QAM2.00010938.983
14675000000256QAM2.00011038.605
15681000000256QAM2.20011138.983
16687000000256QAM2.10011238.983
17693000000256QAM2.10011338.605
18699000000256QAM2.00011438.983
19705000000256QAM1.90011538.983
20711000000256QAM2.10011638.983

 

Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandWidth
130596000ATDMA - 64QAM38.00026400000
223700000ATDMA - 64QAM38.00036400000
338596000ATDMA - 64QAM38.00013200000
Resident Expert
Resident Expert
Posts: 6,144

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

It could be partially responsible.  Log into the modem, navigate to BASIC..... GATEWAY FUNCTION, and disable the Residential Gateway Function.  Save the setting and the modem will reboot into Bridge mode.  Usually anyone running in Bridge mode will then run everything through their own router, so, if there is anything else connected to the modem, it or they should be connected to the router instead.  Reboot the router as well so that it picks up the 192.168.01 address from the modem.

 

To log back into the modem when its in brige mode, use 192.168.100.1.   You can do this through the router, so you don't have to connect a pc or laptop to the modem to get back into it to swtch back to Gateway mode or to check the signal levels.

 

With the modem in Gateway mode you would be running a double NAT situation, which is not good in terms of any port forwarding.

 

Your signal levels look ok.  You should not have any problems with those.



I've Been Here Awhile
Posts: 4

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

My post  got deleted. Idk how. But i did a test and within the first minute of gameplay there was a noticeable spike. Also when I ping riot's servers my ping spikes upto 1000ms at times. And when I ping my router it can go upto 67ms. I need help with this. Is this coming from the ISP or is this cause by my wireless environment?

I've Been Here Awhile
Posts: 4

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

No still a problem. In the first minute of gameplay it spiked upto 100ish from 40ish. Could it be a problem with my router?

This is what i get when i ping riot's servers.

Reply from 104.160.131.1: bytes=32 time=36ms TTL=59
Reply from 104.160.131.1: bytes=32 time=31ms TTL=59
Reply from 104.160.131.1: bytes=32 time=38ms TTL=59
Reply from 104.160.131.1: bytes=32 time=180ms TTL=5
Reply from 104.160.131.1: bytes=32 time=64ms TTL=59
Reply from 104.160.131.1: bytes=32 time=34ms TTL=59
Reply from 104.160.131.1: bytes=32 time=90ms TTL=59
Reply from 104.160.131.1: bytes=32 time=33ms TTL=59
Reply from 104.160.131.1: bytes=32 time=47ms TTL=59
Reply from 104.160.131.1: bytes=32 time=312ms TTL=5
Reply from 104.160.131.1: bytes=32 time=34ms TTL=59
Reply from 104.160.131.1: bytes=32 time=33ms TTL=59
Reply from 104.160.131.1: bytes=32 time=35ms TTL=59
Reply from 104.160.131.1: bytes=32 time=34ms TTL=59
Reply from 104.160.131.1: bytes=32 time=230ms TTL=5
Reply from 104.160.131.1: bytes=32 time=31ms TTL=59
Reply from 104.160.131.1: bytes=32 time=43ms TTL=59
Reply from 104.160.131.1: bytes=32 time=52ms TTL=59
Reply from 104.160.131.1: bytes=32 time=324ms TTL=5
Reply from 104.160.131.1: bytes=32 time=177ms TTL=5
Reply from 104.160.131.1: bytes=32 time=65ms TTL=59
Reply from 104.160.131.1: bytes=32 time=30ms TTL=59
Reply from 104.160.131.1: bytes=32 time=39ms TTL=59
Reply from 104.160.131.1: bytes=32 time=35ms TTL=59
Reply from 104.160.131.1: bytes=32 time=240ms TTL=5
Reply from 104.160.131.1: bytes=32 time=38ms TTL=59
Reply from 104.160.131.1: bytes=32 time=31ms TTL=59
Reply from 104.160.131.1: bytes=32 time=33ms TTL=59
Reply from 104.160.131.1: bytes=32 time=37ms TTL=59
Reply from 104.160.131.1: bytes=32 time=31ms TTL=59
Reply from 104.160.131.1: bytes=32 time=1136ms TTL=
Reply from 104.160.131.1: bytes=32 time=1117ms TTL=
Reply from 104.160.131.1: bytes=32 time=1217ms TTL=
Reply from 104.160.131.1: bytes=32 time=1069ms TTL=
Reply from 104.160.131.1: bytes=32 time=374ms TTL=5
Reply from 104.160.131.1: bytes=32 time=32ms TTL=59
Reply from 104.160.131.1: bytes=32 time=39ms TTL=59
Reply from 104.160.131.1: bytes=32 time=38ms TTL=59
Reply from 104.160.131.1: bytes=32 time=366ms TTL=5
Reply from 104.160.131.1: bytes=32 time=49ms TTL=59
Reply from 104.160.131.1: bytes=32 time=34ms TTL=59
Reply from 104.160.131.1: bytes=32 time=35ms TTL=59
Reply from 104.160.131.1: bytes=32 time=36ms TTL=59
Reply from 104.160.131.1: bytes=32 time=221ms TTL=5
Reply from 104.160.131.1: bytes=32 time=77ms TTL=59
Reply from 104.160.131.1: bytes=32 time=55ms TTL=59
Reply from 104.160.131.1: bytes=32 time=37ms TTL=59
Reply from 104.160.131.1: bytes=32 time=106ms TTL=5
Reply from 104.160.131.1: bytes=32 time=40ms TTL=59
Reply from 104.160.131.1: bytes=32 time=34ms TTL=59
Reply from 104.160.131.1: bytes=32 time=32ms TTL=59
Reply from 104.160.131.1: bytes=32 time=32ms TTL=59
Reply from 104.160.131.1: bytes=32 time=38ms TTL=59
Reply from 104.160.131.1: bytes=32 time=327ms TTL=5
Reply from 104.160.131.1: bytes=32 time=38ms TTL=59
Reply from 104.160.131.1: bytes=32 time=30ms TTL=59
Reply from 104.160.131.1: bytes=32 time=31ms TTL=59
Reply from 104.160.131.1: bytes=32 time=35ms TTL=59
Reply from 104.160.131.1: bytes=32 time=36ms TTL=59
Reply from 104.160.131.1: bytes=32 time=35ms TTL=59
Reply from 104.160.131.1: bytes=32 time=31ms TTL=59
Reply from 104.160.131.1: bytes=32 time=232ms TTL=5
Reply from 104.160.131.1: bytes=32 time=38ms TTL=59
Reply from 104.160.131.1: bytes=32 time=32ms TTL=59
Reply from 104.160.131.1: bytes=32 time=32ms TTL=59
Reply from 104.160.131.1: bytes=32 time=32ms TTL=59
Reply from 104.160.131.1: bytes=32 time=207ms TTL=5
Reply from 104.160.131.1: bytes=32 time=32ms TTL=59
Reply from 104.160.131.1: bytes=32 time=37ms TTL=59
Reply from 104.160.131.1: bytes=32 time=32ms TTL=59
Reply from 104.160.131.1: bytes=32 time=58ms TTL=59
Reply from 104.160.131.1: bytes=32 time=30ms TTL=59
Reply from 104.160.131.1: bytes=32 time=34ms TTL=59
Reply from 104.160.131.1: bytes=32 time=49ms TTL=59
Reply from 104.160.131.1: bytes=32 time=321ms TTL=5
Reply from 104.160.131.1: bytes=32 time=32ms TTL=59
Reply from 104.160.131.1: bytes=32 time=31ms TTL=59
Reply from 104.160.131.1: bytes=32 time=146ms TTL=5
Reply from 104.160.131.1: bytes=32 time=34ms TTL=59
Reply from 104.160.131.1: bytes=32 time=41ms TTL=59
Reply from 104.160.131.1: bytes=32 time=33ms TTL=59

 

And this when I ping my router.

 

Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=18ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=12ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=15ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=67ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64

 

Maybe a problem with my router or my wireless card?

 

Resident Expert
Resident Expert
Posts: 6,144

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

Did you kick the modem into Bridge mode?  And if so, did  you reboot the router so that it picks up the 192.168.0.1 IP address.  In order to look at the ping situation you should run your test via wired connection first in order to rule out any Wifi issues.   Are you connected via 2.4 or 5 Ghz network?



I Plan to Stick Around
Posts: 10

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

League of legends has issues with wireless networks. Even in a perfect enviroment (no other wireless networks, good router, good singal) league still has latency problems, Try testing with no wireless involved if possible to elimiate that as a cause then go from there.