× Introducing the Orbi 970 Series Mesh System with WiFi 7 technology. For more information visit the NETGEAR Press Room.
Orbi WiFi 7 RBE973
Reply

Re: XR1000 the cable modem is scanning for a downstream channel.

jeremyg237
Luminary

XR1000 the cable modem is scanning for a downstream channel.

All,

 

  A new issue has come up. I noticed last night that the internet was getting bogged down. Went and looked at the Netgear cable modem and the downstream light was blinking. I tried to reboot it from my end. It would work for a bit and then start blinking again. I got ahold of ISP and they directed me to plug directly into modem to see if it would stop blinking, which it did. So it looks like something between modem and router is causing an issue. 

 

ISP COX gigablast 1000 mbs

Cable modem Nighthawk CM2000

Router XR1000

QOS set to never, traffic pri off

geo filter off

adblocker off

netgear armor off

speed test 189 down, 37 up ping 8.17, jitter 1.36 packet loss 0% (losing internet somewhere)

 

I have tried changing channels and rebooting both modem and router. Rebooting works for a few minutes and then downstream error occurs again. Also getting missing JSON when getting onto router login. I am sure its a setting somewhere that is new to me that was not on the XR500. Any suggestions. 

Message 1 of 31
Netduma-Fraser
NetDuma Partner

Re: XR1000 the cable modem is scanning for a downstream channel.

What do you mean getting bogged down? Usually when the lights blink it just means traffic is passing through, it's not indicative of an issue
Message 2 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

 

The front panel from what I understand the downstream is not supposed to blink. My modem has never done that ion the past. 

 

https://kb.netgear.com/000060399/What-do-the-LEDs-on-my-NETGEAR-Multi-Gig-Speed-Cable-Modem-mean

Message 3 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

Bogged down, meaning I have COX gigablast 1000mbs and I am getting roughly 90 mbs on ethernet or wifi on several different devices. If I reboot modem/router I will get 980mbs for a few minutes. Light on cable modem will be solid at that point. Once its starts blinking I go back to 90mbs. 

Message 4 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

Also strange log reports

 

Admin login] from source 192.168.1.100, Sunday, Dec 11,2022 12:04:22
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 12:04:17
[Admin login] from source 192.168.1.100, Sunday, Dec 11,2022 12:02:59
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 12:01:29
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 12:00:50
[DoS attack: RST Scan] from source 17.248.169.76,port 443 Sunday, Dec 11,2022 11:58:59
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:56:30
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:56:13
[DoS attack: snmpQueryDrop] from source 205.210.31.13,port 56037 Sunday, Dec 11,2022 11:53:42
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:53:05
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:52:47
[DHCP IP: (192.168.1.103)] to MAC address XXXXXXXXXXXXX, Sunday, Dec 11,2022 11:52:00
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:49:39
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:49:08
[DHCP IP: (192.168.1.104)] to MAC address XXXXXXXXXXXXXXX, Sunday, Dec 11,2022 11:48:33
[DHCP IP: (192.168.1.104)] to MAC address XXXXXXXXXXXXXX, Sunday, Dec 11,2022 11:48:18
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:46:13
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:45:42
[DoS attack: snmpQueryDrop] from source 192.241.213.35,port 57396 Sunday, Dec 11,2022 11:44:38
[DHCP IP: (192.168.1.107)] to MAC address XXXXXXXXXXXXX, Sunday, Dec 11,2022 11:43:41
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:42:49
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:39:49
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:37:52
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:36:51
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:36:24
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:34:26
[DoS attack: ACK Scan] from source 169.197.150.7,port 443 Sunday, Dec 11,2022 11:32:07
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:31:52
[Remote login] from source , Sunday, Dec 11,2022 11:31:35
[Remote login] from source , Sunday, Dec 11,2022 11:31:23
[DHCP IP: (192.168.1.106)] to MAC address XXXXXXXXXXX, Sunday, Dec 11,2022 11:30:52
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:29:27
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:28:26
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:26:01
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:25:00
[DoS attack: ACK Scan] from source 169.197.150.8,port 443 Sunday, Dec 11,2022 11:24:17
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:21:14
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:21:00
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:17:48
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:17:34
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:15:49
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:15:33
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:14:04
[DoS attack: Fraggle Attack] from source 10.16.224.1,port 67 Sunday, Dec 11,2022 11:11:10

Message 5 of 31
Netduma-Fraser
NetDuma Partner

Re: XR1000 the cable modem is scanning for a downstream channel.

When the speed goes down, check the table view of the Device Manager and provide a screenshot please. Netgear routers often show attacks in the logs but it's usually nothing and showing normal connections. Do you chat with anyone in the UK as it is a UK IP address.
Message 6 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

No I do not chat with anyone from the UK. Maybe that has something to do with NETDUMA or xbox.

Message 7 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

Also looks like I lost IPV6 again.

Message 8 of 31
FURRYe38
Guru

Re: XR1000 the cable modem is scanning for a downstream channel.

Please post a copy and paste of the CM200 modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-m...
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-mode...

Be sure your using a good quality LAN cable between the modem and router. CAT6A STP is recommended. 

Message 9 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

I keep putting in password for modem and nothing happens.

Message 10 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

I tries edge, chrome and firefox. All say not secure. I even allowed and once i put in password nothing happens. The cable between modem and router is a cat6. The ethernet cable that comes with the XR1000 is a cat5e.

 

Message 11 of 31
Netduma-Fraser
NetDuma Partner

Re: XR1000 the cable modem is scanning for a downstream channel.

One of the ports there is reading as only allowing 100Mbps, switch out the cable for the device that is having the issue and switch it with another, do the speeds improve?
Message 12 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

I tried switching different cables. The only thing that works is rebooting both router and modem, butr it only works for a few minutes. 

Message 13 of 31
Netduma-Fraser
NetDuma Partner

Re: XR1000 the cable modem is scanning for a downstream channel.

If you try it in a different port does that make a difference? If you do the Device Manager table view after a reboot again does it show all link speeds at 1000?
Message 14 of 31
FURRYe38
Guru

Re: XR1000 the cable modem is scanning for a downstream channel.

I recommend that you change the cable between the XR and CM modem to CAT6A STP. 

 

Factory reset the CM modem and setup from scratch and input a new PW for the modems web page. 


@jeremyg237 wrote:

I tries edge, chrome and firefox. All say not secure. I even allowed and once i put in password nothing happens. The cable between modem and router is a cat6. The ethernet cable that comes with the XR1000 is a cat5e.

 


 

Message 15 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

I moved everything to where it was originally in the house. Looks like there was issues with how I had it hooked up. So far everyuthing is good to include IPV6. Will keep you posted. Fingers crossed

Message 16 of 31
FURRYe38
Guru

Re: XR1000 the cable modem is scanning for a downstream channel.

If you seem to run in to issues again, please post the cable connections status and event logs page from the CM modem. 

 

Any possible same impact on the XR500? 

 

Hope it works better for you. 

Message 17 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

Lost IPV6 again. Speed seems to be good. I cannot login into modem. I can get to the CM2000 page but every time I put the password in nothing happens.

Message 18 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

un Dec 11 21:13:27 2022               (Warning (5))     Dynamic Range Window violation

Sun Dec 11 21:13:27 2022             (Warning (5))     RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM- =1.1;CM-VER=3.1;

Sun Dec 11 21:13:27 2022             (Warning (5))     Dynamic Range Window violation

Sun Dec 11 21:13:27 2022             (Warning (5))     RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC= -QOS=1.1;CM-VER=3.1;

Sun Dec 11 20:50:47 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM- CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 20:50:07 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 20:20:11 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=bCM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 20:19:43 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 20:16:58 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 20:15:12 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 20:12:47 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 20:12:26 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 20:12:13 2022             (Warning (5))     Dynamic Range Window violation

Sun Dec 11 20:12:13 2022             (Warning (5))     RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 20:12:12 2022             (Warning (5))     Dynamic Range Window violation

Sun Dec 11 20:12:12 2022             (Warning (5))     RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 19:59:06 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 19:58:38 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 19:41:04 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 19:40:22 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 19:10:58 2022             (Warning (5))     Dynamic Range Window violation

Sun Dec 11 19:10:58 2022             (Warning (5))     RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 19:10:58 2022             (Warning (5))     Dynamic Range Window violation

Sun Dec 11 19:10:58 2022             (Warning (5))     RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 19:04:49 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 19:03:45 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:59:18 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:58:53 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:42:51 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:42:22 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:35:10 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:34:30 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:32:32 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:32:06 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:25:21 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:24:56 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:22:58 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:22:07 2022             (Notice (6))         CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Sun Dec 11 18:09:44 2022             (Warning (5))     Dynamic Range Window violation

Sun Dec 11 18:09:44 2022             (Warning (5))     RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;

Message 19 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

Everytime I try to upload the other info. Netgear keeps saying I am flodding msg board.

 

Message 20 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

I hooked up the XR500 to see what happens over night with IPV6 as well as the modem dowload blinking.

Message 21 of 31
Netduma-Liam
NetDuma Partner

Re: XR1000 the cable modem is scanning for a downstream channel.

The previous time you lost IPv6, was that without the XR500 connected? Let us know how you get on with it connected again if so.

Message 22 of 31
FURRYe38
Guru

Re: XR1000 the cable modem is scanning for a downstream channel.

Can you capture the cable connections page from the CM modem now? 

Copy and paste that in to a PDF or picture file then select Choose File on your post to attached it to the post instead of trying to put it in the post window. 

@jeremyg237 

 

Event log looks ok...Thought I see some Warnings that maybe the ISP should take a look at. 

Message 23 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

Never lost IPV6 on XR500.

Message 24 of 31
jeremyg237
Luminary

Re: XR1000 the cable modem is scanning for a downstream channel.

 
Message 25 of 31
Discussion stats
  • 30 replies
  • 2542 views
  • 2 kudos
  • 5 in conversation
Announcements

Orbi WiFi 7