New CGN3ACSMR Modem, not compatible with League of Legends?

[Datalink]

Keep in mind that there are at least three issues here:

1.  The latency to and thru the Hitron modems, which requires Hitron to issue a firmware update.  This is an issue known to Hitron.

2.  The issue with the CGN3ACSMR which is stopping LOL from connecting / playing.  This is new, and Hitron probably has no idea of the problem.

3.  Running tracerts down to the LOL server, all of which time out within Riot's network. I don't see how that can be attributed to a modem, but, I'm willing to listen to logic.

[teegeh]

switched to bell, playing without any problems now.

its a shame cuz rogers internet wasnt bad, but issues seem to stay for a long time..

[osuman]

To update my previous post(3 replies back)

I'm getting similar results in other online game called Warframe, which I play very often. So its not just League of Legends.

Here is a tracert to it.

Tracing route to INTEL_CE_LINUX [192.184.12.180]
over a maximum of 30 hops:

1 2 ms 9 ms 9 ms hitronhub.home [192.168.0.1]
2 * * * Request timed out.
3 14 ms 19 ms 39 ms INTEL_CE_LINUX [209.148.243.225]
4 22 ms 29 ms 29 ms INTEL_CE_LINUX [69.63.249.86]
5 22 ms 29 ms 29 ms INTEL_CE_LINUX [69.63.249.77]
6 29 ms 31 ms 39 ms INTEL_CE_LINUX [24.156.144.182]
7 40 ms 39 ms 39 ms ae-32.r05.chcgil09.us.bb.gin.ntt.net [157.238.64.233]
8 58 ms 31 ms 28 ms ae-6.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.26]
9 66 ms 60 ms 58 ms ae-5.r21.dllstx09.us.bb.gin.ntt.net [129.250.4.152]
10 56 ms 59 ms 59 ms ae-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.58]
11 * * * Request timed out.
12 94 ms 99 ms 99 ms ae-1.r04.lsanca03.us.bb.gin.ntt.net [129.250.5.2]

13-30 Request timed out

[RogersGordon]

Gdkitty what results are you getting that are the same on Bell and Rogers?

[Gdkitty]

@RogersGordon


If you look back at post 77, the bottom tracert is MINE from a BELL connection.

[MrPolytime]

I don't know if this warrant a new post, but modem is also creating serious latency issues with Hearthstone on PC. I just moved in to my new place and got the 100mbs package and which came with the CGN3ACSMR modem.

[Datalink]

Have a look at msg #35 on the following page:

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

[jordanmkasla200]

I logged a successful connection to the League of Legends NA server as well as an unsuccessful attempt.  What i found is that all the communications the Game Client makes are over UDP, including establishing the connection to the game server. During the unsuccessful attempts it would appear that the CGN3ACSMR is rejecting an alarming number of UDP packets from the port range used by League of Legends as these packets don't make it past the modem. Because of the nature of UDP any packets lost or rejected while establishing a game connection can have an overwhelming negative impact on the Game Client's ability to establish a game connection and results in the "Firewall Error" as noted by the OP.

[Gdkitty]

---

@MrPolytime wrote:

I don't know if this warrant a new post, but modem is also creating serious latency issues with Hearthstone on PC. I just moved in to my new place and got the 100mbs package and which came with the CGN3ACSMR modem.

---

Your not the first person saying it..

I currently have the regular CGN3, and have no lag issues on the CGN3.

Unless the AC wireless is absolutely necessary.. (which you would get better AC from a 3rd party router anyways).
I really think at this point, people jumping down to the regular CGN3 may be the better option.
(Its identical to the other one, just only N wireless, the modem part is identical.)

[Gdkitty]

OK.. so that makes some sense.

Likely the NAT or FIREWALL is too strong.

You can try droping the firewall strength in the settings, i beleive (if its the same as the regular CGN3)

have you tried PORT FORWARDING then for the port ranges used for LoL?

that SHOULD then allow those to pass through.

May require setting up a STATIC IP for your specific PC your playing on.