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

@ishine80 do you have anything that is connected via ethernet to one of the ethernet ports at the back of the modem?  Does your laptop have an ethernet port that you can use for test purposes?  I suspect that you lose all connectivity from the modem, ethernet and wifi, but it would be good to ensure that the ethernet connection would also be affected.  All depends on whether or not you can connect to the modem via ethernet.



Re: CODA-4582 - Open Issues for Investigation

ishine80
I Plan to Stick Around

@Datalink

nothing is currently connected by ethernet.  I will set up one other laptop we currently do not use regularly and hardwire it to the CODA to see if that as well drops the connection.  I won't be able to get back to you with results until much later this evening after my work day. 

Re: CODA-4582 - Open Issues for Investigation

No problem 🙂



Re: CODA-4582 - Open Issues for Investigation

Hello Community!

 

I'm sorry it has been a little while since my last visit (5 full pages in this thread) but as I said previously, from time to time my boss still wants me to do my real job which I have to do if I want to be able to keep said job and support all of you on the side 🙂

 

That being said, I read all the messages in this tread (will follow up with the other regular threads where I'm active and private messages in the next couple of hours) and picked up a few items for Hitron.

 

Version 2.0.10.29 and 2.0.10.30T1 were initial test code of a brand new development branch. These firmwares were not as stable as I would have wanted but there was a lot more work done on it in the last 2 weeks. We have 2 new firmwares coming soon with a lot of fixes while will hopefully bring on par with the general stability of 2.0.10.27 along with the new features.

 

We have also broken down that was original planned in 2.0.10.30T1 in 2 different builds coming between now and the end of July. The first one will include some of the DFS and band steering changes while the second will focus on WiFi speed improvement.

 

Given the comments in here, I will definitely re-run all my latency tests on these new versions and compare with 2.0.10.27.


@Max24, noted you have a speed issue and will look into it.

 

@RyzenFX, OFDM loss (I think it's a localized problem). Did you make any progress with this issue?

 

@ishine80, I understand that you have intermittent connectivity issue. Will wait for the hardwired test to troubleshoot further.

 

Dave

Re: CODA-4582 - Open Issues for Investigation

RyzenFX
I'm a Reliable Contributor

@RogersDave Welcome back! 😄

 

I have made some progress with this issue and I was able to switch modems. Unfortunately this hasn't resolved the issue for me as my modem is still not reporting a lock to an OFDM carrier. I contacted tier 2 customer support and they said that my modem is connected to an OFDM carrier, which is odd considering that my modem interface is still not showing a lock. I'll call again and see if it's a localized issue. 

 

Also, I will compare my League of Legends game logs on .27 to those of .30T1 to see if there is a latency problem in .30T1.

Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a Senior Contributor

@RogersDave

 

Thanks for the update Dave!

 

By any chance do you have any info on DOCSIS 3.1 upstream deployment?

Re: CODA-4582 - Open Issues for Investigation

Max24
I Plan to Stick Around

@RogersDave, Just an update since my last posting I had spoken with a supervisor last week July 5th and again on July 7th and was advised that the issue was being investigated on the node and a area ticket had been created should be listed on my account I can provide you the number if need be. The ticket is still being worked on AFAIK however I noticed speeds were restored earlier this week Wednesday, July 12th, not sure what the problem was or is. But my guess is some speed restriction was in effect as sometimes when I ran speedtests prior to July 12th my download would sometimes to 800-900 then instantly drop down to around the 550 range and the upload would sometimes start off at 43-36 then drop down to 1-6mbps.

 

Since my speeds were restored I've now been having issues with the port speed dropping from gigabit down to 100M and I have to change the ethernet cable to another port to restore the speed back to gigabit (faster than restarting the modem). Not sure what is causing this as I assumed it was fixed in the earlier firmware versions..

Re: CODA-4582 - Open Issues for Investigation

ishine80
I Plan to Stick Around

@Datalink@RogersDave

 

Finally had some time to get a few things tested.  Hooked up my better of the two laptops through ethernet and found ethernet could not connect when my cell phone dropped the wifi signal.  Note that at the same time my daughter was still able to stream youtube kids on the old iphone that's not linked to any cell network.  

 

Below is the message on the ethernet through my laptop: it stated there was an unknown network and could not connect to network as a general message.  

 

IPv6 address: fd00:6477:7de2:58f2:a869:fccf:baa2:424
IPv6 DNS Servers: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Manufacturer: Realtek
Description: Realtek PCIe FE Family Controller
Driver version: 9.1.406.2015

 

I will run the other tests that @Datalink suggested later in the evening respond on the same thread.  

Re: CODA-4582 - Open Issues for Investigation

sbenninger
I Plan to Stick Around

I am having this same issue with the CODA Running .27 FW in bridge mode. Randomly throughout the day or night there will connection issues with high latency and patcket loss and then finally the modem reboots itself. The connection is excellent otherwise until these events happen. I have not contacted support as of yet. Any suggestions prior to doing so would be great. Does the newer .29 FW correct issues like this?

Here is my Docsis log.

 

N

o. 

Time 

Type 

Priority 

Event 

07/20/2017 05:51:52 

84020200 

warning 

Lost MDD Timeout;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

07/20/2017 06:23:39 

82000200 

critical 

No Ranging Response received - T3 time-out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

07/20/2017 06:23:40 

82000300 

critical 

Ranging Request Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

07/20/2017 06:23:40 

82000600 

critical 

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

07/20/2017 06:28:40 

82000400 

critical 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

07/20/2017 06:29:04 

82000200 

critical 

No Ranging Response received - T3 time-out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

07/20/2017 07:24:18 

82000400 

critical 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

07/20/2017 07:24:18 

85010200 

warning 

TCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

07/20/2017 08:07:48 

82000400 

critical 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

10 

07/20/2017 08:08:18 

82000200 

critical 

No Ranging Response received - T3 time-out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

11 

07/20/2017 08:08:18 

82000300 

critical 

Ranging Request Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

12 

07/20/2017 08:08:18 

82000600 

critical 

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

13 

07/20/2017 08:08:18 

82000400 

critical 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

14 

07/20/2017 08:08:22 

82000200 

critical 

No Ranging Response received - T3 time-out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

15 

07/20/2017 08:08:23 

82000300 

critical 

Ranging Request Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

16 

07/20/2017 08:08:23 

82000600 

critical 

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

17 

07/20/2017 08:08:43 

82000200 

critical 

No Ranging Response received - T3 time-out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

18 

07/20/2017 08:09:01 

90000000 

warning 

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

19 

07/20/2017 08:09:04 

84000700 

warning 

RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

20 

07/20/2017 09:57:52 

82000200 

critical 

No Ranging Response received - T3 time-out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

 

Here is my Docsis WAN signals:

 

OFDM Downstream Overview 

 

 

 

 

 

 

Receiver 

FFT type 

Subcarr 0 Frequency(MHz) 

PLC locked 

NCP locked 

MDC1 locked 

PLC power(dBmv) 

0 

NA 

NA 

NO 

NO 

NO 

NA 

1 

4K 

290600000 

YES 

YES 

YES 

-0.500000 

Downstream Overview 

 

 

 

 

 

Port ID 

Frequency (MHz) 

Modulation 

Signal strength (dBmV) 

Channel ID 

Signal noise ratio (dB) 

1 

639000000 

256QAM 

2.500 

14 

35.084 

2 

849000000 

256QAM 

3.100 

2 

34.484 

3 

855000000 

256QAM 

3.200 

3 

34.926 

4 

861000000 

256QAM 

2.500 

4 

34.346 

5 

579000000 

256QAM 

1.500 

5 

35.084 

6 

585000000 

256QAM 

1.700 

6 

35.084 

8 

597000000 

256QAM 

2.200 

8 

35.595 

9 

603000000 

256QAM 

2.000 

9 

35.595 

10 

609000000 

256QAM 

2.000 

10 

35.084 

11 

615000000 

256QAM 

1.800 

11 

35.084 

12 

621000000 

256QAM 

1.700 

12 

34.926 

13 

633000000 

256QAM 

2.400 

13 

35.084 

14 

303000000 

256QAM 

-1.700 

1 

35.595 

15 

645000000 

256QAM 

2.000 

15 

34.926 

16 

651000000 

256QAM 

2.000 

16 

35.084 

17 

657000000 

256QAM 

2.300 

17 

35.084 

18 

663000000 

256QAM 

2.500 

18 

35.084 

19 

669000000 

256QAM 

3.000 

19 

35.595 

20 

675000000 

256QAM 

2.600 

20 

35.084 

21 

681000000 

256QAM 

2.300 

21 

35.084 

22 

687000000 

256QAM 

2.600 

22 

35.084 

23 

693000000 

256QAM 

2.700 

23 

35.084 

24 

699000000 

256QAM 

3.000 

24 

35.084 

25 

705000000 

256QAM 

3.200 

25 

35.084 

26 

711000000 

256QAM 

3.100 

26 

35.595 

27 

717000000 

256QAM 

3.000 

27 

35.084 

28 

723000000 

256QAM 

3.100 

28 

35.084 

29 

825000000 

256QAM 

3.100 

29 

34.484 

30 

831000000 

256QAM 

2.800 

30 

34.484 

31 

837000000 

256QAM 

2.900 

31 

34.484 

32 

843000000 

256QAM 

2.700 

32 

34.926 

 

Upstream Overview 

 

 

 

 

 

Port ID 

Frequency (MHz) 

Modulation 

Signal strength (dBmV) 

Channel ID 

Bandwidth 

1 

30596000 

ATDMA - 64QAM 

42.750 

1 

6400000 

2 

38595805 

ATDMA - 64QAM 

47.250 

3 

3200000 

3 

23700000 

ATDMA - 64QAM 

41.500 

2 

6400000 

OFDM/OFDMA Overview 

 

 

 

 

 

 

 

Channel Index 

State 

lin Digital Att 

Digital Att 

BW (sc's*fft) 

Report Power 

Report Power1_6 

FFT Size 

0 

DISABLED 

0.5000 

0.0000 

0.0000 

-inf 

-1.0000 

4K 

1 

DISABLED 

0.5000 

0.0000 

0.0000 

-inf 

-1.0000 

4K

Re: CODA-4582 - Open Issues for Investigation

JohnBeaudin
I'm a Senior Contributor

@RyzenFX

 

http://about.rogers.com/cnwposts/rogers-communications-2q17-investment-community-teleconference-july...

 

The Rogers Conference was at 8:00 AM ET today, have you heard any announcement about a new gateway or the deployment of D3.1 Upstream?

Re: CODA-4582 - Open Issues for Investigation

Telek
I Plan to Stick Around

@JohnBeaudin wrote:

@RyzenFX

 

http://about.rogers.com/cnwposts/rogers-communications-2q17-investment-community-teleconference-july...

 

The Rogers Conference was at 8:00 AM ET today, have you heard any announcement about a new gateway or the deployment of D3.1 Upstream?


They better hurry up. Bell came a month ago to install fibre right into my suite. Says that in about 3-4 months they'll be lighting up the building and offering enticing Gigabit (940/100) plans to get people onboard, around or slightly lower than the same price as Rogers' special pricing plans.

Re: CODA-4582 - Open Issues for Investigation

nobs2016
I Plan to Stick Around

Been experiencing this the past 7-8 weeks. Much much longer than prior FW transitions, and now very inconvenient.

1. Modem constantly reboots knocking out my OBI VOIP ATA

2. WIFI signal interrupts while modem LEDs lit up, knocking out phones and tablets

3. WIFI signal reach reduced. Used to easily reach end of backyard ~25-30 metres. Now it struggles just outside the back door.

 

Last night was THE WORST episode. Streaming was interrupted every 5-10 minutes.

 

I'm on .29 FW. But this was an issue when I saw .27. I cannot recall the last stable version #.

Speedtest used to indicate near 900 +/- originally. Now, just approaches 500 but more often in the 250-350 range. Between "EVENTS" all runs well.

 

I've gone back several pages and see I'm not alone. Very similar DOCSIS logs.

 

Any assistance/direction before I return the CODA?

 

Thanks

 

 

 

 

 

Re: CODA-4582 - Open Issues for Investigation

@nobs2016 for the WiFi range issue, make sure you set the 5Ghz to the higher channels (149+) and set 2.4Ghz to either 1, 6, or 11.

 

 

Re: CODA-4582 - Open Issues for Investigation

nobs2016
I Plan to Stick Around

@gp-se my LAN shows 23 hours up time and WAN is at 17 hours.

 

My 2.4 is set at AUTO (1) and 5 is at AUTO (161). when I check wireless clients the 2.4's are using 1 and the 5's are using 161. Would there be more stability in selecting channel 1, 6 or 11 specifically for 2.4 and channel option 149-153-157-161 in the 5GHz?

 

If we get through the night without interruption I will check wifi range tomorrow. Or I'll exchange the modem.

Re: CODA-4582 - Open Issues for Investigation

ishine80
I Plan to Stick Around

@Datalink @RogersDave

 

I used WifiInfo View but neither of my laptops show me 5g connection.  I believe they are to old to handle it.    Below is the info you wanted less the mac addresses.  What do I do now?  Note that when my one laptop was ethernet cable connected and the wifi went down it actually would not allow me to connect to the net even through the wifi on my daughters cell which is not connected to a cell network was still streaming youtube kids app.  

 

Should i use my cell 5g connection to scan the wifi channels and post that as well? Please confirm.  ty.

 

SSIDPHY TypeRSSISignal QualityAverage Signal QualityFrequencyChannelInformation SizeElements CountCompanyRouter ModelRouter NameSecurityCipherMaximum SpeedChannel WidthChannels RangeBSS TypeWPS SupportFirst DetectionLast DetectionDetection CountStart TimeMinimum Signal QualityMaximum Signal Quality802.11 StandardsConnected
 802.11g/n-8721172.4621119114Hitron Technologies. Inc  WPA-PSK + WPA2-PSKTKIP+CCMP216 Mbps20 MHz13-SepInfrastructureNo2017-07-20 23:522017-07-21 0:0672017-07-08 5:551521802.11d/iNo
 802.11g/n-872120.72.412119114Hitron Technologies. Inc  WPA-PSK + WPA2-PSKTKIP+CCMP216 Mbps20 MHz03-JanInfrastructureNo2017-07-20 23:522017-07-21 0:10432017-06-03 21:361630802.11d/iNo
 802.11g/n-842621.72.437619114Hitron Technologies. Inc  WPA-PSK + WPA2-PSKTKIP+CCMP216 Mbps20 MHz08-AprInfrastructureNo2017-07-20 23:532017-07-21 0:00122017-07-17 20:101636802.11d/iNo
 802.11g/n-872122.72.437619114Hitron Technologies. Inc  WPA-PSK + WPA2-PSKTKIP+CCMP216 Mbps20 MHz08-AprInfrastructureNo2017-07-20 23:532017-07-21 0:0292017-05-18 9:051836802.11d/iNo
BELL187802.11g/n-783634.82.4621137716Sagemcom Broadband SASSagemcom5250_BellSagemcom5250_Bell-NQS1WPA2-PSKCCMP216 Mbps20 MHz13-SepInfrastructureConfigured2017-07-20 23:522017-07-21 0:109912017-07-10 21:582543802.11d/iNo
BELL287802.11g/n-872123.12.437634514Sagemcom Broadband SASSagemcom5250_BellSagemcom5250_Bell-NQS1WPA2-PSKCCMP216 Mbps20 MHz08-AprInfrastructureConfigured2017-07-20 23:522017-07-21 0:0292017-07-21 0:022035802.11d/iNo
Bella71802.11g/n-862319.52.437639416Hitron Technologies. IncAPxxHitronAPWPA-PSK + WPA2-PSKTKIP+CCMP216 Mbps20 MHz08-AprInfrastructureLocked2017-07-20 23:522017-07-20 23:59592017-05-18 9:051538802.11d/iNo
Dave$ave802.11g/n-459998.92.437616713   WPA2-PSKCCMP450 Mbps40 MHz12-AprInfrastructureNo2017-07-20 23:522017-07-21 0:1010592017-07-20 23:598599802.11d/iYes
Dave$ave_Ext802.11g/n-773846.62.437644517Belkin International Inc.Linksys RE6500Linksys Range ExtenderWPA-PSK + WPA2-PSKTKIP+CCMP300 Mbps40 MHz12-AprInfrastructureConfigured2017-07-20 23:522017-07-21 0:1010342017-07-21 0:002671802.11i/kNo
DIRECT-7E-HP Officejet 5740802.11g/n-842626.12.437647815Hewlett Packard0DIRECT-7E-HP Officejet 5740WPA2-PSKCCMP72 Mbps20 MHz08-AprInfrastructureLocked2017-07-20 23:522017-07-21 0:104092017-06-13 21:462038802.11h/iNo
DIRECT-A5-HP OfficeJet Pro 8710802.11g/n-872121.92.4621142914Hewlett Packard0DIRECT-A5-HP OfficeJet Pro 8710WPA2-PSKCCMP72 Mbps20 MHz13-SepInfrastructureLocked2017-07-20 23:522017-07-21 0:10552017-06-12 9:461830802.11h/iNo
f@mily802.11g/n/ac-842625.52.4621139718Belkin International Inc.EA8500Linksys17092WPA2-PSKCCMP1733 Mbps40 MHz13-MayInfrastructureConfigured2017-07-20 23:522017-07-21 0:101422017-07-01 17:271835802.11iNo
MAHOUSE802.11g/n-9016172.4621123415Hitron Technologies. Inc  WPA-PSK + WPA2-PSKTKIP+CCMP216 Mbps20 MHz13-SepInfrastructureLocked2017-07-20 23:542017-07-20 23:5422017-05-24 2:441618802.11d/iNo
Rogers12345802.11g/n-8918192.4621123815Hitron Technologies. Inc  WPA-PSK + WPA2-PSKTKIP+CCMP216 Mbps20 MHz13-SepInfrastructureLocked2017-07-20 23:522017-07-20 23:5722017-07-08 5:551820802.11d/iNo
RogersC9563802.11g/n-891820.42.412123815Hitron Technologies. Inc  WPA-PSK + WPA2-PSKTKIP+CCMP216 Mbps20 MHz03-JanInfrastructureLocked2017-07-20 23:532017-07-21 0:10482017-06-03 21:361528802.11d/iNo
WestHam1802.11g/n-842626.52.437623515Hitron Technologies. Inc  WPA-PSK + WPA2-PSKTKIP+CCMP216 Mbps20 MHz08-AprInfrastructureLocked2017-07-20 23:522017-07-21 0:0182017-07-17 20:101638802.11d/iNo

Re: CODA-4582 - Open Issues for Investigation

Raptor2148
I've Been Here Awhile

Hi,

 

 I have Asus RT-68U Router and it works fine with Bell modem.  I am new to Rogers cable and the modem Coda-4582.  I have disabled the Gateway Resident to switch it to bridge mode.  It works fine from the inside.  But my VPN on the Asus does not work.  I can't connect to my ASUS from outside.  It must be the Rogers modem.  Could someone please shed me a light?  thanks.

Re: CODA-4582 - Open Issues for Investigation

@Raptor2148, personal opinion, I'd recommend running a factory reset on the router.  That usually clears up problems when you switch modems from one ISP to another ISP.  Also look at your DNS settings in the router.  If you happened to have Bell's DNS set in the router, you might want to switch them for Rogers (leave the fields empty) or use Google or OpenDNS for example.  

 

Can you also log into the modem and confirm which firmware version is loaded?  Its listed as the Software Version on the Status page. That page comes up automatically when you log into the modem.

 

Also take note, Bell does not use IPV6.  Rogers uses Native IPV6, so, if you happened to have IPV6 enabled in your router, using anything other than Native IPV6, you will have to reset the IPV6 type and change the remaining settings.  Here are the IPV6 settings for the 68U, which I also run:

 

Connection type                 NATIVE
DHCP-PD                              Enable
IPv6 LAN Setting
LAN IPv6 Address                No entry this will fill in on its own after a router reboot where the router negotiates

                                                 with the CMTS.
LAN Prefix Length               No entry this will fill in on its own after a router reboot where the router negotiates

                                                with the CMTS.

LAN IPv6 Prefix                     No entry this will fill in on its own after a router reboot where the router negotiates

                                                with the CMTS.


Auto Configuration Setting        Stateless / Stateful I've tested both in the past and prefer to run stateful

                                                         as it offers more protection for IPV6 operations

 

IPv6 DNS Setting
Connect to DNS Server automatically              Disable       If this is enabled the router and connected devices

                                                                                                      will use Rogers IPV6 DNS 

 

IPv6 DNS Server 1                                                2620:0:ccc::2              (OpenDNS)
IPv6 DNS Server 2                                                2620:0:ccd::2              (OpenDNS)
IPv6 DNS Server 3                                                2001:4860:4860:0:0:0:0:8888             (Google)
Auto Configuration Setting
Enable Router Advertisement                             Enable



Re: CODA-4582 - Open Issues for Investigation

@ishine80 can you tell me which SSID is yours?  When the ethernet and wifi goes down on the modem, you shouldn't be able to stream video on that other cell phone unless that phone is only using IPV4 for example, or, if the phone is connected to someone else's open wifi network.  The fact that you lose the ethernet connections should indicate that the modem can't supply either ethernet or wifi networks.  That's my current thinking about this.  The only other possibility is that this is an IPV4/IPV6 issue, but, I'll have to reread your previous comments to see if you have IPV6 disabled.  If so, then this is a modem to CMTS connection issue.  



Re: CODA-4582 - Open Issues for Investigation

ishine80
I Plan to Stick Around

Hi @Datalink

SSID is Dave$ave.  Unfortunately not at home to confirm if I've got IPV6 disabled.  I can verify this evening.  What does it mean when you say the issue could be a modem to CMTS connection issue?  Our neighbours and the school board wifi are all occupying channels 1 and 6.  Later on in the evening while I was trying to play around for the tests my husbands phone and laptops were connected but I was not able to connect to wifi on my phone.  Am I understanding the situation correctly that there's so many people from rogers in my area trying to make connections with Rogers that individuals are being literally kicked off the connections to accommodate the load?  IF this is the case then firmware on a modem will not correct it will it?  Also is it possible to have a technician finally come to check things and out confirm what we need confirmed?  I'm getting to a point of not understanding on these issues.  

Re: CODA-4582 - Open Issues for Investigation

Raptor2148
I've Been Here Awhile

Thank you.

Re: CODA-4582 - Open Issues for Investigation

RogersDave
Retired Support
Retired Support

Community,

 

Quick update for everybody. I just pushed code 2.0.10.31 to some of you. Based on feedback, I will continue deployment in the coming days (and will resume firmware upgrades for new participants as well).

 

Code 2.0.10.31 on CODA is the same as 2.0.10.29 with the following changes:

  • Band steering is visible in GUI (advanced WiFi 2.4 GHz and 5 GHz)
  • DFS is visible in GUI (advanced WiFi 5GHz)
  • Available DFS channel list updated
  • USB function control displayed in gateway function GUI

 

Dave