CODA 4582 - Bridge Mode issues?

[Effayy]

The past couple of weeks my internet connectivity has been spotty again.  Gaming is particularly affected.  My kids and I are routinely getting bounced from online play. My son with his Oculus has constant issues as well.  We did have an original problem that ended up being a cable outside of the house.  That was resolved (thanks @Datalink!) and has worked great for the past few months, and now we seem to have a different issue. 

Pinging the CMTS is 100% uptime over 24 hours.  Pinging the DNS server is 100% uptime over 24 hours.  Pinging the cablemodem itself however, 0% success.  I also can't hit the UI in bridge mode at all.  I read that the 7.x firmware has issues and an unplug/10 second wait / re-plug will do the trick temporarily, but that's not the case for me.  Gateway mode is just fine, bridge mode is not.  I recall having no issues as recently as 3 weeks ago or so.

Even more confusing, I actually have a second CODA here (4582U) and had that re-activated, I'm having the exact same problem with that one as well.  

To troubleshoot and take the other aspects of my network out of the equation, I wired my PC directly to a port on the cablemodem.  I get an IP, I can access external websites no problem, etc.  What I still cannot do though is access or ping 192.168.100.1, even after a fresh unplug reboot, and even a couple of factory resets.

Am I going nuts or can the same firmware issue affect 2 modems in my house?  Could it be a setting with my Windows 10 network config that isn't allowing me to see the cablemodem for some reason?  I temporarily turned of my PC's firewall in case there was an issue there but still nothing.  As I said, direct ethernet connection to the modem and no luck, and this was working just fine (even from the other side of my 3rd party mesh router) as recently as 3 weeks or so ago.

Anyone experiencing the same thing or have any ideas as to how I can fix this?

[Datalink]

@Effayy what you're seeing is definitely out of the ordinary.  Only explanation I can think of is a firmware update that isn't behaving properly.  

Are the modem's stuck in Bridge mode?  As in you can't access the user interface to kick them back into Gateway mode?

Would you happen to know what Software (firmware) is loaded, as shown on the modem's status page?

My personal opinion is to force a factory reset by holding down the recessed reset button at the back of the modem for 30 seconds.  The modem should run a firmware version check and either update to the latest version or reload the latest version if that's what is currently loaded.  Personally speaking, if my modem or router doesn't respond the way it should, after a couple of attempts, I'll run a factory reset.  I won't wait for it, as I know what it should be doing, not what it might be doing at the moment.  I'd run the factory reset and see that happens afterword.  

Assuming that you run the factory reset, I'd be interested in seeing the firmware version that is currently loaded and the signal levels from the DOCSIS WAN page.  Please post all of the signal levels, from the Downstream Overview line at the top, all the way down to the last character in the very bottom OFDM/OFDMA Overview section. 

[Effayy]

@Datalink you are correct. The modem(s) are stuck in bridge mode.  I can't reach the UI to set it back to Gateway.  The only option is to do a factory reset (hold down reset for 30 secs)., and 5 minutes ago I did just that to get you some stats. 🙂  Just before doing this I was running a "ping -t 192.168.100.1" while going through the unplug / waiting 10 secs / replug of the modem, and not once did it reply to my ping.

It's running 7.1.1.37 currently, and based on my memory that is also the firmware rev. I noted after my previous factory reset as well.

DOCSIS WAN stats are as follows:

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	591000000	QAM256	-2.000	7	38.983
2	597000000	QAM256	-2.099	8	38.983
3	603000000	QAM256	-2.400	9	38.605
4	609000000	QAM256	-2.500	10	38.605
5	849000000	QAM256	-5.200	2	37.636
6	855000000	QAM256	-5.400	3	36.609
7	861000000	QAM256	-5.900	4	36.609
8	579000000	QAM256	-1.599	5	38.983
9	585000000	QAM256	-1.799	6	38.983
10	279000000	QAM256	5.500	1	38.983
11	615000000	QAM256	-2.599	11	38.605
12	621000000	QAM256	-2.599	12	38.605
13	633000000	QAM256	-3.000	13	37.636
14	639000000	QAM256	-3.099	14	37.636
15	645000000	QAM256	-3.200	15	37.636
16	651000000	QAM256	-3.500	16	37.636
17	657000000	QAM256	-3.900	17	37.636
18	663000000	QAM256	-4.200	18	37.636
19	669000000	QAM256	-4.299	19	37.636
20	675000000	QAM256	-4.500	20	37.355
21	681000000	QAM256	-4.299	21	37.355
22	687000000	QAM256	-4.200	22	37.636
23	693000000	QAM256	-4.099	23	37.355
24	699000000	QAM256	-4.000	24	37.355
25	705000000	QAM256	-4.000	25	37.636
26	711000000	QAM256	-4.200	26	37.636
27	717000000	QAM256	-4.200	27	37.355
28	723000000	QAM256	-4.799	28	37.355
29	825000000	QAM256	-4.900	29	37.636
30	831000000	QAM256	-4.900	30	37.355
31	837000000	QAM256	-4.799	31	37.636
32	843000000	QAM256	-5.099	32	37.355

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	275600000	YES	YES	YES	4.699997

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	21100000	64QAM	34.010	1	3200000
2	38700000	64QAM	37.020	4	6400000
3	32300000	64QAM	35.770	3	6400000
4	25900000	64QAM	35.770	2	6400000
5	0	QAM_NONE	-	---	1600000
6	0	QAM_NONE	-	---	1600000
7	0	QAM_NONE	-	---	1600000
8	0	QAM_NONE	-	---	1600000

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.0000	0.0000	0.0000	0.0000	0.0000	2K
1	DISABLED	0.0000	0.0000	0.0000	0.0000	0.0000	2K

From what I can tell, my signal strength and SNR seem to be within a normal range.  Unsure about upstream.  Also ODFMA is disabled which I understand is a good thing as well.  I can ping 192.168.0.1 without issue (of course since I can access the UI). 

I'll fire this back into bridge mode and see if 4th time's the charm?  I don't expect to be able to access UI or ping 100.1, but I'll edit this post otherwise.

[jn00]

I am running firmware version 7.2.4.1.4b15 and have the same issue with bridge mode.  I am unable to connect to the UI via 192.168.100.1, even after reboot.  I did a factory reset into gateway mode and after that I AM able to consistently login via 192.168.0.1.  So the problem seems to be with bridge mode only.

The bridge mode UI access problem has been an issue for a while, but it seems like the latest versions of the firmware (7.1.1.37, 7.2.4.1.4b15) have made it worse.

[Effayy]

So I did a little tinkering tonight, and thanks to a tip from a co-worker of mine, I figured something out that may help you as well:

I stated before that I couldn't connect to the modem's UI even when directly connected.  That was because I didn't go into my Adapter settings in Windows and manually assign a 192.168.100.x IP to the NIC (the modem was assigning a WAN IP directly to the box by default).  Afterwards, I got in.  Now, I never had to do that before.  My router could always hit 100.1 despite the rest of my devices existing on 50.x.  No idea what changed, but something obviously did.  

I did notice that my Gateway and Bridged firmware versions are completely different. (7.1.1.37 for gateway, 7.2.4.1.4b15 for bridge).  I hadn't really checked before so unsure if this is expected.

Once my connection starts acting up again, I'll be able to provide the DOICSIS WAN stats here again.  Hopefully that can help piece together where my problem is coming from.

[Effayy]

I'm currently experiencing issues with my service (frequently cutting-out of my work meetings).  Now that I can access the modem in bridge mode, I've copied the DOCSIS WAN stats here.  @Datalink, by any chance do you see anything in here that may explain my spotty service?  Running a constant ping against the DNS server hasn't shown any timeouts.

Downstream Overview

Port ID	Frequency (Hz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)	Bytes	Correcteds	Uncorrectables
1	591000000	QAM256	-2.299	7	37.636	4102314369	0	0
2	597000000	QAM256	-2.500	8	38.605	3413880241	1	0
3	603000000	QAM256	-2.599	9	37.636	3402673289	2	0
4	609000000	QAM256	-2.700	10	38.605	3129414479	0	0
5	849000000	QAM256	-5.599	2	37.636	487194749	13	0
6	855000000	QAM256	-5.799	3	36.609	495381181	0	0
7	861000000	QAM256	-6.400	4	36.609	493015792	0	0
8	579000000	QAM256	-1.900	5	38.605	3494367199	2	0
9	585000000	QAM256	-2.000	6	38.605	3507248433	3	0
10	279000000	QAM256	5.300	1	38.983	3570292219	11	0
11	615000000	QAM256	-2.700	11	38.605	3075679171	1	0
12	621000000	QAM256	-2.599	12	38.605	3137321946	8	0
13	633000000	QAM256	-3.000	13	37.636	3258862369	8	0
14	639000000	QAM256	-3.200	14	37.355	3244136858	0	0
15	645000000	QAM256	-3.299	15	37.636	3249369047	0	0
16	651000000	QAM256	-3.700	16	37.636	3202843691	1	0
17	657000000	QAM256	-4.099	17	37.355	2974639474	0	0
18	663000000	QAM256	-4.500	18	37.355	2898664265	2	0
19	669000000	QAM256	-4.599	19	37.355	2887437353	1	0
20	675000000	QAM256	-4.700	20	37.636	3048264915	0	0
21	681000000	QAM256	-4.500	21	37.355	3050161462	0	0
22	687000000	QAM256	-4.500	22	37.636	3049743087	2	0
23	693000000	QAM256	-4.299	23	37.636	2944238156	0	0
24	699000000	QAM256	-4.299	24	37.355	3044642884	1	0
25	705000000	QAM256	-4.299	25	37.355	3162182211	0	0
26	711000000	QAM256	-4.500	26	37.355	3163729103	0	0
27	717000000	QAM256	-4.500	27	37.355	3153387441	0	0
28	723000000	QAM256	-5.099	28	36.609	379693893	0	0
29	825000000	QAM256	-5.200	29	37.355	518363215	0	0
30	831000000	QAM256	-5.299	30	37.355	524438930	0	0
31	837000000	QAM256	-5.099	31	37.636	520510758	0	0
32	843000000	QAM256	-5.299	32	37.355	503349134	0	0
Reset FEC Counters

OFDM Downstream Overview

Receiver	FFT type	Subcarr 0 Frequency(MHz)	PLC locked	NCP locked	MDC1 locked	PLC Location	Occupied BW(MHz)	Subcarriers	PLC power(dBmv)
0	NA	NA	NO	NO	NO	NA	0 ~ 0	NA	NA
1	4K	275600000	YES	YES	YES	1544	307 ~ 448.95	2788	4.500000

Upstream Overview

Port ID	Frequency (Hz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	38700000	64QAM	36.270	4	6400000
2	21100000	64QAM	34.760	1	3200000
3	32300000	64QAM	36.270	3	6400000
4	25900000	64QAM	36.270	2	6400000

OFDMA Overview

Channel Index	State	lin Digital Att	Digital Att	BW (sc's*fft)	Report Power	Report Power1_6	FFT Size
0	DISABLED	0.0000	0.0000	0.0000	0.0000	0.0000	2K
1	DISABLED	0.0000	0.0000	0.0000	0.0000	0.0000	2K

[Datalink · Accepted solution]

@Effayy your signal levels are all low except for the 279 Mhz QAM channel, which resides just below the downstream OFDM channel.  So, that entire OFDM channel ramps down in terms of signal level, from the lowest frequency to the highest frequency.  Thats not ideal, but, I don't know if that's a real problem.  Send a message to @CommunityHelps and ask Tony or Moin to have a look at the downstream OFDM MIBS.  Thats an OFDM channel breakdown into smaller subchannels, each with its own signal level and signal to noise ratio.  Tech support level 1 doesn't have access to this data for some reason.  So, the question here is whether or not that ramp down has any effect on the OFDM channel performance.  

Fwiw, I've always found that following a firmware update that:

1.  At the very least, a modem restart/reboot was required, despite the fact that a modem reboot is built into the update process.  

2.  If that didn't resolve any strange problems, then I usually run a factory reset.  That usually resolves any issues.  My normal practice is to simply run a factory reset when I've notices that the firmware has been updated.  So, if you're noticing issues with video conferencing, that's the first thing that I would do.  After the factory reset, you can kick the modem back into Bridge mode.  

I've haven't had any issues recently accessing the modem, so although the nic address change appears to work, you shouldn't have to do that.  I don't have any explanation for the problem.  

[1btflboy]

I'm having the exact same problem: gateway mode (192.168.0.1) has no problems but, after switching to bridge mode (192.168.100.1), I cannot log into the HITRON CODA-4582's user interface at all, even though I have internet access from my (Win10) PC. (2022-DE-22)

[Datalink]

@1btflboy you probably still have firmware version 7.2.4.1.4b15 loaded.  Rogers is currently loading version 7.2.4.7.1b4 on the 4582 modems.  My 4582 was updated yesterday morning.  Interestingly, I didn't have internet service after the update, although all of the front LEDs indicated that the modem was operating normally.  That's very unusual for this modem, following an update.  So, after pulling the power from the modem and plugging it back in after a 15 second wait, the modem restarted and ended up in normal operation once again.  The problem with logging into the 4582 when its in Bridge mode has been fixed.  That was due to a change to IPV6 addressing for Rogers back end systems.  

Fwiw, I've always found that following a firmware update that:

1.  At the very least, a modem restart/reboot was required, despite the fact that a modem reboot is built into the update process. 

2.  If that didn't resolve any strange problems, then I usually run a factory reset.  That usually resolves any issues.  My normal practice is to simply run a factory reset when I've noticed that the firmware has been updated.  So, if you're noticing any unusual issues after the update, that's the first thing that I would do.  After the factory reset back into Gateway mode, you can kick the modem back into Bridge mode.