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
Moderator
Moderator
Posts: 1,436

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

 

Hello, @AllanLin

 

Thank you for your patience. I'd like to help in resolving the issue since we need to access your account I’m going to send you a private message from CommunityHelps.

 

Please check our message via the envelope icon that appears on the top right-hand side of your screen when you are logged in to the forums.

 

Thank you for understanding!

RogersMoin

 

@Datalink - Thank you for all the probing and assistance.

Resident Expert
Resident Expert
Posts: 6,015

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

@AllanLin if you have a disconnect occur, try to log into the modem to check the signal level.  With a two minute or so window, that doesn't give you much time.  I'm wondering if the signal level is spiking upwards for some reason, causing the modem to drop the connection until it comes back down a reasonable level.  The related question is, does the modem stay up and running, as seen by the front LEDs remaining lit, or are you seeing a fast reboot occur?

 

Keep tracking the WinMRT results to see how it changes over time.  That will give you, and the moderators a much better idea of what is going on with the traffic thru the neighborhood node.

 

The attenuator, you might be able to find one, but I wouldn't bet on it.  If you can't find one with a 7 or 8 db drop to replace the splitter but you're able to find the terminators, use the terminators on the unoccupied ports.



I Plan to Stick Around
Posts: 25

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

yay. i did get those terminator. the ping is somehow more stable than the time at 6:51 yesterday after i use those terminator. but sometime it still goes up for some minute. i think it is signal problem. i have to check the winMTR after 7:30 to make sure the ping still good.

 

below is winMTR at 6:39pm

ingame ping 36-110ms
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 107 | 107 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| 209.148.245.149 - 1 | 103 | 102 | 11 | 45 | 178 | 11 |
| 24.153.5.126 - 1 | 103 | 102 | 11 | 45 | 180 | 13 |
|so-5-0-3.gw02.mtnk.phub.net.cable.rogers.com - 1 | 103 | 102 | 13 | 43 | 156 | 14 |
|pos-4-0-0.gw01.ktgc.phub.net.cable.rogers.com - 1 | 103 | 102 | 15 | 48 | 181 | 19 |
| 24.156.157.86 - 1 | 103 | 102 | 15 | 47 | 177 | 20 |
|cal58-5-199-44.dynamic.rogerstelecom.net - 1 | 103 | 102 | 12 | 44 | 178 | 15 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

PS: after the ping go up and back down. i cant access to the modem via 192.168.100.1. i have to restart the modem to aceess it. T_T

Resident Expert
Resident Expert
Posts: 6,015

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

At this point, if you look carefully at the WinMRT ping times, you can see that the average and worst case ping times have doubled from this morning, in some cases tripled.  Keep tracking the WinMRT results please.  

 

At some point can you run a ping test to google and post those results:  ping www.google.com -n 20

 

 



I Plan to Stick Around
Posts: 25

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

This is the ping test result

 

ping www.google.com /n 20

Pinging www.google.com [209.148.199.54] with 32 bytes of data:
Reply from 209.148.199.54: bytes=32 time=66ms TTL=58
Reply from 209.148.199.54: bytes=32 time=107ms TTL=58
Reply from 209.148.199.54: bytes=32 time=96ms TTL=58
Reply from 209.148.199.54: bytes=32 time=26ms TTL=58
Reply from 209.148.199.54: bytes=32 time=14ms TTL=58
Reply from 209.148.199.54: bytes=32 time=19ms TTL=58
Reply from 209.148.199.54: bytes=32 time=183ms TTL=58
Reply from 209.148.199.54: bytes=32 time=62ms TTL=58
Reply from 209.148.199.54: bytes=32 time=277ms TTL=58
Reply from 209.148.199.54: bytes=32 time=49ms TTL=58
Reply from 209.148.199.54: bytes=32 time=18ms TTL=58
Reply from 209.148.199.54: bytes=32 time=79ms TTL=58
Reply from 209.148.199.54: bytes=32 time=12ms TTL=58
Reply from 209.148.199.54: bytes=32 time=41ms TTL=58
Reply from 209.148.199.54: bytes=32 time=126ms TTL=58
Reply from 209.148.199.54: bytes=32 time=33ms TTL=58
Reply from 209.148.199.54: bytes=32 time=104ms TTL=58
Reply from 209.148.199.54: bytes=32 time=23ms TTL=58
Reply from 209.148.199.54: bytes=32 time=38ms TTL=58
Reply from 209.148.199.54: bytes=32 time=43ms TTL=58

Ping statistics for 209.148.199.54:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 277ms, Average = 70ms

 

started to get high ping now T_T

7:19 pm

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 100 | 100 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| 209.148.245.153 - 0 | 100 | 100 | 12 | 70 | 368 | 71 |
|so-5-0-3.gw02.mtnk.phub.net.cable.rogers.com - 0 | 100 | 100 | 9 | 73 | 364 | 76 |
|pos-4-0-0.gw01.ktgc.phub.net.cable.rogers.com - 0 | 100 | 100 | 15 | 73 | 369 | 74 |
| 24.156.157.86 - 0 | 100 | 100 | 15 | 74 | 370 | 75 |
|cal58-5-199-39.dynamic.rogerstelecom.net - 0 | 100 | 100 | 11 | 70 | 372 | 77 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

ping www.google.com /n 20

Pinging www.google.com [209.148.199.39] with 32 bytes of data:
Reply from 209.148.199.39: bytes=32 time=21ms TTL=58
Reply from 209.148.199.39: bytes=32 time=103ms TTL=58
Reply from 209.148.199.39: bytes=32 time=281ms TTL=58
Reply from 209.148.199.39: bytes=32 time=143ms TTL=58
Reply from 209.148.199.39: bytes=32 time=448ms TTL=58
Reply from 209.148.199.39: bytes=32 time=78ms TTL=58
Reply from 209.148.199.39: bytes=32 time=168ms TTL=58
Reply from 209.148.199.39: bytes=32 time=269ms TTL=58
Reply from 209.148.199.39: bytes=32 time=164ms TTL=58
Reply from 209.148.199.39: bytes=32 time=313ms TTL=58
Reply from 209.148.199.39: bytes=32 time=62ms TTL=58
Reply from 209.148.199.39: bytes=32 time=87ms TTL=58
Reply from 209.148.199.39: bytes=32 time=132ms TTL=58
Reply from 209.148.199.39: bytes=32 time=20ms TTL=58
Reply from 209.148.199.39: bytes=32 time=205ms TTL=58
Reply from 209.148.199.39: bytes=32 time=27ms TTL=58
Reply from 209.148.199.39: bytes=32 time=19ms TTL=58
Reply from 209.148.199.39: bytes=32 time=48ms TTL=58
Reply from 209.148.199.39: bytes=32 time=60ms TTL=58
Reply from 209.148.199.39: bytes=32 time=21ms TTL=58

Ping statistics for 209.148.199.39:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 448ms, Average = 133ms

Highlighted
I'm Here A Lot
Posts: 7

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

Trying to play league of legends and I keep getting lag spikes. Just started 2 months ago and is always like this.

This has become  absurd to the point where I have to run a tracert before I play my games to check the lag...

 

A game where everyone else is getting 20-30 ping and I am getting 80-120 more than twice as much..

 


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

  1     *        2 ms    <1 ms  hitronhub.home [192.168.0.1]
  2    35 ms   169 ms    29 ms  INTEL_CE_LINUX [7.11.163.5]
  3    45 ms    33 ms    39 ms  INTEL_CE_LINUX [209.148.245.177]
  4   198 ms    70 ms    59 ms  INTEL_CE_LINUX [69.63.248.185]
  5    60 ms    59 ms   149 ms  van58-10-228-226.dynamic.rogerstelecom.net [209.148.228.226]
  6    49 ms    89 ms    59 ms  INTEL_CE_LINUX [104.160.131.1]

Trace complete.

Resident Expert
Resident Expert
Posts: 6,015

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

1.  Are you running an ethernet or wifi connected device?

2.  Can you log into the modem, navigate to the STATUS.... DOCSIS WAN page, copy the downstream and upstream tables and

      paste them into the thread.

3.  Can you run a wired speedtest at http://speedcheck.rogers.com/en.html and www.speedtest.net using the Toronto Telus server

      and post the results.

4.  What internet plan are you on, 100/10 or 250/20?

5.  Are you located in a house or apartment, condo, highrise, etc, etc.

6.  By now that modem should be running firmware version 4.5.8.16.  While you are logged into the modem, can you check the

     Status page and confirm that.



I'm Here A Lot
Posts: 7

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

1) ethernet
2)
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 621000000 256QAM 6.400 56 40.366
2 579000000 256QAM 7.300 49 40.946
3 585000000 256QAM 7.300 50 40.946
4 591000000 256QAM 6.900 51 40.366
5 597000000 256QAM 6.200 52 40.946
6 603000000 256QAM 6.800 53 40.366
7 609000000 256QAM 7.200 54 40.946
8 615000000 256QAM 7.400 55 40.946
9 633000000 256QAM 6.000 57 40.946
10 639000000 256QAM 6.000 58 40.366
11 645000000 256QAM 5.900 59 40.366
12 651000000 256QAM 5.600 60 40.366
13 657000000 256QAM 5.600 61 40.946
14 663000000 256QAM 5.300 62 40.366
15 669000000 256QAM 5.400 63 40.366
16 675000000 256QAM 5.200 64 38.983
17 681000000 256QAM 5.500 65 40.946
18 687000000 256QAM 5.200 66 40.366
19 693000000 256QAM 5.400 67 40.946
20 699000000 256QAM 5.300 68 40.366
21 705000000 256QAM 5.100 69 40.366
22 711000000 256QAM 5.200 70 38.983
23 717000000 256QAM 4.800 71 38.983
24 723000000 256QAM 4.800 72 40.366
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID BandWidth
1 38596000 ATDMA - 16QAM 41.500 1 3200000
2 23700000 ATDMA - 16QAM 40.750 3 6400000
3 30596000 ATDMA - 16QAM 40.500 2 6400000

3) 131~ down 10~ up
4) 150/10
5) Apartment
6) Yeah I upgraded already a few months back, it worked fine this issue is different. That firmware issue was related to disconnects in game or not being able to connect. While this one is due to latency issues due to your Roger nodes inbetween me and the League of legends Servers which did not exist prior these past 2 month...
Resident Expert
Resident Expert
Posts: 6,015

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

Your downstream levels are high, but given the fact that you're in an apartment that doesn't surprise me.  The upstream levels are ok where they currently are.  The downstream levels shouldn't cause huge issues at the levels that they are currently at but I'd be happier to see them closer to 0 dBmV.  I would suspect that your modem is connected to a Multiple Dwelling Unit (MDU) which resides in a utility room in the basement of the apartment.  I wonder how much of this ia a network issue, with the delays that are seen on the tracert, and how much might be attributed to the MDU.  When an MDU issue comes up, it can be difficult and time comsuming to rectify.  Can you run a trace to google.ca and post the results, just to see how it turns out versus your previous trace.  Do the trace times ever drop down to a reasonable 20 to 40 ms across the board?



I'm Here A Lot
Posts: 7

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

I don't believe an MDU can play a role on causing a node outside of my vicinity to increase my latency...
Doing a simple google search on one of the nodes with a high ping namely 69.63.248.185 will show that it's location is outside of my building and hence not MDU related. Here is a link from google.
http://www.ip-tracker.org/locator/ip-lookup.php?ip=69.63.248.185

Here is my origional trace again for reference:
Tracing route to INTEL_CE_LINUX [104.160.131.1]
over a maximum of 30 hops:

1 * 2 ms <1 ms hitronhub.home [192.168.0.1]
2 35 ms 169 ms 29 ms INTEL_CE_LINUX [7.11.163.5]
3 45 ms 33 ms 39 ms INTEL_CE_LINUX [209.148.245.177]
4 198 ms 70 ms 59 ms INTEL_CE_LINUX [69.63.248.185]
5 60 ms 59 ms 149 ms van58-10-228-226.dynamic.rogerstelecom.net [209.148.228.226]
6 49 ms 89 ms 59 ms INTEL_CE_LINUX [104.160.131.1]

A second trace route for extra reference:

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

1 1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 93 ms 101 ms 108 ms INTEL_CE_LINUX [7.11.163.5]
3 69 ms 60 ms 99 ms INTEL_CE_LINUX [209.148.245.177]
4 106 ms 109 ms 439 ms INTEL_CE_LINUX [69.63.248.185]
5 102 ms 88 ms 79 ms van58-10-228-226.dynamic.rogerstelecom.net [209.148.228.226]
6 108 ms 89 ms 79 ms INTEL_CE_LINUX [104.160.131.1]

Trace complete.

A tracert on google.ca won't work. Their servers don't give priority to trace requests so all I am going to get are *'s back.
How about a good old test to rogers.ca ? That should be sufficient.

Unfortunately, the rest of the requests were *'s but all the nodes hit returned good pings.

Tracing route to rogers.ca [207.245.252.27]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 12 ms 19 ms 9 ms INTEL_CE_LINUX [7.11.163.5]
3 20 ms 29 ms 29 ms INTEL_CE_LINUX [209.148.245.173]
4 26 ms 19 ms 32 ms INTEL_CE_LINUX [69.63.248.181]
5 37 ms 19 ms 39 ms van58-9-230-6.dynamic.rogerstelecom.net [209.148.230.6]
6 30 ms 21 ms 18 ms ge10-0.gwy2-tor.bb.allstream.net [216.191.65.121]
7 21 ms 19 ms 29 ms 10ge4-11.hcap9-tor.bb.allstream.net [199.212.169.202]
8 18 ms 19 ms 60 ms 10ge4-11.hcap9-tor.bb.allstream.net [199.212.169.202]
9 29 ms 19 ms 29 ms 66-46-129-178.dedicated.allstream.net [66.46.129.178]

It looks like I am on a congested node for this specific game, why this occured recently and how can I get Rogers to change my node is why I am here. Any feedback on this matter will be greatly appreciated.