cancel
Showing results for 
Search instead for 
Did you mean: 

New CGN3ACSMR Modem, not compatible with League of Legends?

haguuhar
I Plan to Stick Around

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***

768 REPLIES 768

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

haguuhar
I Plan to Stick Around

Yes, I am using a wired connection. I have also tried wireless on my laptop to no success.

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

haguuhar
I Plan to Stick Around

Heres a tracert I ran to the league servers...

 

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

1 2 ms 9 ms 9 ms hitronhub.home [192.168.0.1]
2 16 ms 19 ms 19 ms INTEL_CE_LINUX [7.11.163.181]
3 16 ms 19 ms 29 ms INTEL_CE_LINUX [67.231.221.25]
4 38 ms 29 ms 29 ms INTEL_CE_LINUX [24.156.146.73]
5 * 22 ms 29 ms INTEL_CE_LINUX [209.148.224.242]
6 28 ms 29 ms 29 ms ae53.edge1.Toronto2.Level3.net [4.31.208.129]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

mfriers
I Plan to Stick Around

Now the windows 7 computer is getting the same error, i guess it was a fluke the game started in the first place.....i dont get it

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

Remotecube
I've Been Around

Having the same problem with this router on just about every game I want to play. Turning the router's firewall off ENTIRELY seemed to help somewhat, but the problem still persists. I'm still stuck on the .13 firmware though, so I'm hoping the .14 update will help. If not, I'm just returning this piece of crap. I've never had such a hard time establishing basic functionality before.

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

haguuhar
I Plan to Stick Around

I tried switching my modem. Turns out the two Rogers where I live are out...I don't understand how this kind of problem made it through the testing phase.

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

gisuck
I'm a Reliable Contributor

The IP address you provided in that trace route is located in Europe. Are you purposefully playing on EU instead of NA? You may want to change your LoL preferences.

 

Also, the first route in your trace route shows that your are still NATting somewhere. To rule out hardware causing the issue, I would put the Rogers modem into bridge mode, and connect a computer directly to the Rogers modem (without your personal router) to test the setup. This way you are ruling out any strange configuration on your LAN causing the issue. It would be down to software at that point.

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

Gdkitty
Resident Expert
Resident Expert

All the users with this, are using the CGN3AC modem, correct?

Since this seems to be an issue.. and even sometimes is persisting through bridge mode, from some user accounts...

Personally... unless you are 100% tied to needing the built in AC...

I would try steping down to the regular CNG3.
Its fully compatable with all the new plans.

 

MANY users on here have it bridged, seemingly without issues.



Re: New CGN3ACSMR Modem, not compatible with League of Legends?

netwrks
I Plan to Stick Around

I tried a tracert from outside of Toronto, with the same results. What this tells me, either the Level3 routers is dropping the tracert, (which I doubt). Looks like a Level3 routing issue.. This has nothing to do with what modem you are using, as you are already into the network.. BTW, I'm using a CGN3.. Can probably have Rogers take it up with Level3.

 

6 28 ms 29 ms 29 ms ae53.edge1.Toronto2.Level3.net [4.31.208.129]

7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out...........

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

I did think about that as well Netwrks..

Sometimes, its common to have SOME come up that way.

I know when you do a tracert to BLIZZARD servers, like wow, SC, etc... the last 4 or so come up that way, as they are within blizzards firewall, and non routable.

But for the amount.. right after the first or second level3 connection.. unless the server is directly off the level3 network there...



Re: New CGN3ACSMR Modem, not compatible with League of Legends?

netwrks
I Plan to Stick Around

IP Address 95.172.65.xx is in the UK. It wouldn't be directly connected to this particualr Level3 router. The Level3 router is a short hop from the Rogers routers. Still looks like a Level3 routing issue.

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

gisuck
I'm a Reliable Contributor

Before we start finger pointing the trace route issues, and where the fault lies, I think we should quickly address if this IP address we trace routing to is even part of RIOT Games. I don't think this is. I think this is based off of legacy information and is no longer current. Here is the troubleshooting tips RIOT Games offers for trace routes, and that IP address is not offered in it's list. (Edit: Sorry, just looked at the IP address a noticed that the IP address range are similar. So I take back my comment this IP address doesn't belong to RIOT Games. But still, the IP address is EU when the preference should be NA for Rogers. Otherwise the game play would be laggy at best since the internet traffic needs to go through half of the world. You can't beat physics. You can't beat the speed of light.)

  

https://support.riotgames.com/hc/en-us/articles/201752674-Network-System-and-League-of-Legends-Logs#...

 

If there was a routing issue, then RIOT Games support would be the people to take it up with since it's their services that are being affected. This is why they are asking for the trace route output being placed in a txt file and sent to support to examine.

 

If we really want to troubleshoot if this is a CGN3ACSMR modem issue, we must rule out all LAN equipment except for the CGN3ACSMR modem and a computer. This is why I brought the discussion back to saying I see a NAT in the trace route and we should take that out.

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

fantasc
I've Been Around

Since UPGRADING to the CGN3ACSMR modem/router I have also been unable to play League of Legends, due to the Firewall May Be Blocking The Connection error message.

 

I have disabled firewalls, used my old router and turned the modem into a bridge, opened ports, put in the DMZ, disabled the IPv6, used a VPN, and then since nothing worked. I removed my old router, reset the modem to be the active router, then did every step again for the CGN3A, and had the same result.  I brought the modem back to the store and got a new one thinking it was faulty, and the same problem continues after doing the entire process again for the new modem.

 

I called the Rogers Techspert division and they told me to do everything I had already done.  The technician on the phone was using the same youtube videos and forums that I was using and he is supposed to be the expert.  

 

I believe this is a problem with Hitron Technologies, the manufacturer of the product itself.  What I really want to do is use the modem as a projectile towards a Rogers office but that will make me unable to flame on forums and try to find an actual solution to this problem.  LOL

 

The most frustrating part of this whole thing is that about 5% of the time, the game connects perfectly and I can play! How can it WORK SOMETIMES!? It makes no sense.  I have the same problem on laptop vs desktop and wireless vs wired.  

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

Hi Guys

 

Im jumping in a little late but i wanted to add my information.

 

I just started playing the game about two days ago. I have the 100u Ignite Package, with the CGN3ACR. Hardware version 1A and im on Software 4.2.8.12

 

The CGN3ACR and CGNACRSMR are essentially identical to my understanding.

 

So far ive played 2 matches on my macbook pro(non-ac) and 2 matches on my windows PC. I am not sure if the match type matters but i played 3 (5 players vs 5 Bots) and 1 (5 players on 5 players).

 

I haven't done any port forwarding yet or any ping tests etc.

 

So far i haven't had any disconnects or degraded performance and didn't get any firewall errors. How often is the issue happening for you guys?

 

I'll be playing more and will see if i can get the SMR model and have lastest firmware pushed to see if it makes any difference in gameplay/connectvity and will report back.

 

The online gaming infastructure is quite complex so there could be various factors to the issue. It would all come down to factoring things out one by one.

 

Your home network needs to be at optimal performance, as with the performance from the ISP. The game servers which we don't hear much about is another factor too.

 

I mostly play PS4 games online and find it varies with different games/different setups etc. I had another case with a PS4 online game where the game support team said it was most likely my NAT and ISP which actually wasn't the case.

 

Being a gamer myself i understand the frustration. I hope everyone gets their problem solvedSmiley Sad

 

RogersAsif

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

gisuck
I'm a Reliable Contributor

Hi Asif,

 

Thank you for your comments here. As a test, can you do this?

 

1) Launch the LoL launcher

2) Before pressing the Launch button in the top center of the screen, go to the top right side of the screen and drop the server to EUW or EUNE.

3) Try to play a few rounds with bots.

 

The reason I ask is that some of the trace route testings I've done is highly suspect that there is an issue with Rogers Upstream provider (Level 3) going to final destinations to Riots LoL servers. This may be the cause of much complains with Rogers and playing LoL which is eroniously being blamed as a modem defect.

 

I don't play LoL myself so I haven't been able to test.

 

If there's failure with the game play, then I suspect what I have stated is what is to be true. Unfortunately resolution to this problem going to be very long and difficult unless we can get someone at the Rogers NOC to investigate. It'll likely mean that Rogers NOC will need to file a support ticket with Level 3 to get the issue resolved. There is no way this is going to happen through normal support channels using Rogers support. The last resort is crossing fingers that Riot can file a ticket with Level3 on Rogers behalf.

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

RogersAsif
Retired Moderator
Retired Moderator

Hi @gisuckSmiley Happy

 

Yes, hence why i started with testing the router. I plan to see if i can test on the "SMR" model with latest firmware so we can possibly rule that out.

 

I haven't even got a chance to start looking at the route traces but as you mentioned  routing issues are something that can't be quickly fixed . Rogers Support wouldn't be able to look into the issue further as it's outside their scope of support, but we intend to see if the issue can be further investigated.

 

RogersAsif

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

gisuck
I'm a Reliable Contributor

I just have the CGN 3 (Wireless N) modem still, and I can see the suspect trace routes when I'm doing traces according to the support documentation suggested by Riot.

 

Specifically this one in EUW:

 

Tracing route to 162.249.72.1 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms ion [192.168.130.1]
2 * * * Request timed out.
3 16 ms 17 ms 22 ms gw03.slnt.phub.net.cable.rogers.com [66.185.90.145]
4 20 ms 27 ms 19 ms so-5-1-3.gw02.ym.phub.net.cable.rogers.com [66.185.81.178]
5 21 ms 24 ms 27 ms 209.148.224.254
6 15 ms 22 ms 11 ms ae53.edge1.Toronto2.Level3.net [4.31.208.129]
7 * 113 ms 109 ms ae-1-60.ear2.Frankfurt1.Level3.net [4.69.154.20]
8 * * * Request timed out.
9 123 ms 119 ms 118 ms dialup-212.162.19.162.frankfurt1.mik.net [212.162.19.162]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

 

Tracing route to 162.249.72.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms ion [192.168.130.1]
2 * * * Request timed out.
3 20 ms 20 ms 16 ms gw03.slnt.phub.net.cable.rogers.com [66.185.90.145]
4 34 ms 132 ms 16 ms so-5-1-3.gw02.ym.phub.net.cable.rogers.com [66.185.81.178]
5 * 16 ms 19 ms 209.148.224.254
6 13 ms 11 ms 16 ms ae53.edge1.Toronto2.Level3.net [4.31.208.129]
7 * * * Request timed out.
8 * * * Request timed out.
9 121 ms 121 ms 119 ms dialup-212.162.19.162.frankfurt1.mik.net [212.162.19.162]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

 

Also this one in EUNE:

 

1 <1 ms <1 ms <1 ms ion [192.168.130.1]
2 * * * Request timed out.
3 15 ms 16 ms 16 ms 66.185.90.149
4 32 ms 19 ms 14 ms pos-0-0.gw01.pr.phub.net.cable.rogers.com [66.185.81.174]
5 28 ms 30 ms 27 ms 69.63.248.89
6 * * * Request timed out.
7 107 ms 113 ms 110 ms ae-3-80.ear2.Frankfurt1.Level3.net [4.69.154.149]
8 * * * Request timed out.
9 * * * Request timed out.

 

1 <1 ms <1 ms <1 ms ion [192.168.130.1]
2 * * * Request timed out.
3 19 ms 19 ms 15 ms 66.185.90.149
4 20 ms 24 ms 19 ms pos-0-0.gw01.pr.phub.net.cable.rogers.com [66.185.81.174]
5 33 ms 28 ms 30 ms 69.63.248.89
6 * * * Request timed out.
7 * * 111 ms ae-3-80.ear2.Frankfurt1.Level3.net [4.69.154.149]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.

 

 

(EDIT: Noticed that the source IP I used was not captured here. It's 95.172.65.100)

 

 

As a network administrator, seeing these kind of irregular responses would be a concern that I would need to address if this was my network. 🙂

 

Again, this could be nothing but I suspect these bad traces are the cause for the blame of defective modems with Rogers when reality, it is not. I suspect the upstream provider Rogers is using causing the problem.

 

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

RogersAsif
Retired Moderator
Retired Moderator

Hi @gisuck

 

Thank you for the information. Our team has flagged the issue and are looking to see if we can have a further analysis conducted.

 

Community, continue to provide us with as much information as you can on the type of issues you guys are encountering. 

 

We hope to provide you guys with a solution to your problems or an explanation on what is occurring.

 

RogersAsif

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

mfriers
I Plan to Stick Around

I have completed ruled out the PC to be the problem.    I made a bunch of changes to the modem (firewall settings/port forwarding rules) and can't get League of Legends to run.    I tried both hard wired connections from my pc and wifi to the mode, both net no connectivity to the game.

 

I decided to try connecting my pc to the wifi hotspot on my phone and game connected each time without issue.   So, I have for sure ruled out misconfiguration of the PC completely.

 

I then started focusing more energy on the port forwarding rules required by League of Legends.   The folowing port forwarding rules have been setup.

 

LOL-Client  5000~5500  5000~5500  TCP/UDP  192.168.0.10  Any
LOL-Patcher  8393~8400  8393~8400  TCP  192.168.0.10  Any 
LOL-PVP1  2099~2099  2099~2099  TCP  192.168.0.10  Any 
LOL-HTTP  80~80  80~80  TCP  192.168.0.10  Any 
LOL-HTTPS  443~443  443~443  TCP  192.168.0.10  Any 
LOL-Spectator  8088~8088  8088~8088  TCP/UDP  192.168.0.10  Any

 

I then turned off the firewall completely on the modem, the game still would not connect.  I also tried firewall settings minimum, custom, a few combinations.   

 

When do the port forwarding rules execute?   If you set firewall settings to minimum, will it still execute the port forwarding rules I defined?

 

The game will intermittently start when playing with the settings on your modem (but it has zero consistency - 1 out of every 20 times).

 

The issue is clearly with this modem.   Any suggestions would be greatly appreciated at this point.

 

 

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

gisuck
I'm a Reliable Contributor

Well this is rather strange. Just decided to do a trace route test and now I'm noticing I'm no longer able to reach the riot games gw server for North America.

 

1  ion (192.168.130.1)  1.228 ms  0.656 ms  0.735 ms

2  * * *

3  66.185.90.149 (66.185.90.149)  21.950 ms  22.764 ms  15.155 ms

4  24.153.5.141 (24.153.5.141)  18.712 ms  17.179 ms  16.186 ms

5  so-5-1-3.gw02.ym.phub.net.cable.rogers.com (66.185.81.178)  17.208 ms  23.836 ms  19.485 ms

6  24.156.144.125 (24.156.144.125)  16.553 ms  21.579 ms  24.400 ms

7  24.156.144.178 (24.156.144.178)  34.798 ms  35.867 ms  34.047 ms

8  * * *

9  * * *

10  * * *

 

 

 

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

gisuck
I'm a Reliable Contributor
Hi @RogersAsif,

Can you look at my previous post and update the support ticket you have open for this issue? Looks like North America Riot Servers is no longer routable. The last IP address listed here appears to be a Rogers router and then ends.

I suspect people who are affected by this problem are not able to play League of Legends at this moment.

Re: New CGN3ACSMR Modem, not compatible with League of Legends?

gisuck
I'm a Reliable Contributor

Something really fishy is going on. Moments later, now I'm able to route out?

 

1 <1 ms <1 ms <1 ms 192.168.130.1
2 * * * Request timed out.
3 18 ms 15 ms 23 ms 66.185.90.149
4 18 ms 17 ms 20 ms 24.153.5.141
5 25 ms 30 ms 23 ms so-5-1-3.gw02.ym.phub.net.cable.rogers.com [66.1
85.81.178]
6 25 ms 22 ms 18 ms 24.156.144.125
7 30 ms 30 ms 31 ms 24.156.144.178
8 25 ms 36 ms 30 ms eqix-ch2.riotgamesdirect.com [206.223.119.235]
9 33 ms 27 ms 30 ms 104.160.131.46
10 63 ms 72 ms 72 ms 104.160.159.11
11 67 ms 69 ms 65 ms 104.160.159.11
12 80 ms 71 ms 69 ms 104.160.159.2
13 77 ms 67 ms 73 ms 104.160.128.101