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

[Datalink]

Update: The new firmware has now been deployed across the network. Customers who received a modem with the old firmware will be updated automatically within 48-72 hours. There is no need to submit your MAC Address & Cable Account Reference number as the update will happen automatically.

This only applies to the CGN3ACSMR.

Announced as of the evening of Thursday 28 May, a firmware update to address the League of Legends issue is close to deployment. Updates are available as indicated in the message below from CommuntyHelps
______________________________________________________________________________________________________________
Hello Community

Good news! We have received a firmware patch from Hitron that resolves the connectivity issue with League of Legends and we’re working on deploying it to all. In the meantime, we can provide the update directly to those who contact @CommunityHelps via private message 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)

Modems will be updated during nightly maintenance windows so you can expect to see the update take effect within 48 hours.

Thank you for your patience.

 Original post:  #176

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

_________________________________________________________________________________________________________________

 Note that this update addresses the League of Legends issue as well as the latency issue observed when pinging the modem. This should also address latency issues through the modem which is good news for anyone who games, not just with LOL, or who runs a time or latency intolerant application. 

The firmware solution that addresses the latency issue will also be applied to the next firmware updates for the CGN3 and CGN3AC, however there is no timeline as of yet for release dates for those modems. 

The Cable account reference number is located within the Internet section of your bill. The account number that you normally see or use is comprised of various home services such as Internet, Home Phone, Home Monitoring, etc, but the requested reference number is located at the top of the Internet section of your monthly account statement.

------

Edited to add the below info:

If you send in your request during the day or early evening, you will probably see the update pushed out either very late in the evening or during the overnight maintenance period.  If not, then it should be pushed out no later than the next night.  The update will install regardless of the operating mode of the modem, Gateway or Bridge mode.

You can tell if you have the latest firmware by logging into the modem to check the firmware version or simply pinging the modem.  The old version is 4.4.8.13.  The new version is 4.5.8.16

If you are connected directly to the modem with the modem in Gateway mode, you can log into and ping 192.168.0.1   If you are connect to a router with the modem in Bridge mode you can log into, and ping 192.168.100.1

Here is an example of what you see with the previous 4.4.8.13 loaded:

ping 192.168.100.1 -n 1000

Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=8ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=12ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=13ms TTL=63
Reply from 192.168.100.1: bytes=32 time=9ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63

Ping statistics for 192.168.100.1:

Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 139ms, Average = 6ms

Note the random ping times and average of 6 ms.

Here is the ping test after 4.5.8.16 is pushed out:

ping 192.168.100.1 -n 1000

Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=25ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63

Ping statistics for 192.168.100.1:

Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 67ms, Average = 1ms

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.

There are two bugs in this updated version:

1.  The wifi is all or nothing.  You either have to have both 2.4 and 5 Ghz networks running, or both disabled.

2.  The firmware doesn't appear to save the enabled / disabled state for the wifi, so, if the power goes out at some point, when the modem fires up, there is a mismatch between what the wifi is actually doing, ie, on or off, and what the user interface indicates.  The way around this is to first save a backup file for the modem.  Navigate to ADMIN.....BACKUP and use the Backup button to create a backup file somewhere on your pc.  Do this when you have the modem settings configured to your preferences.  If the power ever goes out, run a factory reset by pressing the reset button at the back of the modem for 30 seconds and releasing it.  You can also initiate a reset from the ADMIN....DEVICE RESET page.  After the reset and reboot, reload the backup file using the ADMIN....BACKUP page, and then reboot.  Problem solved.

The all or nothing issue has been resolved for the next firmware release.

[Datalink]

@CX2DUBCAKES take a look at the very first post of this thread.  The explanation for the 12 digit cable account reference is in that post.

[CX2DUBCAKES]

Indeed. I'm really sorry I missed that. Been a long day. I found it and sent PM. Thanks again 😉

[Datalink]

No problem.  Please let us know how it works out after the update  🙂

[RyzenFX]

@Vibe I think I found a more efficient way of upgrading the firmware. Try to access the router interface and on the left hand side, one of the options should be 'Firmware' After clicking 'Firmware', there should be a button where you can check for the latest firmware. If there is a firmware update availiable, I think it will automatically download. After that, it should give you instructions.

[Vibe]

I have updated the firmware Manually due to it never coming up when I clicked update firmware kept saying i had the latest hopefully all is well now thank you eddie if anymore suggestions I'll try and If anyone wants to see any tests done with the new cgn3acsmr firmware to see if it's worth the update post and let me know... thanks for the help

[Datalink]

Can you go to this page:

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

have a look at post 209, which is my request for a couple of ping tests.  If you have the time, can you have a try at this and post the results?  I'm assuming that you're running a wired pc or laptop for gaming....

[Vibe]

Ok I am on my pc and yes I am wired everything here you go

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 11ms, Average = 1ms

[Vibe]

Hey datalink check your PMs if anything else let me know 

[Akimova]

---

The firmware solution that addresses the latency issue will also be applied to the next firmware updates for the CGN3 and CGN3AC, however there is no timeline as of yet for release dates for those modems. 

---

I knew it. CSMR existed for a reason, which is most likely a hardware difference. I also had this feeling that they will update it first, royally the rest of the "tester" base. Yes, I've been waiting for two months now (first waiting 3 weeks to get the AC version of the modem) and now I'm forced to go and chase the CSMR. Thank you Rogers.

---

[CX2DUBCAKES]

I woke up this morning after last night's post and to my surprise, I have received the new firmware update. Will be testing today and will post my results. Thanks again to everyone here that helped address this issue. It's a big thumbs up to you all. And especially the support team for their haste on resolving this issue.

[RyzenFX]

@CX2DUBCAKES Is the interface any faster than the CGN3?

[RyzenFX]

@Datalink I can confirm that the interface loading time is faster on the CGN3ACSMR w/o the new firmware update. However, I do notice that it is lacking some features such as the ability to change timezones. Does anybody know if the new firmware adds that?

[CX2DUBCAKES]

Didn't really notice an interface time loading difference. But I still can go into the administration panel and change time settings / time zone.

AND MOST IMPORTANTLY. .. THE FIREWALL ERRORS ARE GONE PLAYING LoL... Connects everytime 😉

[CX2DUBCAKES]

And I just noticed I can't answer that question anyways cause I have the AC version. And I think you want the CGN3 version. I am running 4.5.8.16 firmware on the ACSR model and it's flawless. So happy with the community fellas 😉

[jackthecompguy]

Just got the CGN3ACSMR tonight, its great so far. Testing out the 5G portion... Sent a PM to CommunityHelps just now with the required info and looking forward to being on the latest firmware.

Cheers everybody 🙂

[jackthecompguy]

Well... Firmware just got pushed to me. Looks like I found a bug: With this firmware version (4.5.8.16) I cannot run 5Ghz Wi-Fi only. The 2.4 needs to be enabled for the 5 to work. On the firmware it shipped with 5G only wasn't an issue. I'm happy to live with it while it is investigated but I expect it to be fixed. (I am under the impression that this firmware that is being pushed out on request only is still in beta hence it not being released en masse)

[Datalink]

I think I noticed the same issue, turn off the 2.4 Ghz wifi and the 5 Ghz LED goes out.  Now, the only way to confirm this is to monitor the 5 Ghz network with inSSIDer.  This might just be an LED control issue, not necessarily one where the 5 Ghz network stops working.  I didn't test for that and probably won't as I run my modem in Bridge mode.  Not sure when I can run another test to check it out.  Here's the link for the last freebie version of inSSIDer.  It doesn't do 802.11ac, but the new pay version does, and is worth the $20 U.S. if you use 802.11ac networks.  You don't need an 802.11ac capable laptop as the program reads the transmit headers and displays the a/n/ac networks in the 5 Ghz band.

http://www.techspot.com/downloads/5936-inssider.html

[jackthecompguy]

Nope I tested and confirmed, with 2.4Ghz off and 5Ghz on, neither the 2.4 or 5 Ghz networks show up to either my laptop or phone, and the paid version of Inssider does not see them. (Thanks for the recommendation - had paid the $20 for it a while back based on its frequent mention here - I have had 802.11ac routers for the past 2yrs and set it up at clients places alot, and have an 802.11ac capable laptop and desktop. So a worthwile investment)

So its not just the LEDs going out, the actual wi-fi networks go down.

The other thing is, (minor issue) when going to the login screen it says "Undefined" instead of "Username" - just a minor OCD thing.

[Datalink]

Thanks very much.  I'll make sure that the Modem Products Manager sees this in the morning.  I'll also ask the mods to approve the screen shots in the morning as well. 

[Datalink]

This issue is fixed in the next release. 🙂

[CX2DUBCAKES]

I hope it's just a fluke. But I just got the dreaded "firewall error" on LOL on game I jus played. I'm queuing up another game to confirm. I hope it's not gonna rear it's ugly head again. Will post results :;