I have been experiencing intermittent disconnects of internet service for a few minutes at a time and have replaced the CODA-4582U with no improvement. The modem is is bridged mode and after reading some of the other posts I believe there may be a signal issue. I was able to capture the following info from the DOCSIS Event log today and was hoping someone could interpret and point me in the right direction to resolve the issue.
Thanks for your help.
**Removed logs due to Community Guideline: Keep personal info private. - RogersZia**
Solved! Solved! Go to Solution.
Yup, connect the TP-Link to the modem and then connect to the TP-Link.
Use 192.168.100.1 thru the router. You can also use that with a direct connection to the modem when its in Bridge mode.
I don't encourage a direct connection to the modem when its in Bridge mode due to the constant port scanning by various miscreants scattered across the internet, probing for open ports or mis-configured firewalls.
With V184.108.40.206T6, in the modem as indicated on the status page, you can use 192.168.01. or 192.168.100.1 when the modem is in Gateway mode. When its in Bridge mode you can only use 192.168.100.1, which will normally work thru any connected router. There are exceptions but they are few and far between, so to speak.
With V220.127.116.11 loaded you can only use 192.168.0.1 when the modem is in Gateway mode and only use 192.168.100.1 when the modem is in Bridge mode.
@MD83 there are a few ways to do this.
1. connect directly to the modem, even though I'm not a huge fan of this.
2. As soon as the pc/laptop gains an IP address, log into the modem using 192.168.100.1 I'm assuming that the modem is stuck in Bridge mode.
3. kick the modem back into Gateway mode when you've managed to log in.
Call tech support and ask the CSR to switch your modem back into Gateway mode
Reset the modem. Ugh. Depress the recessed reset button at the back of the modem for at least 15 seconds. It should reset the modem, at which point the modem will reboot into Gateway mode. Unfortunately you would have to set the modem up from scratch.
With the modem in Bridge mode, if you rebooted the TP-Link router it should pick up its assigned external address from the modem and you should be able to use 192.168.100.1 to access the modem's login page. If you can't, then the TP-Link is blocking the path out to the modem. Usually thats taken care of by defining a route out to the modem, but, I don't know if the TP-Link will let you do that.
This menu displays general information of the device
Hardware Version 1A
Software Version 18.104.22.168T6
System Time Wed, 18 Mar 2020 01:40:55
Time Zone UTC+00:00 Greenwich Mean
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 591000000 256QAM 9.800 7 38.605
2 597000000 256QAM 9.800 8 38.605
3 603000000 256QAM 9.700 9 38.605
4 849000000 256QAM 7.100 2 37.356
5 855000000 256QAM 6.500 3 36.610
6 861000000 256QAM 5.800 4 36.387
7 579000000 256QAM 9.700 5 38.605
8 585000000 256QAM 9.800 6 38.605
9 279000000 256QAM 7.000 1 37.636
10 609000000 256QAM 9.600 10 38.605
11 615000000 256QAM 9.800 11 37.636
12 621000000 256QAM 9.800 12 38.605
13 633000000 256QAM 9.600 13 38.605
14 639000000 256QAM 9.500 14 37.636
15 645000000 256QAM 8.900 15 37.636
16 651000000 256QAM 8.800 16 37.636
17 657000000 256QAM 8.800 17 38.605
18 663000000 256QAM 8.700 18 37.636
19 669000000 256QAM 8.500 19 37.356
20 675000000 256QAM 8.700 20 38.605
21 681000000 256QAM 8.400 21 38.605
22 687000000 256QAM 8.400 22 37.636
23 693000000 256QAM 8.700 23 37.636
24 699000000 256QAM 8.700 24 38.258
25 705000000 256QAM 8.800 25 37.636
26 711000000 256QAM 8.700 26 37.636
27 717000000 256QAM 8.600 27 37.636
28 723000000 256QAM 8.400 28 37.636
29 825000000 256QAM 7.300 29 36.610
30 831000000 256QAM 7.400 30 36.610
31 837000000 256QAM 7.000 31 37.356
32 843000000 256QAM 7.200 32 37.356
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 9.000000
Will get you trace route soon as I log on my laptop
Got it up and running again. We'll see if the problem still persists, as I assume it will. Any further ideas before the tech comes to check things out. Again, I really appreciate the time and effort given here.
@MD83 I'm assuming that Rogers is using that 45.xxx.xxx.xxx block internally, which is a little odd, but, it is what it is.
Just to see whats up, and not worry about any confusion with the modem or TP-Link configuration, try pinging Rogers primary IPV4 DNS: 22.214.171.124
I'd let that run in the background while you're running the normal household internet activities. That might cause higher latency, but, I suspect the family would revolt if you said, "no internet for an hour!" Ok, so, run:
ping -n 3600 126.96.36.199
Lets see how that turns out.
Sorry, I was getting that from phone and its selected all with copy. There is latest from laptop along with trace route from google. Please analyze and let me know as I have a tech visit tommorow and would like some insight before.
Oh yeah coda 4582 fw ver
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC power(dBmv)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Bandwidth|
|1||22100000||ATDMA - 64QAM||33.250||1||3200000|
|2||36996000||ATDMA - 64QAM||28.000||4||6400000|
|3||30596000||ATDMA - 64QAM||30.000||3||6400000|
|4||25300000||ATDMA - 64QAM||34.500||2||3200000|
|Channel Index||State||lin Digital Att||Digital Att||BW (sc's*fft)||Report Power||Report Power1_6||FFT Size|
Ping statistics for 188.8.131.52:
Packets: Sent = 3600, Received = 3537, Lost = 63 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 3434ms, Average = 28ms
@savuser12 your DOCSIS 3.0 channels (1 to 32) are higher than they should be, arguably within spec, yes, but, then should be down around 0 dBmV. Your QAM levels are ok, the signal to noise ratios are ok as well.
The upstream DOCSIS 3.0 levels aren't too bad where they currently sit.
The DOCSIS 3.1 OFDM channel can't be assessed as the signal level, signal to noise ratio and QAM Level isn't presented to the user. Tech support has access to that data, and I would expect the field techs to have access to that data as well.
My personal opinion about the packet loss in the ping test is that its higher than it should be, but, I base that on my test results from West Ottawa, which are typically well under 1%. The distribution of the high ping times (latency) would be interesting to see and it might be the more important point here. That's something I have to work on to make it easy to accomplish.
On the surface, yes the downstream signal levels are higher than normal, but, given the problems with the Rogers network these days, you might not have any problems caused by local issues. That's really problematic these days, are the problems local, or are they network issues? Really the only thing the tech can do is check the cables and connectors for continuity. That's a minor check and might not do much if anything to address any latency and packet loss that you're seeing 😞
@Datalink Here are the results of the ping test to the second hop, with the computer plugged directly into the CODA. The test took about two hours to complete.
Ping statistics for 184.108.40.206:
Packets: Sent = 3600, Received = 3178, Lost = 422 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 3981ms, Average = 277ms
Slightly off-topic, but would "upgrading " to Rogers Ignite Internet Gigabit" do anything to alleviate my ongoing issues? This at least would replace/upgrade the modem to the Arris XB6 , if that makes any difference at all..?
Maybe the solution is to request a tech visit to check for noise issues? Don't know. The modems themselves are equipped to check and monitor for noise and as far as I know there is a noise record kept to each modem, if not minute by minute, maybe every five minutes. Don't know why Rogers can't use that record to initiate further action to resolve upstream noise issues.