- last edited on by
RogersAsif
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
_________________________________________________________________________________________________________________
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.
From what I understand, you need to have the modem running in Gateway mode with the 2.4 Ghz network up and running. Thats the instructions that I received when I requested the update.
This isn't a normal firmware distribution, so, for some reason that has not been specified, the modem need to be in Gateway mode with the 2.4 Ghz network up and running. You're correct, it normally doesn't matter what mode the modem is in, but this time around, its does.
To request the firmware update, follow this link @CommunityHelps to get to the CommunityHelps page when you are signed into the forum. On the right hand side of the page is a link titled "Send this user a private message". Use that link to get to the next message composition page, fill in the title, your modem MAC address and Cable Account Reference Number in the text area and hit send. If the staff are not too busy, you might see the firmware pushed out either late this evening or overnight during the scheduled maintenance periods. If not, it should be pushed out no later than tomorrow night.
I'm assuming then that you have a CGN3ACSMR ?
- last edited on by
RogersAliciaG
Hi, sorry I missed your post earlier,
First thing I wll do is have you read the first post in this thread:
http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/253...
Then, to request the firmware update, follow this link @CommunityHelps to get to the CommunityHelps page when you are signed into the forum. On the right hand side of the page is a link titled "Send this user a private message". Use that link to get to the next message composition page, fill in the title, your modem MAC address and Cable Account Reference Number in the text area and hit send. If the staff are not too busy, you might see the firmware pushed out either late this evening or overnight during the scheduled maintenance periods. If not, it should be pushed out no later than tomorrow night.
The new firmware is now in deployment across the network and is scheduled to be completed by the end of the week.
The @CommunityHelps team will be taking requests until 11:59pm July 8th, 2015. I'd like to see if the speeds that you see on the Android device pick up after the update is loaded.
The 10/100mb/s ethernet port issue was resolved on the CGN3 but I really don't know if it was, or still is a problem for the CGN3ACSMR. That might take a little digging to see if it was reported anywhere on the forum.
-
70117 views
-
27 Likes
-
-
