Rogers → [Modem/Router] Rogers CODA-4582 modem now available Puma 7 Chipset

Should be available to all 250u and gigabit customers. IPV6 is not enabled yet and wont be until January or so Dave says.

»communityforums.rogers.c ··· 1#M37931

Is it confirmed this is running as DOCSIS 3.1 or is this just a CPE upgrade that supports 3.1 when the CMTS does?

I'm picking mine up in a few hours so I guess I'll know for sure.

As far as was stated, its 3.1 certified, no mention that it will be running at it but it was also mentioned there will be beta firmware for us to test after the holidays, and that there will be more features added such as IPV6 in January. But let us know, especially how the ping plot/latency is.

Dang, white? thats going to clash with everything i own. Oh well though, i need this. how is the latency/ping/jitter and of course speed?

In Gateway mode, GRC's DNS Benchmark results for Reliability % is greatly improved, so that means that the UDP performance has improved, which will please the gamers in the crowd. UDP packet loss is down, but its not totally perfect, which is what I was expecting to see, but there is a definite improvement. I still have to compare the lookup times to see if there was any improvement there.

Running the same test in Bridge mode thru an RT-AC68U, all of the cached results are 100% Reliable, so, no packet loss, which is a definite improvement. Only one uncached result had a low score, at 97.9 %, so thats not too bad.

Speed test this morning 950Mb/s down / 40 Mb/s up. First time I had ever seen 950, so the download capability has improved as well.

Looks like Hitron's designers said "make it look like an AirPort Extreme".

Same as what i was seeing with 3552.

DOCSIS WAN Page:

IPV6 works as well.

C:\Windows\System32>ping -6 dslreports.com
 
Pinging dslreports.com [2607:fad0:3706:1::1000] with 32 bytes of data:
Reply from 2607:fad0:3706:1::1000: time=28ms
Reply from 2607:fad0:3706:1::1000: time=34ms
Reply from 2607:fad0:3706:1::1000: time=30ms
Reply from 2607:fad0:3706:1::1000: time=30ms
 
Ping statistics for 2607:fad0:3706:1::1000:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 28ms, Maximum = 34ms, Average = 30ms
 

Is the OFDM Downstream enabled? if so you're DOCSIS 3.1 enabled. which may or may not be in the area you are in.

Edit: derp replied with out refreshing. Saw above post.

OFDM Downstream is enabled in High Park. I'm up on D3.1.
OFDM upstream is not.

Also FYI ping is rock solid.


64 bytes from 8.8.8.8: icmp_seq=0 ttl=58 time=9.592 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=58 time=9.840 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=58 time=10.504 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=58 time=11.826 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=58 time=11.066 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=58 time=10.446 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=58 time=10.562 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=58 time=9.787 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=58 time=12.021 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=58 time=10.021 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=58 time=11.975 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=58 time=10.115 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=58 time=11.825 ms


Only few Nodes in KW are D3.1 ready, mine is not yet, which is coming soon though.

yep, same here

how about traceroute? are u getting any packet loss like in my output?

This makes me so happy, I'm going to check again after work see if the UPS guy dropped off the new modems at my local store.

Thanks, so, its something 'with the modem then'

*Daveeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee*

LoL (poor guy)

Guys the packet loss might just be Rogers in general today, I've had a ping plot going all morning and even i have loss and i have not replaced my modem yet.

Thanks for that. In that case, I might not complain about it until tomorrow. That started today?

To put the WinMTR stats in a post, and have them line up, use the following:

"[code]
"

"
[/code]"

Without the parenthesis in front or behind the square brackets.

Same on IPV4:

 1. 172.16.254.1                                                                                                       0.0%    19    0.3   0.4   0.3   0.5   0.0
 2. 99.233.208.1                                                                                                      47.4%    19   11.4  11.3   9.8  13.0   0.9
 3. 67.231.222.221                                                                                                     0.0%    19    9.9  13.2   9.9  22.5   3.5
 4. 69.63.248.185                                                                                                      0.0%    19   13.3  12.8  10.0  19.1   1.9
 5. 209.148.230.14                                                                                                    44.4%    19    9.9  11.1   8.4  15.0   1.6
 6. ???
 7. 209.85.242.109                                                                                                    47.4%    19   11.5  14.9   9.7  43.7  10.3
 8. 72.14.235.34                                                                                                      33.3%    19   22.7  27.1  21.9  46.9   7.1
    216.239.46.160
 9. 209.85.143.60                                                                                                     21.1%    19   22.8  23.5  21.2  30.5   2.3
    209.85.241.46
    72.14.233.69
    72.14.237.131
10. 108.170.243.161                                                                                                   33.3%    19   24.9  23.3  21.7  25.3   1.0
    108.170.243.193
11. 216.239.42.33                                                                                                     36.8%    19   23.8  24.1  21.0  34.3   3.5
    216.239.42.35
12. ord38s04-in-f3.1e100.net                                                                                           0.0%    18   23.2  23.4  21.2  31.0   2.0
 

No issues on IPV6:

 1. 2607:fea8:13df:fec3:8a1f:a1ff:fe29:e8ca                                   0.0%    27    1.4   0.9   0.3   1.9   0.0
 2. 2607:f798:804:ef::1                                                       0.0%    27   10.2  12.2   8.2  35.3   5.2
 3. 2607:f798:10:1c63::672:3122:2213                                          0.0%    27   10.4  12.8   8.5  24.1   4.0
 4. ???
 5. 2607:f798:10:295::2                                                       0.0%    26    8.3  14.7   7.3  49.5   8.6
 6. 2001:4860:1:1::32c:0:8                                                    0.0%    26   11.0  12.5   9.6  20.1   3.0
 7. 2001:4860::1:0:713a                                                       0.0%    26   32.8  16.2   8.9  37.2   9.1
 8. 2001:4860:0:1::4ab                                                        0.0%    26   12.1  12.1   8.3  22.2   2.9
 9. yyz08s10-in-x03.1e100.net                                                 0.0%    26   11.5  11.5   9.3  16.7   1.7
 

I just started win mtr, if i get anything meaningful ill post it so far no packet loss at this moment i had it this morning though. I wonder if they have changed anything on their back end with the new modem launch that would cause us to see this in different areas, clearly we are all on different nodes.

Ok to summarize from High Park.

32 channels of DOCSIS 3.0 bound and one channel of DOCSIS 3.1. I'm assuming the D3.1 channel = 3.0 is unused, but bound for fallback purposes.

Standard 3 channels of DOCSIS upstream, no DOCSIS 3.1 upstream right now.

IPV6 works despite what RogersDave had said. Not sure if this is area specific.

Average ping time and jitter is MUCH improved over the 3552. Lowest ping I saw on one test was 5ms. VDSL2 didn't even hit that low in my area.

IPV4 ping (100 pings to 8.8.8.8):
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 10.314/13.655/22.542/2.656 ms

IPV6 ping (100 pings to google.ca):
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 7.368/11.237/55.548/5.171 ms

So there it is. DOCSIS 3.1 is sorta here. It's not quite the fibre connection at the office in terms of performance but it's a LOT better than 3.0 so far, and that's without D3.1 upstream enabled.

Also for LED watchers, on the new Hitron units:

GREEN: DOCSIS connected.
BLUE: DOCSIS 3.0 multiple channels connected.
LIGHT PURPLE: DOCSIS 3.1 connected.

So if you're not in a 3.1 area yet and you see a restart followed by some purple LED"s on your DS/US, you're 3.1 enabled.

Any questions about anything specific?

Thanks for all the info and screens guys. I hope that my local store had theirs delivered today, i called this AM they didnt have them yet. your results and tests look promising though, its a HUGE improvement it seems over the CGN3XXXX series.

Panda, aren't your upstream levels out of range?

I've checked into that a few times.

Upstream signal strength = how much power your modem needs to hit the CMTS cleanly. Apparently the lower this goes the better and it's never been an issue. The "spec" says 40-52 and higher than 52 expect problems so I've always taken that as "lower is unlikely but fine".

I keep an eye on it but it's never given me any sync/disconnect/reliability issues and until gigabit never had any performance issues (even on gigabit my performance issues are that I'm not getting a full gigabit but still getting 400-500Mbps easily).

You want solid? this is from Bell Fiber 250/250 just installed at my office. hehe... Goodbye problems related to crappy modems and RF issues...

Reply from 8.8.8.8: bytes=32 time=1ms TTL=56
Reply from 8.8.8.8: bytes=32 time=1ms TTL=56
Reply from 8.8.8.8: bytes=32 time=1ms TTL=56
Reply from 8.8.8.8: bytes=32 time=1ms TTL=56
Reply from 8.8.8.8: bytes=32 time=1ms TTL=56
Reply from 8.8.8.8: bytes=32 time=1ms TTL=56
Reply from 8.8.8.8: bytes=32 time=1ms TTL=56