Tonight we will be pushing 188.8.131.52 to our CGN3AC community members devices.
This build brings Band Steering enabled through Easy Connect.
The modem will not have Band Steering enabled until a factory reset is performed and the Easy Connect flow completed.
Band Steering will automatically select either the 2.4GHz or 5GHz band to optimize your devices connection and overall experience.
@ffdhfhf what are you pinging in that test? Is that the Cable Modem Termination System (CMTS) which is hop #2 on any trace to any target? If so, you can't use the CMTS for latency testing due to a timing issue in the firmware. You can use the CMTS for packet loss testing and there isn't any issue with that. If you're looking for latency testing, ping the Rogers DNS as listed below:
Rogers IPV4 DNS:
Rogers IPV6 DNS:
Primary IPv6 DNS:
Secondary IPv6 DNS:
If you are looking to run an IPV4 ping test at a higher rate, use HRPing, as shown in the following post:
Substitute your own CMTS IP address for the address shown in that post. If you do that and run very short ping intervals, in the order of 50 milli-seconds, you'll see that the high time returns actually run in groups, then drop back down to normal return times in the 8 to 13 ms range, then back up again, back down again, etc, etc.
To really look for any latency issues, ping the Rogers DNS. When you've determined that there no issue with latency from your modem to the Rogers DNS, then consider checking other DNS addresses outside of the Rogers network. Beyond the ISP border you will see higher return times, but, they shouldn't be that much different on average.
$ sudo traceroute 184.108.40.206 -I
traceroute to 220.127.116.11 (18.104.22.168), 30 hops max, 60 byte packets
1 172.18.2.2 (172.18.2.2) 1.459 ms 1.601 ms 2.717 ms
2 22.214.171.124 (126.96.36.199) 14.166 ms 20.872 ms 20.883 ms
3 8076-dgw02.mtnk.rmgt.net.rogers.com (188.8.131.52) 19.053 ms 19.106 ms 19.188 ms
Where hop #2 is CMTS gateway, hop one is the Rogers cable modem itself.
Has anyone encountered any upload speed issues since the upgrade to CGN3ACSMR 184.108.40.206? Running in bridge mode.
just an update, on the CODA modem.
I noticed my upstream signal levels were a bit low and the modem was occasionally freezing and rebooting. i contacted tech support, they had me swap to a new modem.
the new modem is hardware revision 2.
surprisingly the signal levels are improved. I wasn't expecting that, but I'll take it. it came with firmware 33T3, and it was noticeably slower than my old modem. i asked for the latest test firmware to get pushed, got it, and things are perfect for me right now. it's been rock solid and fast for the last week. maybe this nightmare is finally over.
I'm running in gateway mode btw.
Anyone else lose connectivity today? Is a new firmware being pushed out?
Lost connection twice so far in the last 2 hours. Second time modem fixed itself. First time I had to power off.
Web interface inaccessible.
Same exact thing happened to me but I'm still on 36T6 firmware. Was around 11:30 a.m. (16:30 log time).
Also had no Internet and couldn't access the modem. I had to power off and on again to get it working.
Not really, we're waiting on the next firmware but it's been delayed for a while.
3 weeks ago you said that there was an issue ''We have a reported issue where some devices experience the 5GHz band freezing''
Are we making any progress with that?
Looking forward to that firmware upgrade soon.