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
Resident Expert
Resident Expert
Posts: 6,015

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

Quickest solution would probably be to find a CGN3.  I'm not sure that would fully solve the problem.  What were you running before? 

 

Most reliable solution:  CGN3 in Bridge mode with your own router running in full router mode.



I Plan to Stick Around
Posts: 24

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

It is definitely the CGN3ACSMR. Like I've said in previous posts, I had the DPC3825 And never had any problems on my xbox. Even worth much slower internet. Now with the new upgrade I have packet loss on my xbox and can't fix it. I've done everything Microsoft wanted and still mothing. Port forwarding and making my xbox the DMZ host only made my NAT open. But I still have packet loss so I'm constantly disconnecting from game servers
Resident Expert
Resident Expert
Posts: 6,015

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

Not surprised Smiley Sad  Cisco:  acceptable results.  Hitron:  unacceptable results.

 

When you changed the modem, was it just a modem swap, or did a tech drop by and possibly install an inline amplifier in the cable system?  Do you happen to have other Rogers services and do you notice any problems with them?



Highlighted
I Plan to Stick Around
Posts: 24

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

Ya it's quite unfortunate. Do you think Hitron would know of a fix? I'm thinking I should contact them
Resident Expert
Resident Expert
Posts: 6,015

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

Believe me, they know about it, and they are under some pressure to issue a solution.  Unfortunately, its a firmware issue which is specific to their hardware vendor, so they are waiting for the hardware vendor to issue the baseline firmware to address the latency issues.  This is a problem for both Rogers and Shaw modems.



Resident Expert
Resident Expert
Posts: 13,829

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


@PawLoh23 wrote:
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.

This is slightly differen than the LoL issue.

 

The NAT problem, is present on the CGN3 and the CGN3AC modems.. its a deficiency, etc in the gateway portion itself.
BUT people who have bridged the unit, with their own router.. this problem has gone way with the consoles.

From the reports... the issue with LoL... is STILL present, even after bridging.

Makes me wonder, if there is some sort of routing table on the MODEM part itself.. and for whatever reason having issues with those IPs.



Resident Expert
Resident Expert
Posts: 13,829

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


@jordanmkasla200 wrote:

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.


 

These are interesting results.  Assuming this is the proper server IP address?
This leads me to beleive, its a RIOT problem and not rogers.

It appears by hop 7, its jumped onto the RIOT network... everything after that would then be within Riot.. it appears its boucing around and not able to find the right endpoint internally.

If you have NOT sent this to Riot, i would sugest it.
And for them if they come back saying its a hitron issue, is a load of bull.

Because..... I am on BUSINESS Bell Fiber, fiber optic into the building direct into a cisco 1800 router (i beleive).
And these are my results. (i only ran to 30, but sure it would go the same after)

Tracing route to 192.64.170.252 over a maximum of 30 hops

  1     6 ms     2 ms     1 ms  10.10.3.21
  2     1 ms     1 ms    <1 ms  10.10.3.249
  3     1 ms     1 ms     1 ms  206.47.188.185
  4     1 ms    12 ms    14 ms  tcore4-toronto47_1-0-0-2.net.bell.ca [64.230.49.
192]
  5    14 ms    15 ms    16 ms  tcore4-chicagocp_hundredgige0-3-0-0.net.bell.ca
[64.230.79.159]
  6    15 ms    14 ms    14 ms  bx6-chicagodt_0-7-0-0.net.bell.ca [64.230.79.87]

  7    15 ms    15 ms    15 ms  be4247.ccr21.ord03.atlas.cogentco.com [38.122.18
1.153]
  8    14 ms    14 ms    14 ms  38.122.181.130
  9    14 ms    14 ms    14 ms  38.122.181.130
 10    14 ms    14 ms    14 ms  104.160.131.46
 11    14 ms    14 ms    14 ms  104.160.159.8
 12    54 ms    54 ms    54 ms  104.160.159.11
 13    69 ms    58 ms    58 ms  104.160.159.1
 14    58 ms    58 ms    63 ms  104.160.128.103
 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.

 

Mine is at hop 10 but you see its on the same 104. network at Riot..  Where it gets lost.



Resident Expert
Resident Expert
Posts: 6,015

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

Here is another tracert to the same Riot address:

 

TRACEROUTE (using proto 1/icmp)

HOP RTT ADDRESS

1     0.00 ms router.asus.com (10.0.0.1)

2   17.00 ms 7.11.164.173

3   18.00 ms 67.231.220.25

4   19.00 ms 24.153.7.230

5   21.00 ms so-5-0-3.gw02.bloor.phub.net.cable.rogers.com (66.185.81.73)

6   30.00 ms van58-10-228-226.dynamic.rogerstelecom.net (209.148.228.226)

7   29.00 ms eqix-ch2.riotgamesdirect.com (206.223.119.235)

8   33.00 ms 104.160.131.46

9   27.00 ms 104.160.159.8

10 70.00 ms 104.160.159.11

11 76.00 ms 104.160.159.2

12 74.00 ms 104.160.159.1

13 75.00 ms 104.160.128.103

14 ... 30

 

Riot address range from Whois:  104.160.128.0 - 104.160.159.255

 

After hop 7, the remaining addresses are all Riot addresses.  So, beyond hop 13, the servers are not transmitting a response, therefore the trace times out.  That is a big problem with troubleshooting network paths to distant servers.  If the server is configured to not send a response to a ping, then, you're hooped.  You have no control over that, and no other immediate avenue to determine what the problem is other than to go through your own ISP so that the investigation takes place at an ISP to ISP level.  For that to happen you would have to be able discuss the matter with Rogers Network staff and find the one or two individuals who can understand the problem and have the time and authorization to look at this, ISP to ISP.

 

A small but interesting point is that both tracerts, Gdkitty's and mine show that Rogers is peering with Riot as seen by the hop from the Rogers network over to Riot's network:

 

6   30.00 ms van58-10-228-226.dynamic.rogerstelecom.net (209.148.228.226)

7   29.00 ms eqix-ch2.riotgamesdirect.com (206.223.119.235)



I'm Here A Lot
Posts: 7

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

I have the exact same problem!!!

Upgraded to Ignite250 6 days ago, started having problems right after switching the modem to CGN3ACSMR

The only online games I play are League of Legends, Warframe for pc and Warframe for ps4. Connection problems with all of them. Came over to friend's house and everything worked normally.

I tried running with ethernet cable only, wireless 2.4 or 5. I'm on Windows 8.1.

Here is tracert to League NA server that I play

 

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

1 6 ms 9 ms 9 ms hitronhub.home [192.168.0.1]
2 * * * Request timed out.
3 24 ms 19 ms 19 ms INTEL_CE_LINUX [209.148.243.225]
4 15 ms 23 ms 29 ms INTEL_CE_LINUX [69.63.249.86]
5 26 ms 16 ms 14 ms INTEL_CE_LINUX [69.63.249.77]
6 35 ms 127 ms 39 ms van58-10-228-226.dynamic.rogerstelecom.net [209.148.228.226]
7 36 ms 34 ms 34 ms eqix-ch2.riotgamesdirect.com [206.223.119.235]
8 34 ms 35 ms 39 ms INTEL_CE_LINUX [104.160.131.46]
9 31 ms 36 ms 59 ms INTEL_CE_LINUX [104.160.159.8]
10 80 ms 79 ms 71 ms INTEL_CE_LINUX [104.160.159.11]
11 72 ms 82 ms 78 ms INTEL_CE_LINUX [104.160.159.1]
12 80 ms 81 ms 75 ms INTEL_CE_LINUX [104.160.128.103]
13 78 ms 79 ms 89 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.

 

Will post Warframe's tracert as soon as I get their support's reply.

 

Already had Rogers technician come over and he suggested me to change the modem to the one that looks exactly same as my modem but doesn't have AC written on the front. Is that just CGN3 model? And if the problem still persists then change back to the one I had (looks like cheese modem with lots of holes, does anyone know the exact model?).

 

I hope Rogers will solve this issue.

 

btw what are the differences b/w CGN3ACSMR vs CGN3 ?

Resident Expert
Resident Expert
Posts: 13,829

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

The only difference between the CGN3 and CGN3ACSMR is that the latter has AC wireless.  The regular CGN3 is N only.
Other than that, practically identical.

 

With the NEW plan, you are not able to go back to the old one (the one with the holes), which is the CNG2.  They are not supported under the 250 plan.
(Nor would i really sugest it.. the 150 and higher plans, tend to choke and start getting congestion again with only 8 channel modems like the CGN2.. its the reason for the move to the CGN3 series which are 24)

 

Again, i am leary of that its just directly the modem/plans fault.


As with a BELL connection, i am getting the same results.