*** CGN3ACSMR - League of Legends – latency: firmware release pending

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,107

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

Have a look at the following thread from last Friday if you haven't done so already. 

 

http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/page/1/thread-...

 

That might give your some ideas of things to try.  Read thru it all first before you attempt any changes.



I've Been Here Awhile
Posts: 3

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

Will do. Thanks.

I Plan to Stick Around
Posts: 25

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

Hi,

 

I have same problem on my ignite 100 as well. Also i get multiple package lost when i ping google and league server.

 

ping www.google.com /n 100

 

Request timed out.
Request timed out.
Reply from 209.148.199.20: bytes=32 time=190ms TTL=58
Reply from 209.148.199.20: bytes=32 time=49ms TTL=58
Reply from 209.148.199.20: bytes=32 time=30ms TTL=58
Reply from 209.148.199.20: bytes=32 time=59ms TTL=58
Reply from 209.148.199.20: bytes=32 time=19ms TTL=58
Reply from 209.148.199.20: bytes=32 time=110ms TTL=58
Reply from 209.148.199.20: bytes=32 time=64ms TTL=58
Reply from 209.148.199.20: bytes=32 time=188ms TTL=58
Reply from 209.148.199.20: bytes=32 time=27ms TTL=58
Reply from 209.148.199.20: bytes=32 time=14ms TTL=58
Reply from 209.148.199.20: bytes=32 time=324ms TTL=58
Reply from 209.148.199.20: bytes=32 time=164ms TTL=58
Reply from 209.148.199.20: bytes=32 time=43ms TTL=58
Request timed out.
Reply from 209.148.199.20: bytes=32 time=348ms TTL=58
Reply from 209.148.199.20: bytes=32 time=213ms TTL=58
Reply from 209.148.199.20: bytes=32 time=206ms TTL=58
Reply from 209.148.199.20: bytes=32 time=42ms TTL=58
Reply from 209.148.199.20: bytes=32 time=47ms TTL=58
Reply from 209.148.199.20: bytes=32 time=88ms TTL=58
Reply from 209.148.199.20: bytes=32 time=144ms TTL=58
Reply from 209.148.199.20: bytes=32 time=61ms TTL=58
Reply from 209.148.199.20: bytes=32 time=59ms TTL=58
Reply from 209.148.199.20: bytes=32 time=174ms TTL=58
Reply from 209.148.199.20: bytes=32 time=23ms TTL=58
Reply from 209.148.199.20: bytes=32 time=15ms TTL=58
Request timed out.
Reply from 209.148.199.20: bytes=32 time=15ms TTL=58

Ping statistics for 209.148.199.20:
Packets: Sent = 100, Received = 92, Lost = 8 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 350ms, Average = 90ms

 

ping 104.160.131.1 /n 100

 

Reply from 104.160.131.1: bytes=32 time=61ms TTL=58
Reply from 104.160.131.1: bytes=32 time=72ms TTL=58
Reply from 104.160.131.1: bytes=32 time=128ms TTL=58
Reply from 104.160.131.1: bytes=32 time=135ms TTL=58
Reply from 104.160.131.1: bytes=32 time=82ms TTL=58
Reply from 104.160.131.1: bytes=32 time=126ms TTL=58
Reply from 104.160.131.1: bytes=32 time=70ms TTL=58
Reply from 104.160.131.1: bytes=32 time=228ms TTL=58
Reply from 104.160.131.1: bytes=32 time=186ms TTL=58
Reply from 104.160.131.1: bytes=32 time=25ms TTL=58
Reply from 104.160.131.1: bytes=32 time=55ms TTL=58
Reply from 104.160.131.1: bytes=32 time=68ms TTL=58
Reply from 104.160.131.1: bytes=32 time=45ms TTL=58
Reply from 104.160.131.1: bytes=32 time=32ms TTL=58
Reply from 104.160.131.1: bytes=32 time=183ms TTL=58
Reply from 104.160.131.1: bytes=32 time=67ms TTL=58
Reply from 104.160.131.1: bytes=32 time=34ms TTL=58
Reply from 104.160.131.1: bytes=32 time=139ms TTL=58
Reply from 104.160.131.1: bytes=32 time=86ms TTL=58
Reply from 104.160.131.1: bytes=32 time=31ms TTL=58
Reply from 104.160.131.1: bytes=32 time=269ms TTL=58
Reply from 104.160.131.1: bytes=32 time=237ms TTL=58
Reply from 104.160.131.1: bytes=32 time=193ms TTL=58
Reply from 104.160.131.1: bytes=32 time=36ms TTL=58
Reply from 104.160.131.1: bytes=32 time=55ms TTL=58
Reply from 104.160.131.1: bytes=32 time=40ms TTL=58

Ping statistics for 104.160.131.1:
Packets: Sent = 100, Received = 98, Lost = 2 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 337ms, Average = 85ms

I've Been Here Awhile
Posts: 3

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

CGN3ACSMR LED Lighs

 

 

I've just put my CGN3ACSMR modem into bridge mode and using a router for internet.

 

Works fine however I noticed the LED lights are still lit on the modem.

 

Is it normal for most of the modem light o remain lit after placing it to Bridg mode?

 

Is there anyway to turn them off?

 

 

 

***Edited Labels***

 

Retired Moderator RogersPrasana
Retired Moderator
Posts: 624

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

Hi @bobor

 

Welcome to Community Forums!

 

You've come to the right place for some assistence.

 

I'm sure one of our Resident Experts @Datalink or @Gdkitty can provide you with the answers.

 

 

@RogersPrasana

Moderator
Moderator
Posts: 1,510

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

 

Hello, @bobor

 

We've discussed this issue in the previous pages of this thread. The workaround is to disable 2.4GHz and 5GHz SSIDs before bridging. Thank you for your patience.

 

Cheers,

RogersMoin

Resident Expert
Resident Expert
Posts: 6,107

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

If you mean the top five LEDs, yes, that is normal.  The top four will remain lit while the fifth, the computer shaped LED indicates traffic over a connected ethernet port.  That LED will flash as long as there is traffic thru a connected ethernet port.  What you don't want is the wifi LEDs showing up when the modem is in Bridge mode.  That is due to a firmware bug in the current version, 4.5.8.16.  If you disable the wifi networks before kicking the modem into Bridge mode, they should remain inoperative.  Here's a link to the CGNV4 Manual, which is close to the CGN3ACSMR.  I haven't seen a manual for the CGN3ACSMR published, so this will have to suffice.  The manual contains a guide to the LEDs.

 

https://www.upc.ro/pdf/manuale/internet/HITRON_CGNV4_UG_V1-1_DRAFT_2014-01-28.pdf

 

Here is a link to the CGN3 user manual which is also close to the CGN3ACSMR modem.

 

https://www.midco.com/contentassets/b443bbd36fcf458a883231f34d6f24aa/hitron-cgn3res-user-guide.pdf

 

 

 



I've Been Around
Posts: 1

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

CGN3ACSMR still broadcasting over 2.4G band while in bridge mode

 

Recently, my wifi bandwith and range on the 2.4G band were basically cut in half. Originally when I had my service installed the wifi signal was full and strong on 2.4G, but something has changed resulting in this reduction in wifi signal. I have done a bunch of trouble shooting myself and even had a Rogers tech out to the house today and still no resolution to the problem.

 

The CGN3ACSMR gateway I have is in bridge mode, but the 2.4GHz light is still illuminated on the front. If it is in fact still broadcasting on the 2.4 G channels, that would explain my reduction in bandwith. What should I do?

Moderator
Moderator
Posts: 1,510

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

 

Hello, @dgreene77

 

Welcome to the Rogers Community Forums! Smiley Happy

 


@dgreene77 wrote:

 

 

The CGN3ACSMR gateway I have is in bridge mode, but the 2.4GHz light is still illuminated on the front. If it is in fact still broadcasting on the 2.4 G channels, that would explain my reduction in bandwith. What should I do?


 

We've discussed this issue in the previous pages of this thread. The workaround is to disable 2.4GHz and 5GHz SSIDs before bridging. Even though you see 2.4GHz led is lit, it's not broadcasting neither 2.4GHz or 5GHz network in bridge mode. 

 


@dgreene77 wrote:

Recently, my wifi bandwith and range on the 2.4G band were basically cut in half. Originally when I had my service installed the wifi signal was full and strong on 2.4G, but something has changed resulting in this reduction in wifi signal.



It could due to some interferences from other 2.4GHz sources, like other routers in your vicinity etc. I'll invite @Datalink to share his expertise for this issue, thank you for your patience.

 

Cheers,

RogersMoin

Resident Expert
Resident Expert
Posts: 6,107

Re: *** CGN3ACSMR - League of Legends – latency: firmware release pending

Hmm, in cases such as this, there is always the question, is this a wifi issue only, or is it a combined wifi and modem issue? So, first a few questions:

 

  1. What data plan are you on, 100/10 or 250/20 Mb/s
  2. Can you run a wired speedtest at http://speedcheck.rogers.com/en.html and speedtest.net using the Toronto Telus server and post both results.
  3. Can you log into the modem, navigate to the STATUS …. DOCSIS WAN page, copy the downstream and upstream tables and paste them into this thread. Between the wired speedtest results and the signal levels in the tables we can tell if the modem data rates themselves are where they should be.

The LED illuminated when the modem is in Bridge mode is a firmware bug. As @RogersMoin indicated, the workaround is to disable both wifi networks prior to kicking the modem into Bridge mode. I don’t think that works in every case. For some reason I’ve never had that issue with my CGN3ACSMR.

 

For the wifi itself, it may be nothing more than one or more neighbors bringing home new routers, which are now competing with your modem for free channels. The 2.4 Ghz band is normally heavily oversubscribed, resulting in slow wifi data rates for all concerned. The way to determine this is to load inSSIDer onto a laptop or wifi equipped pc. The link below is for the last freebie version of inSSIDer, which can be used to monitor both 2.4 and 5 Ghz networks. It doesn’t show the 802.11ac networks in the 5 Ghz band, so it doesn’t show a complete 5 Ghz picture in that respect. There is a newer pay version out now that does and which runs on a normal 802.11 b/g/n laptop. It reads the transmit headers to determine the various networks , b/g/n/ac and display them on the graphical and text display. If you use 5 Ghz networks at all, for $20 US its worth having so that you can assess the network situation in the 5 Ghz band.

 

http://www.techspot.com/downloads/5936-inssider.html

 

So, load this onto your laptop and have a look at the graphical display to see what you’re up against in terms of competing networks. That alone might explain why your wifi data rates have dropped, assuming that the modem itself is providing the data rates that it should. The display is a negative scale, with zero at the top and descending power levels below. Ideally your network would be the highest network on the display and have at least 40 to 45 dBmW separation between your network and any competing network that is running on the same channel or a nearby overlapping channel. Anything less than that and your data rates will suffer. As that separation comes down to zero, your wifi data rate will slow right down. So, ideally you would be able to select an operating channel that has no competition, however, depending on where you live, that might be impossible. If anything, that might give you the impetus to move everything that you can up to the 5 Ghz band. For devices that remain in the 2.4 Ghz band your choice would be to put up with the neighborhood competition, or buy a good third party router and run the modem in Bridge mode. That is what I and a good many others do.

 

The only recommendation I would have if you decide to go the third party route is to buy a router with gigabit WAN and LAN ports and with external antenna. I run an Asus RT-AC68U which has been replaced by the RT-AC68P. This has a slightly faster processor and proper shielding around the USB ports. Fwiw, the RT-AC68U is a common router here on the forum. Its not a cheap router, but its not uber expensive either and Asus seems to be good with updates for it, along with the other routers that it supports.

 

So, have a go with the questions regarding the modem and inSSIDer and post the results. If you need any help interpreting the inSSIDer display, do a screen capture, remove your network name and MAC address and post it somewhere so that we can have a look at it.