cancel
Showing results for 
Search instead for 
Did you mean: 

CODA-4582 - Open Issues for Investigation

RogersDave
Retired Support
Retired Support

*** This post was last edited May 2, 2017 ***

 

Good morning Community,

 

As I mentioned in a post two days ago, we have received the next firmware 2.0.10.20 from Hitron. We are currently running initial testing on this version and will push it out to participants in the firmware trial program as soon as it passes initial testing.

 

However, while running these tests, we discovered abnormal behavior with ICMP and are awaiting feedback from Hitron today to asses how this will be addressed. As soon as I this is confirmed, I’ll update the change log with the correct version information and start pushing it out.

 

In parallel, we are still working on the following high priority items. In some cases below, I requested affected customers to reach out to me via private message. If you do so, please include your modem MAC address in the subject line (even if we exchange messages daily) as there are a lot of you reaching out to me daily 🙂

 

UDP Packet Loss

The investigation for what has been reported as UDP packet loss is still ongoing. We have deployed a probe at one fellow forum member on both a CODA-4582 and a CGNM-3552 to collect additional data. We are actively working with Hitron and Intel on the results observed.

 

Based on what we know so far, in most instances UDP packet loss is coupled with higher uplink usage in the area. Although the impact is noticeable in specific logs (League of Legends), the root cause for the perceivable impact (while playing) is likely related to bufferbloat (see next issue).

 

 

Bufferbloat

When comparing the performance of a CODA-4582 to a CGNM-3552 in the same network conditions, the CODA-4582 consistently reports higher bufferbloat when tested on DSLReports.

 

Update April 12: The solution for this problem will come in two folds. It will require a change in software which will possibly be included in 2.0.10.27 but more likely in 2.0.10.28 and a change in network configuration.

 

The network configuration change is not compatible with the current firmware so this change will only come after a vast majority of the modems are running the new code. We are however looking at a way to make the change only for specific modems to support testing in the community.

 

Update April 22: This problem seems resolved in firmware 2.0.10.27

 

 

5 GHz WiFi Low range for channels 36 to 48

Lower WiFi channels on the modem have a much smaller range. This is due in part to the limit imposed by Industry Canada to maximum transmit power.

 

Furthermore, the current automatic channel selection (auto mode) tends to select the lower channels when in similar load conditions.

 

Workaround: manually select higher channels (149-153-157-161)

 

Update April 22: The channel selection algorithm has been improved in firmware 2.0.10.27

 

 

Loss of OFDM Channel Lock

Under some RF conditions, the modem fails to lock properly on the OFDM channel. This typically result in variable performance.

 

Update April 12: This problem is resolved in 2.0.10.26T2

 

 

List of connected device does not get fully populated

This is a known issue that has been tracked since firmware 2.0.10.13. We are making improvements at every firmware but it is not a perfect system.

 

The situation is worst after a reboot or firmware upgrade as the list gets reset and must be repopulated as devices renew their DHCP lease.

 

 

NAT Loopback not working for wired clients

When setting up port forwarding to an internal server, it is possible for a client on WiFi to reach the server using the external IP/port. If the client is on a wired interface, it doesn't work.

 

Update April 12: This problem is resolved in 2.0.10.26T2 (not confirmed)

 

 

LAN Counters not working

Some customers reported that LAN counters (especially in bridge mode) are reporting inaccurate values.

 

This problem has been reported to Hitron for investigation.

 

 

Unexpected modem reboot

Some customers reported their modem reboots unexpectedly. We have also seen this behavior in our lab.

 

Update April 12: This problem is resolved in 2.0.10.26T2

 

 

Missing SC-QAM Channels

After a reboot, some modems are missing SC-QAM channels. A fix has been implemented in 2.0.10.26T2 to address this behavior but it has not corrected all scenarios.

 

Investigation continues with Hitron.

 

 

WiFi Survey

The WiFi Survey functionality in firmware 2.0.10.26T2 (and possibly before) reports incorrect SSID names.

 

 

Guest Network

When connecting to the Guest Network, an error message is displayed "only allow DHCP client to use this wireless".  This has been reported in firmware 2.0.10.26T2.

 

Update April 22: This issue has been resolved in firmware 2.0.10.27

Update May 2: It seems this issue is not fully resolved and still experienced by some users


 

Future Planned Improvements

The following are items that we are working on in parallel of the above.

  • Improvement in WiFi speeds
  • Improvement in latency / bufferbloat

 

 

Dave

 

*Edited Labels*

2,620 REPLIES 2,620

Re: CODA-4582 - Open Issues for Investigation

I know for a fact the new coda modem has a open Nat with the Xbox one but if you have more then one console it's not the greatest

Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a Senior Contributor

That's great.

Re: CODA-4582 - Open Issues for Investigation

I couldn't get an open NAT and I couldn't get a Download speed higher than 5mps wired.

Any suggestions on settings I should be trying? Coda or Xbox related?

Re: CODA-4582 - Open Issues for Investigation

I didn't have to do any settings at all to coda or Xbox , try clearing your Xbox network settings

Re: CODA-4582 - Open Issues for Investigation

Thanks. I will try that tonight.

What are you getting as a download speed and what package do you have from Rogers? I tried auto settings before and it wasn't working for me.

Re: CODA-4582 - Open Issues for Investigation

I just leave it on auto settings, I'm on ignite 250 I get speeds from 60- 100 mb upload always 20mb.
Firmware .20 (January 10, 2017) *
Improved flow control algorithm (handle wired devices at different speeds)
Improve XBOX NAT
WinMTR packet loss fix
Improve Switch Link Speed autodetection
Improvement to connected device list (not final fix)

Re: CODA-4582 - Open Issues for Investigation

yyzsam
I Plan to Stick Around

Just noticed two downstream channels missing. Did a soft reboot and then 4 were missing. Did a powercycle and they all came back. Fun....

Re: CODA-4582 - Open Issues for Investigation

I just did a reboot with no port forwarding and auto settings for the Xbox. My NAT is open but I only got 20 MBS download and 20 up.

Again when I plug in a laptop I do get 311 Down and 21 up.

Not sure why people think that below 100 MBS down on the Xbox test is acceptable. A month ago I was getting 180 down. Any suggestions on next steps? Contact Tec support again? Should I buy my own cable modem? Is it some issue with settings?

Re: CODA-4582 - Open Issues for Investigation

Really you can't do anything you can message @RogersDave about the issue is working on a fix with this and udp issues

Re: CODA-4582 - Open Issues for Investigation

crazyshot
I Plan to Stick Around

Hello guys,

 

I ran a traceroute to the NA League servers and was wondering if anyone knows what's going on? I really can't tell, Rogers says there's no problem but Riot says there's packet loss on the 2nd and 5th node. I'll copy and paste it here, hopefully it's not too hard to read. 

 

------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| hitronhub.home - 0 | 200 | 200 | 0 | 1 | 14 | 0 |
| 99.253.156.1 - 50 | 68 | 34 | 9 | 20 | 49 | 15 |
| 66.185.90.37 - 0 | 200 | 200 | 7 | 16 | 43 | 19 |
| 64.71.241.97 - 0 | 200 | 200 | 8 | 18 | 47 | 26 |
| 24.156.144.122 - 0 | 200 | 200 | 14 | 22 | 48 | 28 |
| 209.148.230.134 - 49 | 70 | 36 | 50 | 60 | 100 | 62 |
| eqix-ch2.chi01.riotdirect.net - 49 | 70 | 36 | 48 | 57 | 82 | 64 |
| 104.160.131.44 - 35 | 86 | 56 | 35 | 49 | 87 | 57 |
| 104.160.131.101 - 34 | 86 | 57 | 36 | 46 | 81 | 41 |
| No response from host - 100 | 41 | 0 | 0 | 0 | 0 | 0

 

 

Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| hitronhub.home - 0 | 277 | 277 | 0 | 0 | 5 | 0 |
| 99.253.156.1 - 50 | 94 | 47 | 10 | 16 | 41 | 12 |
| 66.185.90.37 - 0 | 277 | 277 | 9 | 16 | 43 | 21 |
| 64.71.241.97 - 0 | 277 | 277 | 9 | 18 | 64 | 29 |
| 209.148.230.230 - 0 | 277 | 277 | 13 | 21 | 48 | 25 |
| 209.148.230.138 - 49 | 95 | 49 | 36 | 40 | 60 | 47 |
| 104.160.131.1 - 0 | 277 | 277 | 20 | 28 | 47 | 28 |
|________________________________________________|______|______|______|______|______|______|

Re: CODA-4582 - Open Issues for Investigation

Yea I was getting packet loss last night but on the Xbox one I ran few test 1st on the Xbox one which it showed 2% packet loss then when I was playing NHL it was also showing 2% packet loss and upload was very low last night when running test on speed test @RogersDave on .23firm

Re: CODA-4582 - Open Issues for Investigation

crazyshot
I Plan to Stick Around

Yeah this sucks. Will a future firmware update fix this or will I have to swap my modem?

Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a Senior Contributor

@crazyshot 

 

More than likely but only @RogersDave will be able to confirm.

Re: CODA-4582 - Open Issues for Investigation

Anyone know when rogersdave is coming back wasn't he suppose to be back this week

Re: CODA-4582 - Open Issues for Investigation

@crazyshot, yes you have packet loss between the modem and the CMTS.  What I would suggest is to download Pingplotter and use it to look for packetloss occurance so that you can cue tech support to have a look at the modem to CMTS path when the packetloss is at its worst.  You don't have to buy the program unless you decide to.  After 14 days it will kick down to a limited freebie mode which is still usefull to look for packetloss.  Have a look at the following post on how to set that up:

 

http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/355...

 

You are also showing packet loss at the following Rogers servers, which are the last Rogers servers before jumping off to the Riot Games servers:

 

209.148.230.134

209.148.230.138

 

Keep an eye on those servers to see if the packet loss continues throughout the day, as in its a persistent loss.  If so, call tech support and ask to speak with a Level II tech regarding the server.   The Level I tech won't be able to help as this is a network issue.  The Level II tech probably won't be able to resolve it but, he or she should be able to report the problem to the NOC or the Network Engineering staff.  If you have no success with reporting this, please let us know.

 

Fwiw, I'm running a WinMTR to 104.160.131.101 at the moment and do not see any packet loss all the way to 104.160.131.101

 

 

 

 



Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a Senior Contributor

@lethalsniper

 

That's what we were told but I guess he's too busy to return yet, everyone is waiting for his return since he's the only one that can help us.

 

He's also the only one to give us fix,hopes and dreams about having a good connection!

 

Long Life @RogersDave please come back 😞

Re: CODA-4582 - Open Issues for Investigation

crazyshot
I Plan to Stick Around

Okay so i started it up and the whole thing on the bottom of the program is red? That can't be good right

Re: CODA-4582 - Open Issues for Investigation

That is correct.  Just to make sure that you have the correct address, try this:  

 

1.  Enter www.google.ca as a target in the address bar and hit the go button.  You should see the bottom panel display the www.google.ca address results.

2.  Right click on the second IP address, which will be the IP address following the modem.  In this case its the CMTS.  Select the second option to copy the IP address.

3.  Pause pingplotter and paste that address into the address bar.  Change the interval time to 1 second.  Hit the restart selection at the right side of the address bar.  

 

When pingplotter is running with that CMTS address in the address bar, you're monitoring the modem to CMTS path, looking for packet loss and high ping times.  If you see persistent packet losses, thats the time to call tech support to have the CSR run a signal check on the modem and then ping the modem from the CMTS or ping the CMTS from the modem.  If you can see packet loss via pingplotter, then the CSR should be able to see the same.  That  will probably lead to a tech visit. 

 

Pingplotter automatically puts the target address display on the bottom panel.  If you click or double click on any of the intermediate addresses on the way to the target it will open up another panel to show the ping results from that intermediate address.  To hide a display, right click on the display and select "Hide".  In this particular case, and at this particular time, we're only interested in the modem to CMTS path, so, anything beyond the CMTS won't help in determining what the problem might be.  

 

Hope this helps.  Please let me know if you have further difficulties running Pingplotter. 



Re: CODA-4582 - Open Issues for Investigation

crazyshot
I Plan to Stick Around

Okay so the 2nd hop seems okay I think, the first hop has packet loss though, does that mean anything? Should I PM you a picture?

 

edit: also i contacted rogers, they said they are not able to replicate this issue which is quite unfortunate

Re: CODA-4582 - Open Issues for Investigation

Crazyshots I would like to ping lan league server on pingplotter what's the address

Re: CODA-4582 - Open Issues for Investigation

crazyshot
I Plan to Stick Around

they have two, you can pick either one

 

192.64.170.252

104.160.131.1

 

thanks btw!