New CGN3ACSMR Modem, not compatible with League of Legends?

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
I'm a Reliable Contributor
Posts: 156

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

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

 

 

 

I'm a Reliable Contributor
Posts: 156

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

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.
I'm a Reliable Contributor
Posts: 156

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

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

I Plan to Stick Around
Posts: 35

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

So what is the difference between CGN3ACR and CGNACRSMR? It seems they have different firmware versions too.

I Plan to Stick Around
Posts: 15

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

update  - response from Riot game player support that cites bad firmware on CGN3ACSMR Modem

 

 

*************** (Riot Games Player Support)

May 5, 11:42

 

I'm ****'s personal Tech with Riot Games Technical Support. Based on the information that you have provided, I suspect that it is 100% the modem.

 

I noticed in your networkinfo log you are using Hitron hardware. Currently Hitron's hardware has bad firmware, and cause the issues that you are experiencing. If you have a Hitron router/modem, I recommend that you contact your ISP and ask them to swap out your hardware; hopefully they have something other than Hitron in stock.

 

Additionally,  the more people that contact Hitron Technologies, Rogers, about the problem, the more pressure it puts on them to fix it. If you tell this division of Rogers about the problem they will also submit a support ticket directly to the modem manufacturer.

 

-------------------------------------------------------------------

 

Ok... so now that narrows things down, do we have a chance of this getting fixed?

I Plan to Stick Around
Posts: 24

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

Thank you mfriers. I've been thinking that is the problem but haven't been able to fully prove it. Hopefully it get fixed soon.
I've Been Here Awhile
Posts: 4

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

I did a 100 hop tracert of the Riot NA Server it routes successfully to the 13th hop then it keeps trying to route endlessly beyond that. FYI I've never seen any other modem route beyond 30 hops to the NA server.

 

Tracing route to INTEL_CE_LINUX [192.64.170.252]

over a maximum of 100 hops:

 
  1    18 ms     9 ms     8 ms  hitronhub.home [192.168.0.1]
  2    23 ms    20 ms    23 ms  INTEL_CE_LINUX [7.11.162.193]
  3    24 ms    25 ms    33 ms  INTEL_CE_LINUX [69.63.242.73]
  4    30 ms    28 ms    26 ms  INTEL_CE_LINUX [24.156.157.81]
  5    31 ms    25 ms    28 ms  INTEL_CE_LINUX [24.156.144.129]
  6    36 ms    33 ms    43 ms  van58-10-228-226.dynamic.rogerstelecom.net [209.
148.228.226]
  7    36 ms    40 ms    38 ms  eqix-ch2.riotgamesdirect.com [206.223.119.235]
  8    39 ms    38 ms    43 ms  INTEL_CE_LINUX [104.160.131.44]
  9    34 ms    38 ms    36 ms  INTEL_CE_LINUX [104.160.159.8]
 10    97 ms    78 ms    74 ms  INTEL_CE_LINUX [104.160.159.2]
 11    83 ms    81 ms    75 ms  INTEL_CE_LINUX [104.160.159.1]
 12    79 ms    92 ms    86 ms  INTEL_CE_LINUX [104.160.128.103]
 13    93 ms    93 ms    80 ms  INTEL_CE_LINUX [104.160.128.103]
 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.
 31     *        *        *     Request timed out.
 32     *        *        *     Request timed out.
 33     *        *        *     Request timed out.
 34     *        *        *     Request timed out.
 35     *        *        *     Request timed out.
 36     *        *        *     Request timed out.
 37     *        *        *     Request timed out.
 38     *        *        *     Request timed out.
 39     *        *        *     Request timed out.
 40     *        *        *     Request timed out.
 41     *        *        *     Request timed out.
 42     *        *        *     Request timed out.
 43     *        *        *     Request timed out.
 44     *        *        *     Request timed out.
 45     *        *        *     Request timed out.
 46     *        *        *     Request timed out.
 47     *        *        *     Request timed out.
 48     *        *        *     Request timed out.
 49     *        *        *     Request timed out.
 50     *        *        *     Request timed out.
 51     *        *        *     Request timed out.
 52     *        *        *     Request timed out.
 53     *        *        *     Request timed out.
 54     *        *        *     Request timed out.
 55     *        *        *     Request timed out.
 56     *        *        *     Request timed out.
 57     *        *        *     Request timed out.
 58     *        *        *     Request timed out.
 59     *        *        *     Request timed out.
 60     *        *        *     Request timed out.
 61     *        *        *     Request timed out.
 62     *        *        *     Request timed out.
 63     *        *        *     Request timed out.
 64     *        *        *     Request timed out.
 65     *        *        *     Request timed out.
 66     *        *        *     Request timed out.
 67     *        *        *     Request timed out.
 68     *        *        *     Request timed out.
 69     *        *        *     Request timed out.
 70     *        *        *     Request timed out.
 71     *        *        *     Request timed out.
 72     *        *        *     Request timed out.
 73     *        *        *     Request timed out.
 74     *        *        *     Request timed out.
 75     *        *        *     Request timed out.
 76     *        *        *     Request timed out.
 77     *        *        *     Request timed out.
 78     *        *        *     Request timed out.
 79     *        *        *     Request timed out.
 80     *        *        *     Request timed out.
 81     *        *        *     Request timed out.
 82     *        *        *     Request timed out.
 83     *        *        *     Request timed out.
 84     *        *        *     Request timed out.
 85     *        *        *     Request timed out.
 86     *        *        *     Request timed out.
 87     *        *        *     Request timed out.
 88     *        *        *     Request timed out.
 89     *        *        *     Request timed out.
 90     *        *        *     Request timed out.
 91     *        *        *     Request timed out.
 92     *        *        *     Request timed out.
 93     *        *        *     Request timed out.
 94     *        *        *     Request timed out.
 95     *        *        *     Request timed out.
 96     *        *        *     Request timed out.
 97     *        *        *     Request timed out.
 98     *        *        *     Request timed out.
 99     *        *        *     Request timed out.
100     *        *        *     Request timed out.
 
Trace complete.

I've Been Here Awhile
Posts: 4

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

This could potentially be the cause of the issues with the CNG3ACSMR and League of Legends. It seems the requests to the Riot NA Servers are entering into an endless routing loop that times out requests to the servers. Don't know what the difference is in the CGN3ACSMR and the DPC3825 I had previously that would cause this issue but it seems like a big issue. 

Resident Expert
Resident Expert
Posts: 6,015

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

There might be a way to prove what the problem is, or at least determine if its port related.  @mfriers, if you could load Wireshark on your pc and manage to fire it up to run a capture session, you might be able to see a difference in the connection ports when the modem is used as opposed to your phone.  If you fire it up, hit the green shark fin button to start a capture and then right right click on the column names to bring up the column preferences, you can add the Destination Port (resolved) to the columns.  With that done, start the game and then shut down the game and stop the capture.  Save that session.  Then run another session on the other device.  Save the session.  With two short sessions, it might be possible to compare the two of them and determine if the CGN3ACSMR is causing a port problem and therefore a game failure.  Food for thought....

 

RogersAsif, this also applies to yourself if you have access to the CGN3, CGN3ACR and CGN3ACSMR.  You should have access to network experts who can read through the captured data and determine if the CGN3ACSMR is causing a port problem.



I've Been Around
Posts: 1

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

The problem is not only with League but with game consoles as well. Multiple NAT type errors experienced on the ps4 when we switched to rogers ignite internet and were given the CGN3ACSMR (this had never happened before on the old modem). I called the support team and we've done everything we could possibly do to open the necessary ports for the PlayStation, to no avail. I Can play games just fine but I'm unable to communicate with my friends without running into constant NAT errors. Been surfing the web and it appears to be bad firmware on hitron. Have already ruled out the ps4 and the bungie servers as the issue. Wired connection has no effect either. This is definitely something wrong with the router as these problems only began to manifest when we changed to CGNACSMR. Any info on a fix is greatly appreciated.