FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

[RogersMargaret]

Hello Community,

We are currently offering our users an exclusive opportunity to participate in an upcoming trial of the new firmware for our Rocket Wi-Fi Modem (CGN3ACR, CGN3AMR and CGN3ACSMR) and Rocket Gigabit Wi-Fi Modem (CGN3552 and CODA-4582). For details of this program, please see this thread.

This thread will be used for feedback regarding the firmware.  We've invited @RogersSergio, @RogersSyd & @RogersBob from our Networking team to participate in this thread.  Your feedback is very valuable and will be used to enhance the firmware before it is released publicly.

Thank you for your continued feedback and support.

[ffdhfhf]

This still happens, TX/RX, SNR is all good, the fact it seems to happen to the CMTS gateway interface im connected to seems to be it's not my signal or cabling here...

Since this modem runs Linux I'd be saddened for any issues with the kernel version.

That said, I doubt its any signal issues.

Software/firmware build: 2.0.10.36T6

$ ping 99.228.0.1  
PING 99.228.0.1 (99.228.0.1) 56(84) bytes of data.
64 bytes from 99.228.0.1: icmp_seq=1 ttl=63 time=14.3 ms
64 bytes from 99.228.0.1: icmp_seq=2 ttl=63 time=9.22 ms
64 bytes from 99.228.0.1: icmp_seq=3 ttl=63 time=7.73 ms
64 bytes from 99.228.0.1: icmp_seq=4 ttl=63 time=16.3 ms
64 bytes from 99.228.0.1: icmp_seq=5 ttl=63 time=9.95 ms
64 bytes from 99.228.0.1: icmp_seq=6 ttl=63 time=8.90 ms
64 bytes from 99.228.0.1: icmp_seq=7 ttl=63 time=9.94 ms
64 bytes from 99.228.0.1: icmp_seq=8 ttl=63 time=9.10 ms
64 bytes from 99.228.0.1: icmp_seq=9 ttl=63 time=8.24 ms
64 bytes from 99.228.0.1: icmp_seq=10 ttl=63 time=9.64 ms
64 bytes from 99.228.0.1: icmp_seq=11 ttl=63 time=9.65 ms
64 bytes from 99.228.0.1: icmp_seq=12 ttl=63 time=9.89 ms
64 bytes from 99.228.0.1: icmp_seq=13 ttl=63 time=74.4 ms
64 bytes from 99.228.0.1: icmp_seq=14 ttl=63 time=17.4 ms
64 bytes from 99.228.0.1: icmp_seq=15 ttl=63 time=7.91 ms
64 bytes from 99.228.0.1: icmp_seq=16 ttl=63 time=9.69 ms
64 bytes from 99.228.0.1: icmp_seq=17 ttl=63 time=11.1 ms
64 bytes from 99.228.0.1: icmp_seq=18 ttl=63 time=10.6 ms
64 bytes from 99.228.0.1: icmp_seq=19 ttl=63 time=8.84 ms
64 bytes from 99.228.0.1: icmp_seq=20 ttl=63 time=9.30 ms
64 bytes from 99.228.0.1: icmp_seq=21 ttl=63 time=8.84 ms
64 bytes from 99.228.0.1: icmp_seq=22 ttl=63 time=31.8 ms
64 bytes from 99.228.0.1: icmp_seq=23 ttl=63 time=16.10 ms
64 bytes from 99.228.0.1: icmp_seq=24 ttl=63 time=9.81 ms
64 bytes from 99.228.0.1: icmp_seq=25 ttl=63 time=9.86 ms
64 bytes from 99.228.0.1: icmp_seq=26 ttl=63 time=8.84 ms
64 bytes from 99.228.0.1: icmp_seq=27 ttl=63 time=8.97 ms
64 bytes from 99.228.0.1: icmp_seq=28 ttl=63 time=8.79 ms
64 bytes from 99.228.0.1: icmp_seq=29 ttl=63 time=10.7 ms
64 bytes from 99.228.0.1: icmp_seq=30 ttl=63 time=10.4 ms
64 bytes from 99.228.0.1: icmp_seq=31 ttl=63 time=7.01 ms
64 bytes from 99.228.0.1: icmp_seq=32 ttl=63 time=8.85 ms
64 bytes from 99.228.0.1: icmp_seq=33 ttl=63 time=7.79 ms
64 bytes from 99.228.0.1: icmp_seq=34 ttl=63 time=10.8 ms
64 bytes from 99.228.0.1: icmp_seq=35 ttl=63 time=8.81 ms
64 bytes from 99.228.0.1: icmp_seq=36 ttl=63 time=8.88 ms
64 bytes from 99.228.0.1: icmp_seq=37 ttl=63 time=10.7 ms
64 bytes from 99.228.0.1: icmp_seq=38 ttl=63 time=18.10 ms
64 bytes from 99.228.0.1: icmp_seq=39 ttl=63 time=41.10 ms
64 bytes from 99.228.0.1: icmp_seq=40 ttl=63 time=7.87 ms
64 bytes from 99.228.0.1: icmp_seq=41 ttl=63 time=10.9 ms
64 bytes from 99.228.0.1: icmp_seq=42 ttl=63 time=9.93 ms
64 bytes from 99.228.0.1: icmp_seq=43 ttl=63 time=13.0 ms
64 bytes from 99.228.0.1: icmp_seq=44 ttl=63 time=11.7 ms
64 bytes from 99.228.0.1: icmp_seq=45 ttl=63 time=11.7 ms
64 bytes from 99.228.0.1: icmp_seq=46 ttl=63 time=9.56 ms
64 bytes from 99.228.0.1: icmp_seq=47 ttl=63 time=8.00 ms
64 bytes from 99.228.0.1: icmp_seq=48 ttl=63 time=29.8 ms
64 bytes from 99.228.0.1: icmp_seq=49 ttl=63 time=16.6 ms
64 bytes from 99.228.0.1: icmp_seq=50 ttl=63 time=11.5 ms
^C
--- 99.228.0.1 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 114ms
rtt min/avg/max/mdev = 7.005/13.226/74.403/10.836 ms

The times are great, nothing unusual here

[RogersIan]

We are still testing the CODA firmware. We have a reported issue where some devices experiece the 5GHz band freezing. Any type of roll out is on hold until we find out what is causing this.

@DatalinkUnfortunately extending the frequency range is not solely a firmware upgrade and would require additional changes to support

In regards to modems showing 4 upstream channels. The number of channels seen on devices is driven by what our network is able to support in that area. Since every area is different it's sometimes difficult to provide the same support in all areas all at once but as support is available we make sure to enable it as quickly as possible so our customers benefit from the improvements.

RogersIan

[RogersIan]

Tonight we will be pushing 4.5.8.40 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.

RogersIan

[Datalink]

@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:

64.71.255.204

64.71.255.198

Rogers IPV6 DNS:

Primary IPv6 DNS:

2607:f798:18:10:0:640:7125:5204

Secondary IPv6 DNS:

2607:f798:18:10:0:640:7125:5198

If you are looking to run an IPV4 ping test at a higher rate, use HRPing, as shown in the following post:

https://communityforums.rogers.com/t5/Internet/Lag-with-Wireless-Turned-On/m-p/441641#M56292

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. 

.  

[ffdhfhf]

Im using

$ sudo traceroute 8.8.8.8 -I
traceroute to 8.8.8.8 (8.8.8.8), 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  99.228.0.1 (99.228.0.1)  14.166 ms  20.872 ms  20.883 ms
3  8076-dgw02.mtnk.rmgt.net.rogers.com (66.185.91.165)  19.053 ms  19.106 ms  19.188 ms

Where hop #2 is CMTS gateway, hop one is the Rogers cable modem itself.

[noziel]

Has anyone encountered any upload speed issues since the upgrade to CGN3ACSMR 4.5.8.40? Running in bridge mode.

[xenoguy]

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.

[hoek]

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.

[ablatt]

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.

[soundwave80]

Any progress being made here in terms of latency?

[JohnBeaudin]

Not really, we're waiting on the next firmware but it's been delayed for a while.

[JohnBeaudin]

@RogersIan 

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.

[morrik5]

Is it possible to have this 4.5.8.40 pushed through to my modem CGN3-ACSMR that I had recently been upgraded to. I currently have 4.5.8.39T6. Also my IPv6 is no longer enabled and it was when I had the regular CGN3.

[RogersIan]

@JohnBeaudin - The 5GHz issue which was found meant that version of code was shelved. The cause was identified and will be patched in the next version, which we are expecting to have towards the end of the month. Once it's delivered we will put it through its paces and then hopefully be able to share it here to get your feedback. 

RogersIan

[JohnBeaudin]

Thanks Ian, will you enable D3.1 on the upstream with that update later on?

[morrik5]

All is fixed, turned out to be my Linksys router not picking up IPv6 anymore. Connected directly to modem.

[morrik5]

Found out I forgot to put new modem in bridge mode to have Linksys detecting the IPv6 so all is good with Linksys router.

[xenoguy]

any word on new firmware for the CODA coming soon?

I've had some more instability lately.  i moved the modem closer to the demarc, which gets stronger signals.  this seems to solve some docsis/cable network instability.

unfortunately the wifi is a bit weaker/slower, because 5ghz isn't great at going through walls/floors.  the demarc is downstairs in a closed room.

there's also an issue where the modem itself just freezes.  I checked and it has a very very old version of dnsmasq, with bugs, security vulnerabilities and memory leaks.  to combat this, I'm turning off the DNS proxy feature and just using the rogers dns servers.

to check dns server version information use this command line in windows.  not every server will return info, but the CODA does.

nslookup -type=TXT -class=CHAOS -debug version.bind

[JohnBeaudin]

Hello Community,

Last firmware update on the CODA was on  2.0.10.36T6 (October 23, 2018) 

I hope we will have some good news soon about the new firmware and possibly what direction Rogers is going with the internet service, (Staying with coax for a while or going full fibre?)

[JohnBeaudin]

@RogersIan 

I don't want to sound like a broken record, but I was wondering if you have any news or ETA to share with the community?

[RogersIan]

@JohnBeaudin 

Apologies for the silence, I wish I had more to share.

CGN3AC - We are carefully moving forward with .40. 

CODA - Still testing the new code which brings items discussed earlier in the year.

RogersIan