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 Plan to Stick Around
Posts: 10

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

I PM'ed you the whole test.

Resident Expert
Resident Expert
Posts: 6,141

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

Got it, thanks very much. Here's the interesting part for all to see:

 

Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=125ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

 

There is an occasional excursion up to something in the 10 ms range, and then every once in a while some wacky time over 100 ms.  Very interesting indeed.  Its still a vast improvement over what I see with my CGN3.



I Plan to Stick Around
Posts: 10

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

Glad I could help. I hope LoL is going to start working for other people soon

 

Highlighted
I've Been Here Awhile
Posts: 3

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

I messaged community this afternoon the details of modem and account.

Just got the updated firmware.

Thank you very much!

First game a success!

 

I've Been Here Awhile
Posts: 4

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

Post Firmware upgrade update, light load

 

Ping statistics for 10.10.10.1:
Packets: Sent = 291, Received = 291, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 64ms, Average = 1ms

Hardware Version1A
Software Version4.5.8.16

 

105/31/15 06:29:4369010100noticeSW Download INIT - Via NMS
205/31/15 06:34:2969011100noticeSW download Successful - Via NMS

 

Dramatic improvement over previous .13 firmware.

 

Some ping data from local Debian server as well...

 

64 bytes from 10.10.10.1: icmp_seq=9037 ttl=64 time=1.34 ms
64 bytes from 10.10.10.1: icmp_seq=9038 ttl=64 time=5.02 ms
64 bytes from 10.10.10.1: icmp_seq=9039 ttl=64 time=3.80 ms
64 bytes from 10.10.10.1: icmp_seq=9040 ttl=64 time=1.78 ms
64 bytes from 10.10.10.1: icmp_seq=9041 ttl=64 time=2.28 ms
64 bytes from 10.10.10.1: icmp_seq=9042 ttl=64 time=3.64 ms
64 bytes from 10.10.10.1: icmp_seq=9043 ttl=64 time=9.64 ms
64 bytes from 10.10.10.1: icmp_seq=9044 ttl=64 time=19.1 ms
64 bytes from 10.10.10.1: icmp_seq=9045 ttl=64 time=2.64 ms
64 bytes from 10.10.10.1: icmp_seq=9046 ttl=64 time=66.9 ms
64 bytes from 10.10.10.1: icmp_seq=9047 ttl=64 time=2.23 ms
64 bytes from 10.10.10.1: icmp_seq=9048 ttl=64 time=6.42 ms
64 bytes from 10.10.10.1: icmp_seq=9049 ttl=64 time=3.52 ms
64 bytes from 10.10.10.1: icmp_seq=9050 ttl=64 time=3.23 ms
64 bytes from 10.10.10.1: icmp_seq=9051 ttl=64 time=1.27 ms
64 bytes from 10.10.10.1: icmp_seq=9052 ttl=64 time=1.40 ms
64 bytes from 10.10.10.1: icmp_seq=9053 ttl=64 time=7.91 ms
64 bytes from 10.10.10.1: icmp_seq=9054 ttl=64 time=4.58 ms
64 bytes from 10.10.10.1: icmp_seq=9055 ttl=64 time=1.80 ms
64 bytes from 10.10.10.1: icmp_seq=9056 ttl=64 time=2.45 ms
64 bytes from 10.10.10.1: icmp_seq=9057 ttl=64 time=5.45 ms
64 bytes from 10.10.10.1: icmp_seq=9058 ttl=64 time=3.69 ms
64 bytes from 10.10.10.1: icmp_seq=9059 ttl=64 time=1.37 ms
64 bytes from 10.10.10.1: icmp_seq=9060 ttl=64 time=2.07 ms
64 bytes from 10.10.10.1: icmp_seq=9061 ttl=64 time=4.44 ms
64 bytes from 10.10.10.1: icmp_seq=9062 ttl=64 time=2.23 ms
64 bytes from 10.10.10.1: icmp_seq=9063 ttl=64 time=4.34 ms
64 bytes from 10.10.10.1: icmp_seq=9064 ttl=64 time=1.34 ms
64 bytes from 10.10.10.1: icmp_seq=9065 ttl=64 time=8.95 ms
64 bytes from 10.10.10.1: icmp_seq=9066 ttl=64 time=3.53 ms
64 bytes from 10.10.10.1: icmp_seq=9067 ttl=64 time=1.30 ms
64 bytes from 10.10.10.1: icmp_seq=9068 ttl=64 time=2.47 ms
64 bytes from 10.10.10.1: icmp_seq=9069 ttl=64 time=1.04 ms
64 bytes from 10.10.10.1: icmp_seq=9070 ttl=64 time=9.57 ms
64 bytes from 10.10.10.1: icmp_seq=9071 ttl=64 time=6.61 ms
64 bytes from 10.10.10.1: icmp_seq=9072 ttl=64 time=7.41 ms
64 bytes from 10.10.10.1: icmp_seq=9073 ttl=64 time=6.41 ms
64 bytes from 10.10.10.1: icmp_seq=9074 ttl=64 time=5.02 ms
64 bytes from 10.10.10.1: icmp_seq=9075 ttl=64 time=3.82 ms
64 bytes from 10.10.10.1: icmp_seq=9076 ttl=64 time=9.29 ms
64 bytes from 10.10.10.1: icmp_seq=9077 ttl=64 time=1.30 ms
64 bytes from 10.10.10.1: icmp_seq=9078 ttl=64 time=4.85 ms
64 bytes from 10.10.10.1: icmp_seq=9079 ttl=64 time=8.85 ms
64 bytes from 10.10.10.1: icmp_seq=9080 ttl=64 time=2.15 ms
64 bytes from 10.10.10.1: icmp_seq=9081 ttl=64 time=3.79 ms
64 bytes from 10.10.10.1: icmp_seq=9082 ttl=64 time=4.01 ms
64 bytes from 10.10.10.1: icmp_seq=9083 ttl=64 time=1.87 ms
64 bytes from 10.10.10.1: icmp_seq=9084 ttl=64 time=69.1 ms
64 bytes from 10.10.10.1: icmp_seq=9085 ttl=64 time=1.35 ms
64 bytes from 10.10.10.1: icmp_seq=9086 ttl=64 time=10.0 ms
64 bytes from 10.10.10.1: icmp_seq=9087 ttl=64 time=8.63 ms
64 bytes from 10.10.10.1: icmp_seq=9088 ttl=64 time=2.76 ms
64 bytes from 10.10.10.1: icmp_seq=9089 ttl=64 time=6.93 ms
64 bytes from 10.10.10.1: icmp_seq=9090 ttl=64 time=4.34 ms
64 bytes from 10.10.10.1: icmp_seq=9091 ttl=64 time=3.78 ms
64 bytes from 10.10.10.1: icmp_seq=9092 ttl=64 time=2.49 ms
64 bytes from 10.10.10.1: icmp_seq=9093 ttl=64 time=2.41 ms
64 bytes from 10.10.10.1: icmp_seq=9094 ttl=64 time=3.65 ms
64 bytes from 10.10.10.1: icmp_seq=9095 ttl=64 time=2.67 ms
64 bytes from 10.10.10.1: icmp_seq=9096 ttl=64 time=2.98 ms
64 bytes from 10.10.10.1: icmp_seq=9097 ttl=64 time=7.07 ms
64 bytes from 10.10.10.1: icmp_seq=9098 ttl=64 time=2.74 ms
64 bytes from 10.10.10.1: icmp_seq=9099 ttl=64 time=4.33 ms
64 bytes from 10.10.10.1: icmp_seq=9100 ttl=64 time=1.89 ms
64 bytes from 10.10.10.1: icmp_seq=9101 ttl=64 time=19.7 ms
64 bytes from 10.10.10.1: icmp_seq=9102 ttl=64 time=1.95 ms
64 bytes from 10.10.10.1: icmp_seq=9103 ttl=64 time=2.27 ms
64 bytes from 10.10.10.1: icmp_seq=9104 ttl=64 time=0.933 ms
64 bytes from 10.10.10.1: icmp_seq=9105 ttl=64 time=5.03 ms
64 bytes from 10.10.10.1: icmp_seq=9106 ttl=64 time=2.28 ms
64 bytes from 10.10.10.1: icmp_seq=9107 ttl=64 time=1.69 ms
64 bytes from 10.10.10.1: icmp_seq=9108 ttl=64 time=2.06 ms
64 bytes from 10.10.10.1: icmp_seq=9109 ttl=64 time=9.95 ms
64 bytes from 10.10.10.1: icmp_seq=9110 ttl=64 time=8.94 ms
64 bytes from 10.10.10.1: icmp_seq=9111 ttl=64 time=4.25 ms
64 bytes from 10.10.10.1: icmp_seq=9112 ttl=64 time=1.31 ms
64 bytes from 10.10.10.1: icmp_seq=9113 ttl=64 time=4.83 ms
64 bytes from 10.10.10.1: icmp_seq=9114 ttl=64 time=2.79 ms
64 bytes from 10.10.10.1: icmp_seq=9115 ttl=64 time=3.39 ms
64 bytes from 10.10.10.1: icmp_seq=9116 ttl=64 time=9.30 ms
64 bytes from 10.10.10.1: icmp_seq=9117 ttl=64 time=3.36 ms
64 bytes from 10.10.10.1: icmp_seq=9118 ttl=64 time=4.25 ms
64 bytes from 10.10.10.1: icmp_seq=9119 ttl=64 time=6.08 ms
64 bytes from 10.10.10.1: icmp_seq=9120 ttl=64 time=1.08 ms
64 bytes from 10.10.10.1: icmp_seq=9121 ttl=64 time=1.62 ms
64 bytes from 10.10.10.1: icmp_seq=9122 ttl=64 time=10.3 ms
64 bytes from 10.10.10.1: icmp_seq=9123 ttl=64 time=2.72 ms
64 bytes from 10.10.10.1: icmp_seq=9124 ttl=64 time=8.51 ms
64 bytes from 10.10.10.1: icmp_seq=9125 ttl=64 time=6.75 ms
64 bytes from 10.10.10.1: icmp_seq=9126 ttl=64 time=1.34 ms
64 bytes from 10.10.10.1: icmp_seq=9127 ttl=64 time=1.96 ms
64 bytes from 10.10.10.1: icmp_seq=9128 ttl=64 time=2.78 ms
64 bytes from 10.10.10.1: icmp_seq=9129 ttl=64 time=11.5 ms
64 bytes from 10.10.10.1: icmp_seq=9130 ttl=64 time=1.30 ms
64 bytes from 10.10.10.1: icmp_seq=9131 ttl=64 time=398 ms
64 bytes from 10.10.10.1: icmp_seq=9132 ttl=64 time=1.87 ms
64 bytes from 10.10.10.1: icmp_seq=9133 ttl=64 time=4.63 ms
From 10.10.10.200 icmp_seq=9177 Destination Host Unreachable

...this is when the update gets pushed, was back up in about 2 mins

64 bytes from 10.10.10.1: icmp_seq=20 ttl=64 time=0.815 ms
64 bytes from 10.10.10.1: icmp_seq=21 ttl=64 time=0.696 ms
64 bytes from 10.10.10.1: icmp_seq=22 ttl=64 time=0.798 ms
64 bytes from 10.10.10.1: icmp_seq=23 ttl=64 time=0.724 ms
64 bytes from 10.10.10.1: icmp_seq=24 ttl=64 time=0.772 ms
64 bytes from 10.10.10.1: icmp_seq=25 ttl=64 time=0.763 ms
64 bytes from 10.10.10.1: icmp_seq=26 ttl=64 time=0.739 ms
64 bytes from 10.10.10.1: icmp_seq=27 ttl=64 time=0.713 ms
64 bytes from 10.10.10.1: icmp_seq=28 ttl=64 time=0.790 ms
64 bytes from 10.10.10.1: icmp_seq=29 ttl=64 time=0.829 ms
64 bytes from 10.10.10.1: icmp_seq=30 ttl=64 time=0.741 ms
64 bytes from 10.10.10.1: icmp_seq=31 ttl=64 time=0.812 ms
64 bytes from 10.10.10.1: icmp_seq=32 ttl=64 time=0.733 ms
64 bytes from 10.10.10.1: icmp_seq=33 ttl=64 time=0.733 ms
64 bytes from 10.10.10.1: icmp_seq=34 ttl=64 time=3.79 ms
64 bytes from 10.10.10.1: icmp_seq=35 ttl=64 time=0.842 ms
64 bytes from 10.10.10.1: icmp_seq=36 ttl=64 time=1.35 ms
64 bytes from 10.10.10.1: icmp_seq=37 ttl=64 time=0.829 ms
64 bytes from 10.10.10.1: icmp_seq=38 ttl=64 time=0.804 ms
64 bytes from 10.10.10.1: icmp_seq=39 ttl=64 time=0.827 ms
64 bytes from 10.10.10.1: icmp_seq=40 ttl=64 time=1.53 ms
64 bytes from 10.10.10.1: icmp_seq=41 ttl=64 time=0.803 ms
64 bytes from 10.10.10.1: icmp_seq=42 ttl=64 time=10.3 ms
64 bytes from 10.10.10.1: icmp_seq=43 ttl=64 time=0.671 ms
64 bytes from 10.10.10.1: icmp_seq=44 ttl=64 time=1.26 ms
64 bytes from 10.10.10.1: icmp_seq=45 ttl=64 time=0.653 ms
64 bytes from 10.10.10.1: icmp_seq=46 ttl=64 time=0.703 ms
64 bytes from 10.10.10.1: icmp_seq=47 ttl=64 time=0.829 ms
64 bytes from 10.10.10.1: icmp_seq=48 ttl=64 time=0.833 ms
64 bytes from 10.10.10.1: icmp_seq=49 ttl=64 time=0.832 ms
64 bytes from 10.10.10.1: icmp_seq=50 ttl=64 time=0.763 ms
64 bytes from 10.10.10.1: icmp_seq=51 ttl=64 time=0.765 ms
64 bytes from 10.10.10.1: icmp_seq=52 ttl=64 time=1.00 ms
64 bytes from 10.10.10.1: icmp_seq=53 ttl=64 time=1.06 ms
64 bytes from 10.10.10.1: icmp_seq=54 ttl=64 time=0.737 ms
64 bytes from 10.10.10.1: icmp_seq=55 ttl=64 time=0.708 ms
64 bytes from 10.10.10.1: icmp_seq=56 ttl=64 time=0.800 ms
64 bytes from 10.10.10.1: icmp_seq=57 ttl=64 time=8.51 ms
64 bytes from 10.10.10.1: icmp_seq=58 ttl=64 time=0.704 ms
64 bytes from 10.10.10.1: icmp_seq=59 ttl=64 time=0.810 ms
64 bytes from 10.10.10.1: icmp_seq=60 ttl=64 time=0.699 ms
64 bytes from 10.10.10.1: icmp_seq=61 ttl=64 time=0.749 ms
64 bytes from 10.10.10.1: icmp_seq=62 ttl=64 time=0.703 ms
64 bytes from 10.10.10.1: icmp_seq=63 ttl=64 time=0.785 ms
64 bytes from 10.10.10.1: icmp_seq=64 ttl=64 time=0.687 ms
64 bytes from 10.10.10.1: icmp_seq=65 ttl=64 time=0.738 ms
64 bytes from 10.10.10.1: icmp_seq=66 ttl=64 time=0.811 ms
64 bytes from 10.10.10.1: icmp_seq=67 ttl=64 time=0.797 ms
64 bytes from 10.10.10.1: icmp_seq=68 ttl=64 time=0.748 ms
64 bytes from 10.10.10.1: icmp_seq=69 ttl=64 time=0.700 ms

 

Verdict

 

Excellent result.

Resident Expert
Resident Expert
Posts: 6,141

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

That looks really good, except for that one 8.51 ms result.  That single point is not terrible compared to the non-updated results but I'm wondering what is driving that time up.  Other runs that I have seen tonight have many more upward pops to single digit times.



Resident Expert
Resident Expert
Posts: 6,141

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

@g3tester congrats.  Nice to see the update working as planned.  Can you let us know what your ingame ping times are?



I've Been Here Awhile
Posts: 4

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

Here is some  more ping data under significant load running torrents and Iperf while Pinging the gateway to determine if ICMP requests would be deprioritized and balloon again.
Hardware Version 1A
Software Version 4.5.8.16

 

Ping statistics for 10.10.10.1:
Packets: Sent = 492, Received = 492, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 185ms, Average = 5ms

 

Some  simultaneous Iperf testing below, results mitigated by torrent traffic using bandwidth.

 

Client connecting to iperf.volia.net, TCP port 5001
TCP window size: 63.0 KByte (default)
------------------------------------------------------------
[ 7] local 10.10.10.10 port 56161 connected with 82.144.193.18 port 5001
[ 4] local 10.10.10.10 port 56158 connected with 82.144.193.18 port 5001
[ 5] local 10.10.10.10 port 56159 connected with 82.144.193.18 port 5001
[ 6] local 10.10.10.10 port 56160 connected with 82.144.193.18 port 5001
[ ID] Interval Transfer Bandwidth
[ 4] 0.0-10.5 sec 4.00 MBytes 3.19 Mbits/sec
[ 4] local 10.10.10.10 port 5001 connected with 82.144.193.18 port 59082
[ 8] local 10.10.10.10 port 5001 connected with 82.144.193.18 port 59080
[ 9] local 10.10.10.10 port 5001 connected with 82.144.193.18 port 59079
[ 10] local 10.10.10.10 port 5001 connected with 82.144.193.18 port 59081
[ 6] 0.0-10.9 sec 1.50 MBytes 1.15 Mbits/sec
[ 7] 0.0-11.3 sec 1.12 MBytes 836 Kbits/sec
[ 5] 0.0-11.6 sec 1.25 MBytes 907 Kbits/sec
[SUM] 0.0-11.6 sec 7.88 MBytes 5.72 Mbits/sec
[ 4] 0.0-11.0 sec 4.25 MBytes 3.23 Mbits/sec
[ 10] 0.0-11.2 sec 4.00 MBytes 3.00 Mbits/sec
[ 9] 0.0-11.3 sec 4.25 MBytes 3.16 Mbits/sec
[ 8] 0.0-11.5 sec 4.00 MBytes 2.92 Mbits/sec
[SUM] 0.0-11.5 sec 16.5 MBytes 12.0 Mbits/sec
[SUM] Sent 8 datagrams

 


Not fantastic but  very reasonable.  ICMP requests are not being dropped in favour of TCP/UDP in the same fashion as pre upgrade.

 

I'm Here A Lot
Posts: 7

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

My software version is now: 4.5.8.16

 

I have played about 15 games today and all have worked without any issues.

 

I do however, now see a different issue. Upon logging in, the first time I hit enter I get a failed connection error. After which, my game closes and upon logging in for a second time, I connect correctly. This seems to be prevelant whenever I stop playing for a while and log back into the game. I have tested this throughout the day and received the connection error once upon every log in attempt. By far a way nicer error to deal with as it does not inturrupt the game itself but still seems like a small tweak is required to fix this connection issue fully.

I Plan to Stick Around
Posts: 14

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

@nourel that oroblem isn't related to Rogers or Hitron router, it's happening to a lot of my friends, as well as my self. It just started happening after the recent 5.10 patch i believe. Riot themselves will have to fix this problem. 

Also my modem rebooted and updated it's firmware a couple hours ago after i sent a message to communityhelp, resolved my issue as well. Getting a ping of 72m/s in game, same as i use to get before with Bell. Thanks for the help!