New CGN3ACSMR Modem, not compatible with League of Legends?

[haguuhar]

I just changed from a hybrid fibre 30 (with CGN2 modem) to the Rogers Ignite 60 (with the CGN3ACSMR modem). I'm not sure why, but I now get firewall errors when I try to load up the game. The internet works fine, other than the specific case in the game. Does anyone know what is happening, or how to fix it? I have tried port forwarding, turning the modem into bridge mode, even disabling the router's firewall. None of these options have fixed the problem.

*Edited Labels***

[RogersMoin]

Hello, @robinrobin

Thank you for your post and welcome to the Rogers Community Forums!

CGN3ACR should be running firmware version 4.2.8.12, which is the updated version for this model. If your modem has a different version, please let us know.

You have the option of swapping your modem to CGN3ACSMR model and see if that improves your online gaming experience. For a lot of our Community members, the gaming latency issue was resolved with the firmware version 4.5.8.16 on CGN3ACSMR modem.

Hope this helps!

RogersMoin

[Datalink]

All Hitron CGN3 series modems have or had issues with latency.  The CGN3ACSMR, until the latest firmware release also had connect / disconnect problems with online games, VOIP devices and VPNs.  Those two problems have been solved for the CGN3ACSMR in the firmware release and it is very stable.  There are still some people who run into issues with it and replacing it with the CGN3 solves those issues, albeit with added latency.  It takes 48 hours to update the CGN3ACSMR after it goes active on the network, so for those first 48 hours, don't consider doing anything that is latency intolerant or cannot tolerate connect / disconnect occurrences.  After the firmware upgrade you will probably be satisfied with its performance. 

The firmware changes that were made to the CGN3ACSMR to solve the latency issue will also be made to the CGN3 and CGN3ACR, but I have not heard of the timeline for those updates.  The best solution for now is to swap the modem for the CGN3ACSMR and tolerate the 48 hours that it takes to update the firmware. 

[robinrobin]

Thanks @Datalink for your suggestion!

[robinrobin]

Hi @RogersMoin,

Yes, my modem's firmware is 4.2.8.12. I'll think about swapping to CGN3ACSMR model.

[RogersMoin]

Hello, @robinrobin

Great! I too believe swapping to the CGN3ACSMR model should help. Thank you for your contributions and for your help in keeping the community a pleasant place to be.

Cheers,

RogersMoin

[robinrobin]

Got CGN3ACSMR model this afternoon. The firmware version is 4.4.8.14.

Hope it can be auto-updated within 48 hours.

[Datalink]

If it doesn't, follow this link @CommunityHelps to navigate to the CommunityHelps public 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 navigate to the next message composition page, fill in an appropriate title, your modem MAC address and Cable Account Reference Number and a brief explanation indicating that the modem has not updated as of yet, and send the pm.

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.

The modem MAC address can be found on the sticker at the back of the modem, or in the HFC MACC Address located in the Status page of the modem.

[Akimova]

Any differences between the beta firmware for SMR vs the final, which has been pushed to everyone?

[jayte]

Hi, I got my CGN3ACSMR router 2 days ago and I just checked the software version and it is 4.5.8.16, however, it still doesn't allow me to connect to the game.  I have forwarded the ports, but it hasn't helped.  I read that the new software should help with the game, but it doesn't seem to have any effect on my connection.  

[RogersArthur]

Hi @jayte,

Thank you for your post and Welcome to the forums!

We really appreciate your patience, I'm surprised the update hasn't help with getting you connected to the game. We have confirmed the firmware has helped many other users resolve any firewall connectivity issues. What type of error message are you receiving? What have you tried so far? Have you tried removing and reinstalling the application?

 
Regards,
RogersArthur

[robinrobin]

The modem firmware got updated yesterday. The average of ping response time seems good now, but it still has some packages lost and long response time occationally.

I use my gaming laptop with AC wifi connection. Speedtest is great which is 320/21.

Please see the following record:

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=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=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=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=680ms TTL=64
Request timed out.
Request timed out.
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=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=39ms 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=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

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

**************************************************************

Downstream Overview
Port ID     Frequency (MHz)     Modulation     Signal strength (dBmV)     Channel ID     Signal noise ratio (dB)
1    603000000     256QAM     3.800    3    38.983
2    591000000     256QAM     3.600    1    38.983
3    597000000     256QAM     3.700    2    38.983
4    609000000     256QAM     3.900    4    38.605
5    615000000     256QAM     3.600    5    38.983
6    621000000     256QAM     3.500    6    38.983
7    633000000     256QAM     3.100    7    38.605
8    639000000     256QAM     3.300    8    38.605
9    645000000     256QAM     3.700    9    38.605
10    651000000     256QAM     3.700    10    38.983
11    657000000     256QAM     4.200    11    38.983
12    663000000     256QAM     4.000    12    38.605
13    669000000     256QAM     4.000    13    38.605
14    675000000     256QAM     3.300    14    38.983
15    681000000     256QAM     3.000    15    38.605
16    687000000     256QAM     2.900    16    38.983
17    693000000     256QAM     3.500    17    38.605
18    699000000     256QAM     3.500    18    38.983
19    705000000     256QAM     3.900    19    38.983
20    711000000     256QAM     3.800    20    38.605
Upstream Overview
Port ID     Frequency (MHz)     Modulation     Signal strength (dBmV)     Channel ID     BandWidth
1    30596000    ATDMA - 64QAM    43.500     2     6400000
2    23700000    ATDMA - 64QAM    43.500     3     6400000
3    38596000    ATDMA - 64QAM    43.500     1     3200000

Any comments?

Thanks!

[JesseF]

As stated above, I'm on update 4.5.8.16 and using the AC connection (Although even if I'm not on the ac connection, or on 5g or 2.4g) the issue is the same.

My speedtest shows 200+ down and 20ish Up however whenever I get into any game I start to drop packets like crazy... it's really annoying as I can't enjoy the game at all.

It also only seems to be this computer as well, my other computers don't seem to have the issue while in game.

[Datalink]

What game are you playing and does it require any ports to be forwarded so that it runs correctly?  If so, are those ports set for forwarding or are you using UPNP enabled in the modem?  The extremely high ping times are very odd for this firmware version.

[JesseF]

League of Legends, No it does not require ports to be forwarded however if required you can (I did just to make sure I wasn't getting any issues on that end)

I believe UPNP is on currently on the router. It isn't high ping, my ping actually stays pretty constant at around 70-80. What happens is everything on the game will move around and you can move but don't see any damage or abilities being casted for a period of time and then when everything comes back it's all at once in a big mess of things.

[Datalink]

@robinrobin your ping times for the most part are good.  Its unusual to see such a high ping time and time outs.  I have to assume that when the ping test was running that something else started that caused those two items.  Normally the ping times are down in the 1ms timeframe with an occasional double digit ping.  The signal levels and signal to noise ratios are good as well.  Everything running as expected?

[Datalink]

@JesseF League of Legends issues led to the release of 4.5.8.16 so its unusual to see issues still going on, unless they are caused by a cable issue or wifi issues.   Can you log into the modem, navigate to the STATUS.... DOCSIS WAN page, copy the downstream and upstream tables and paste them into this thread, as is shown above so I can have a look at them.  Those are the cable signal levels and signal to noise ratios which might be of interest at this point. 

[JesseF]

Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 639000000 256QAM 0.000 8 36.387
2 591000000 256QAM -0.500 1 36.387
3 597000000 256QAM -2.200 2 35.595
4 603000000 256QAM -2.900 3 35.595
5 609000000 256QAM -2.500 4 35.595
6 615000000 256QAM -1.600 5 36.387
7 621000000 256QAM -1.000 6 36.387
8 633000000 256QAM -0.100 7 36.387
9 645000000 256QAM -0.200 9 36.610
10 651000000 256QAM -0.200 10 35.780
11 657000000 256QAM -0.100 11 36.387
12 663000000 256QAM 0.200 12 36.387
13 669000000 256QAM -0.400 13 35.780
14 675000000 256QAM 0.100 14 36.387
15 681000000 256QAM -0.600 15 35.595
16 687000000 256QAM -1.100 16 35.595
17 693000000 256QAM -1.800 17 35.595
18 699000000 256QAM -2.500 18 35.084
19 705000000 256QAM -2.200 19 34.926
20 711000000 256QAM -2.100 20 34.926
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID BandWidth
1 38596000 ATDMA - 64QAM 46.750 1 3200000
2 23700000 ATDMA - 64QAM 46.750 3 6400000
3 30596000 ATDMA - 64QAM 45.250 2 6400000

[Datalink]

You're downstream power levels are fine, the signal to noise ratios are at the low end of the range which is normally 36 to 40 dB.  The  upstream signal levels are elevated, almost to the point of calling tech support, but not just yet.  You indicated that the problem is only on the one pc, which makes me wonder if there if something firing up on that pc on a periodic basis and calling out to a server some reason.  Do you use any cloud services on that pc of any type, or backup service that would chew thru cpu cycles and transmit / receive time on the ethernet port? 

Do you run LOL on any other pc or laptop?  The best way to run port forwarding is to create a DHCP reservation for the pc/laptop/console in question, and then set up the port forwarding for that reserved IP address.  If you have set up port forwarding, you shouldn't need UPNP.  It should be one or the other.  The problem with UPNP, from what I can see from comments made here online is that it doesn't clean up after itself, and the modem has a limit on the number of rules that it can have set.  So, if you were switching pc's or laptops and running LOL on various platforms, I can see that causing problems within the modem.  Just as an experiment you could set up a DHCP reservation for the pc, clean out any other existing port forwarding rules while you are in there and then set up new rules for that reserved IP address.

[JesseF]

I've already done this, the issue persists.

It seems the issue only happens (From my tests of 1 game since I haven't had much time today) if I am in a skype call as well as playing the game. I'm thinking port congestion but I've disabled the use port 80 feature on skype... so I'm not sure why that would cause an issue. I'm not sure if it's all VoIP programs or just skype either as I've only ever tested with skype at the moment.

That's probably why it looks like only the one computer is having issues because it's the only one that runs skype while in a game. I have another computer running beside me most of the time with league running as well as I play with a friend but he doesn't go on skype as there would be no point for 2 of us in the same room to be on talking to friends.

If I'm not on skype, I seem to be ok. If I get on a skype call I start to loose packets like nuts.

[Datalink]

With more than one pc running LOL, UPNP would be the best way to go.  With UPNP enabled, I'd clean out any hard set port forwarding rules and reboot the modem.  Skype, yep, I can see that possibly conflicting with a game that happens to be running at the same time, at least in terms of the resources required by both applications.  I don't know if there is any solution for that other than have a third pc or laptop running just for that purpose when you happen to be gaming. Maybe it just depends on the speed of that pc.  |Hopefully anyone else who runs a similar setup can comment on their experience with it.  Just for the heck of it, have a look at the ports required for both LOL and Skype and see if there are any common ports.  That could definitely be a problem if the same port is required for both applications.

[JesseF]

The only common ports seem to be the 80 and 443 I think, which I unchecked on skype.

My pc is a custom build, I7 24gb ram, gtx 970 so on so forth so it's not the pc resources reaching it's max or anything and I've never had this issue before switching to rogers so it's something within the rogers framework either the router or the service it's self.