Intermittent disconnects - CODA-4582U

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Resident Expert
Resident Expert
Posts: 6,829

Re: Intermittent disconnects - CODA-4582U

@MD83 did you have to nuke the modem to get it back to Gateway mode?  

 

What configuration are you in now, modem in Gateway or Bridge mode, TP-Link in Nat (Gateway) or Bridge mode?



Highlighted
Resident Expert
Resident Expert
Posts: 6,829

Re: Intermittent disconnects - CODA-4582U

@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:  64.71.255.204

 

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 64.71.255.204

 

Lets see how that turns out.   



Highlighted
I Plan to Stick Around
Posts: 13

Re: Intermittent disconnects - CODA-4582U

Unfortunately, I had to hard reset the modem.

I got back to Gateway mode. Both the CODA and the TP-LINK are in gateway mode currently. Apparently, you cannot set your primary Google Wi-Fi point in bridge mode without affecting the other modules.
Highlighted
I Plan to Stick Around
Posts: 13

Re: Intermittent disconnects - CODA-4582U

Awesome, I'll do that in the morning and report back.
Highlighted
I Plan to Stick Around
Posts: 10

Re: Intermittent disconnects - CODA-4582U

, that trace was probably generated on a "traceroute" web utility hosted by someone on a Linode VPS, hundreds of these pop up if you paste a tracert command into Google. Notice the formatting in the respective post, this forum would not have formatted the output of Windows' tracert/*nix traceroute as such. More plausible than the internal 45.x.x.x theory, AFAIK they (Rogers) only do this for USDoD 7.0.0.0/8 with permission; a consequence of running out of RFC1918 space.
Highlighted
Resident Expert
Resident Expert
Posts: 6,829

Re: Intermittent disconnects - CODA-4582U

@wsxedc so that's a consequence of running google wifi, it takes over your trace routes?

 

I couldn't discount the format as I'm by no means aware of all of the trace commands and results available to Rogers customers.  Maybe in a few more years 🙂



Highlighted
I Plan to Stick Around
Posts: 10

Re: Intermittent disconnects - CODA-4582U

Lol, I'm sorry. I was implying the user could have pasted it into his browser's search engine instead of the command line by mistake to find the '2nd hop'.
Highlighted
Resident Expert
Resident Expert
Posts: 6,829

Re: Intermittent disconnects - CODA-4582U

Ah, right.  Gotcha.   Ah understand what you're saying to me.  D'oh 🙂



Highlighted
I Plan to Stick Around
Posts: 9

Re: Intermittent disconnects - CODA-4582U

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

 

Hardware Version1A
Software Version2.0.10.36T6

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1591000000256QAM9.900738.983
2597000000256QAM10.000838.605
3603000000256QAM9.900938.605
4849000000256QAM7.200237.636
5855000000256QAM6.700337.356
6861000000256QAM5.900436.387
7579000000256QAM9.900538.605
8585000000256QAM9.900638.605
9279000000256QAM7.200137.356
10609000000256QAM9.8001038.605
11615000000256QAM9.9001138.605
12621000000256QAM10.0001238.605
13633000000256QAM9.8001338.983
14639000000256QAM9.7001438.605
15645000000256QAM9.1001537.636
16651000000256QAM9.0001637.356
17657000000256QAM9.0001738.605
18663000000256QAM9.0001837.636
19669000000256QAM8.8001937.636
20675000000256QAM8.9002038.605
21681000000256QAM8.7002138.605
22687000000256QAM8.7002237.636
23693000000256QAM9.0002338.605
24699000000256QAM9.0002438.605
25705000000256QAM8.9002537.636
26711000000256QAM8.7002637.356
27717000000256QAM8.6002737.636
28723000000256QAM8.3002837.636
29825000000256QAM7.3002937.356
30831000000256QAM7.6003037.356
31837000000256QAM7.2003137.356
32843000000256QAM7.4003237.356
OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
0NANANONONONA
14K275600000YESYESYES9.199997
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
122100000ATDMA - 64QAM33.25013200000
236996000ATDMA - 64QAM28.00046400000
330596000ATDMA - 64QAM30.00036400000
425300000ATDMA - 64QAM34.50023200000
OFDM/OFDMA Overview
Channel IndexStatelin Digital AttDigital AttBW (sc's*fft)Report PowerReport Power1_6FFT Size
0DISABLED0.50000.00000.0000-inf-1.00004K
1DISABLED0.50000.00000.0000-inf-1.00004K

 

 

Ping statistics for 172.217.1.164:
Packets: Sent = 3600, Received = 3537, Lost = 63 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 3434ms, Average = 28ms

Highlighted
Resident Expert
Resident Expert
Posts: 6,829

Re: Intermittent disconnects - CODA-4582U

@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 😞