CGN3ACR (firmware .27) , I just did a Factory reset.
Getting better results on IPv6 as expected.
also some tracerts results
tracert google.ca IPV6
1 1 ms 1 ms 1 ms ************
2 17 ms 12 ms 16 ms 2607:f798:80c:c1::1
3 27 ms 32 ms 31 ms 2607:f798:10:8009:0:690:6325:5117
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 53 ms 50 ms 49 ms 2607:f798:10:293::2
8 66 ms 49 ms 59 ms 2001:4860:1:1:0:32c:0:8
9 46 ms 49 ms 55 ms 2001:4860::1:0:7139
10 57 ms 79 ms 59 ms 2001:4860::8:0:9154
11 56 ms 59 ms 59 ms 2001:4860::1:0:cb45
12 61 ms 62 ms 61 ms 2001:4860:0:100f::1
13 69 ms 154 ms 62 ms 2001:4860:0:1::15a1
14 75 ms 59 ms 59 ms ord36s02-in-x03.1e100.net [2607:f8b0:4009:80d::2003]
Tracert google.ca IPV4
1 1 ms * * ************
2 14 ms 19 ms 10 ms INTEL_CE_LINUX [220.127.116.11]
3 25 ms 28 ms 19 ms INTEL_CE_LINUX [18.104.22.168]
4 26 ms 23 ms 17 ms INTEL_CE_LINUX [22.214.171.124]
5 34 ms 31 ms 37 ms van58-9-229-245.dynamic.rogerstelecom.net [126.96.36.199]
6 41 ms 40 ms 44 ms van58-9-229-229.dynamic.rogerstelecom.net [188.8.131.52]
7 50 ms 50 ms 42 ms INTEL_CE_LINUX [184.108.40.206]
8 182 ms 45 ms 37 ms INTEL_CE_LINUX [220.127.116.11]
9 52 ms 48 ms 43 ms INTEL_CE_LINUX [18.104.22.168]
10 56 ms 51 ms 51 ms INTEL_CE_LINUX [22.214.171.124]
11 52 ms 58 ms 53 ms INTEL_CE_LINUX [126.96.36.199]
12 56 ms 52 ms 46 ms INTEL_CE_LINUX [188.8.131.52]
13 64 ms 56 ms 50 ms INTEL_CE_LINUX [184.108.40.206]
14 50 ms * 48 ms ord36s02-in-f3.1e100.net [220.127.116.11]
I still continue to have T3 timeouts. And its causing some connectivity issues. Agents say that everything looks good signal wise from their end. Last thing I did was swap my modem and this has not helped. They have given me the 3552. I've had major line work done and everything has been reran. I suspect neighbourhood issues but not sure how to get that checked. I don't know what to do from here
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||BandWidth|
|1||23700000||ATDMA - 64QAM||43.500||2||6400000|
|2||38595851||ATDMA - 64QAM||47.750||3||3200000|
|3||30596000||ATDMA - 64QAM||43.000||1||6400000|
Will this Beta firmware work on a "CGN3" modem/router? I'm having T3 timeouts too.
T3 Timeout ( Ranging Request Retries Exhausted )
Explanation: The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem’s power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process.
@Mythen, what Software Version (Firmware) is listed on the STATUS page when you log into the modem.
As far as the T3s occurring I see two or three of those in my logs on a daily basis. Personally I don't pay any attention to them and I don't see any effects on the all day ping tests that I am running these days.
If you are seeing disconnects that's a different issue. With a new CGNM-3552, you should ask for 18.104.22.168. With 22.214.171.124 loaded, which is possible as its a new modem, you will see dead LAN ports occurring. Version .21 resolves that, .22 resolves the Chromecast connectivity issue.
@jszentir - thanks for that concise explanation! I would hazard a guess that low SNR on the cable network is not the culprit in my case, since we have fibre to the home and the only other device is an SD cable TV box. Upstream power levels are currently 36-38 dBmV.
@Datalink - thanks for the tip! Since I'm not on Gigabit I decided to acutally go the other way, to the DPC3825 that I just picked up a few hours ago. In an unscentific test, pings and top speeds are roughly the same. I can also access the modem in gateway mode.
Thanks, is there a reason why the upload speeds are no longer consistent? Did not encounter this issue with .22. Is this being investigated?
In addition, if performing a factory reset, prior to .21 I was able to login directly to the gui without havin to go through the easy connect wizard page. Is this still in place setting a wifi password that is also your admin login?
Good morning Community,
I have now completed to deployment of firmware 126.96.36.199 to all trial participants running a CGN3ACSMR, CGN3ACR or CGN3AMR modem.
If you are a registered participant but have not received this firmware, it is likely because I couldn’t reach your modem for one reason of another. I suggest to remove the power from the modem for a few seconds and put it back. I will re-attempt to upgrade the missed modems later this week.