I thought I'd create a new thread for those who end up getting the SB8200 so they can post screenshots (not copy/pasting) and experiences and signal stuff. :)

I've had my SB8200 about a month with Cox ISP and have a recurring problem where IPv4 stops working but IPv6 is fine. I can only access websites that have AAAA records in DNS with an IPv6 address. Restarting modem fixes issue - restarting my Netgear Orbi router doesn't help. Prior to SB8200 I had a Netgear CM600 and never had this issue. I don't have an OFDM channel yet, my SB8200 modem is connected on 32 downstream and 4 upstream channels. I telnetted into my Netgear Orbi router to do some troubleshooting. Everything looks good root@RBR50:/# route -nKernel IP routing tableDestination Gateway Genmask Flags Metric Ref Use Iface0.0.0.0 174.66.192.1 0.0.0.0 UG 0 0 0 brwan174.66.192.0 0.0.0.0 255.255.248.0 U 0 0 0 brwan192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0239.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 br0 Redacted my specific IP (xxx) root@RBR50:/# ip route default via 174.66.192.1 dev brwan 174.66.192.0/21 dev brwan proto kernel scope link src 174.66.196.xxx192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.1 239.0.0.0/8 dev br0 scope link root@RBR50:/# ip -6 route 2600:8806:8200:1b::/64 dev br0 proto kernel metric 256 2600:8806:9f00:200:2889:2343:2702:592b dev brwan proto kernel metric 256 fe80::/64 dev eth1 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 dev ath0 proto kernel metric 256 fe80::/64 dev ath1 proto kernel metric 256 fe80::/64 dev ath2 proto kernel metric 256 fe80::/64 dev ath01 proto kernel metric 256 fe80::/64 dev brwan proto kernel metric 256 fe80::/64 dev br0 proto kernel metric 256 default via fe80::6600:f1ff:fe3f:efd9 dev brwan metric 1 root@RBR50:/# cat /etc/resolv.conf nameserver 68.105.28.11nameserver 68.105.29.11nameserver 68.105.28.12nameserver 2001:578:3f::30 nameserver 2001:578:3f:1::30 Did some ping tests. I cannot ping default gateway 174.66.192.1 from my computers or from the router itself. I can ping IPv6 hosts out on the internet just fine, can't ping IPv4 hosts: root@RBR50:/bin# ping6 e16.ycpi.nya.yahoo.comPING e16.ycpi.nya.yahoo.com (2001:4998:1c:803::2003): 56 data bytes64 bytes from 2001:4998:1c:803::2003: icmp6_seq=0 ttl=58 time=33.9 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=1 ttl=58 time=41.1 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=2 ttl=58 time=33.8 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=3 ttl=58 time=33.4 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=4 ttl=58 time=33.5 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=5 ttl=58 time=33.2 ms^C--- e16.ycpi.nya.yahoo.com ping statistics ---6 packets transmitted, 6 packets received, 0% packet lossround-trip min/avg/max = 33.2/34.8/41.1 ms root@RBR50:/bin# ping e16.ycpi.nya.yahoo.com PING e16.ycpi.nya.yahoo.com (69.147.82.219): 56 data bytes The IPv4 ping test seems to be resolving via ipv6 resolvers based on how long it took to resolve. I feel like it timed out on the three v4 resolvers in /etc/resolv.conf before hitting ipv6 resolvers and getting a v4 IP address back from v6 resolver. So at this point, I restarted my router. Didn't help anything. GUI said it couldn't connect to internet. So I restarted my modem, and then it worked! Routing tables on the router and resolv.config looked identical after restarting modem - I received same IP address from Cox. I've had this particular IPv4/IPV6 issue happen about 4 times over course of ownership of this modem (so weekly). Each time, restarted modem fixes. This last time I didn't even both restarting router. I wonder if this is related to this other problem I have with SB8200 where I can't access admin page: https://www.dslreports.com/forum/r31725961-Modem-Admin-page-blocked-on-my-SB8200 I called ARRIS first, they said there is nothing to configure on modem so nothing to do other than call Cox. Called Cox, they didn't really have any ideas either. Said call next time it happens. I found similar complaints on Comcast forum (I have Cox service) from both users of the SB8200 and MB8600 (same chipset): http://forums.xfinity.com/t5/Your-Home-Network/Frequently-loosing-IPv4-while-IPv6-is-fine/td-p/2923874 http://forums.xfinity.com/t5/Your-Home-Network/Re-Frequently-loosing-IPv4-while-IPv6-is-fine/td-p/3016461 http://forums.xfinity.com/t5/Your-Home-Network/Motorola-MB8600-frequently-loses-IPv4-connection-but-IPv6-is-ok/td-p/2996458 Anyone else experiencing this?

I've recently switched from ATDD DSL to Comcast cable modem. This is the first time I've ever used Cable Modem, I've always been a DSL user. We only paid for 55Mb/down and 5Mb up. Shortly after we switched to Comcast, they've upped the download speed to 71Mb, without charging us. Initially, i used Comcast's gateway to make sure everything worked, but then I had ordered a Netgear R8000 router and a Surfboard SB6183. I've returned the gateway to Comcast and no longer pay a monthyl fee. I generally check my speeds several times a week, and usually at night (around8PM PST), when most people are home and streaming. I've been measuring ~68-71 Mb down and 5-6 Mb up, consistantly. So far, I'm happy with my new service and equipment, I hope it stays that way.

There were rumors several months back that a future firmware update would enable SB8200 owners to use both ethernet ports simultaneously to achieve higher bandwidth. Has there been any new news regarding this? Has anyone given it a shot? I know each port works individually right now, but I wanted to know if it was possible to use both. Thanks for any insight that anyone can give!

(Since I don't see my ISP listed somewhere on the forums, I go ahead and post it here since I own a Arris modem + router, I hope I'm on the right place...) I'm in the 30Mbps Download/ 1Mbps Upload only internet plan (is cable internet) from a ISP called Liberty Cablevision of Puerto Rico for about 4 years and now there's a problem which has been persisting since January 18th, 2018 with the Arris/Motorola Touchstone SVG6582 modem + router combo (gateway)... To better clarify the situation, I did not have this problem until hurricane Maria arrived. It wrecked the power grid completely and I suspect that might have damaged the internet cables due to the hurricane. I had no internet about 4 months and finally got the service back. Also, to just mention other detail... is when I had no power, I used a power generator to generate electricity partially every 5 hours or more and had the gateway connected (which I had no internet service at that time). Every time the generator shuts down, the power it flickers a few times until finally ends. I don't know if has to do with it because I remember years ago that one of the ISP's technicians said that outages can damage the gateway by overloading it every time the power went out, which is also the same case for other electronics such as refrigerators and TVs for example. So that's why I mention that if that's a possible cause but let me explain the problem... The first thing that I noticed is it's intermittent connection: it just stops and then starts again. I'm still on this situation, I haven't called a tech yet, I was trying many approaches to fix the problem but to no avail. It had restarted by itself for quite sometime for about approx. 4 times a day but seems to have stopped by itself. There's the information for the gateway: Information Standard Specification Compliant: DOCSIS 3.0 Hardware Version: 1 Software Version: SVG6X82-6.5.2.1-GA-00-06-LTSH Cable Modem MAC Address: [removed] Cable Modem Serial Number: 398681406301496404010003 CM certificate: Installed Then there's the connectivity: Downstream Bonded Channels (as 9:24PM) Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 11 555000000 Hz -1.5 dBmV 31.0 dB 3237941 70071 2 Locked QAM256 12 561000000 Hz -1.4 dBmV 37.9 dB 9 0 3 Locked QAM256 1 567000000 Hz -2.1 dBmV 40.8 dB 14 0 4 Locked QAM256 2 573000000 Hz -1.9 dBmV 40.9 dB 18 0 5 Locked QAM256 3 579000000 Hz -0.7 dBmV 41.5 dB 7 0 6 Locked QAM256 4 585000000 Hz -0.2 dBmV 41.9 dB 5 0 7 Locked QAM256 5 591000000 Hz -0.1 dBmV 41.8 dB 5 0 8 Locked QAM256 6 597000000 Hz -0.3 dBmV 41.9 dB 11 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked TDMA and ATDMA 6 2560 Ksym/sec 30600000 Hz 48.5 dBmV 2 Locked TDMA and ATDMA 4 2560 Ksym/sec 37000000 Hz 48.5 dBmV 3 Locked TDMA and ATDMA 3 2560 Ksym/sec 33800000 Hz 48.5 dBmV 4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV Also I add the event log in: Time Priority Description Sat Feb 03 21:34:26 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 20:50:51 2018 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE Sat Feb 03 20:49:03 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 20:23:10 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 20:18:44 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 20:10:38 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 20:07:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 20:04:25 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 20:03:47 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 20:03:35 2018 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:GUI Sat Feb 03 20:03:20 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 20:02:58 2018 Notice (6) WiFi Interface [wl0] set to Channel 5 (Side-Band Channel:N/A) - Reason:GUI Sat Feb 03 20:02:56 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 20:00:01 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 19:58:50 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 19:16:19 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 19:15:26 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 19:13:59 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 19:12:14 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:48:40 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:44:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:36:27 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:36:19 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:36:14 2018 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE Sat Feb 03 18:35:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:34:30 2018 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Sat Feb 03 18:34:21 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:28:45 2018 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Sat Feb 03 18:28:06 2018 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE Sat Feb 03 18:27:43 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:27:40 2018 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Sat Feb 03 18:27:23 2018 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Sat Feb 03 18:25:55 2018 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:GUI Sat Feb 03 18:24:51 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:24:02 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:23:56 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:23:12 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:22:04 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 18:20:50 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 17:53:14 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 17:51:35 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 17:50:43 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 17:50:33 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 17:41:21 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 17:41:18 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 17:37:19 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 17:36:16 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 17:05:59 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 17:05:35 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 16:13:13 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 16:13:03 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 16:12:00 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 16:11:43 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:56:16 2018 Error (4) Map Request Retry Timeout;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:55:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:54:56 2018 Error (4) Improper Configuration File CVC Format Sat Feb 03 15:54:55 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:54:51 2018 Notice (6) TLV-11 - unrecognized OID;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT Sat Feb 03 15:51:17 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:50:26 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:50:12 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:48:46 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:48:34 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:43:27 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:43:09 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:41:28 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:40:59 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:40:47 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:40:27 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:39:46 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:39:22 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:39:21 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:38:49 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:24:11 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:23:39 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:21:11 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:20:57 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:20:10 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:19:52 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:17:27 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:17:09 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:13:30 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:13:22 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:11:20 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:11:12 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:06:06 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:05:47 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:05:11 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:04:42 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:04:11 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:04:09 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:03:37 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:00:31 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 15:00:22 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 14:56:50 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; Sat Feb 03 14:56:34 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=00:17:10:84:bd:9d;CM-QOS=1.1;CM-VER=3.0; I get the T3 and T4 timeout a lot, like every minute or so... That's doesn't sound so good according what I researched... I'm thinking has to do with the condition of the cables... I play games a lot and I experience a lot of disconnections, is just so frustrating. Sometimes is just when I'm surfing on the internet and watching YouTube videos. I even go 4 hours uninterrupted until it disconnects again. Is worse when 5 devices or more are connected into one single network (we're 5 in the house). Also part of the cable that connects the gateway is partially chewed up by my dog... it sounds kinda stupid, but didn't do a lot of damage compared to the old cable that are hanging around that are unused... only the insides are visible, luckily didn't go any further like the old one hanging around... but further prevention it was now located higher and away from the dog. Near the entrance of my home there's a two-way coaxial splitter that are installed by the tech when I had a problem about slow internet before. It was way before Maria, like 2015 or 2016. I don't know the capacity of the splitter for now. I tried: Turning off WMM Using a DNS address Restarting the gateway Removing and insert the coax into the gateway Changing to non-auto channel selection Setting a multicast rate Setting Beacon Interval to 50 instead of 100 Turing on WMM and giving priorities for certain applications (for games in my case) Port forwarding to that game Disabling the firewall Enabling UPnP Switching to 40MHz Disabling WPS (while maintaining WPS2 +AES encryption) Reset the gateway to the factory default state ...and none of them work at all. What you think what's causing the problem? removed all instances of the mac address from this post --state

Hi all! New here but I'm getting tired of googling my issue to no help. I recently purchased the SB8200 and had it activated to Comcasts Pro Extreme 400 package. Although their website calls it Gigabit Tier. There's some confusion there but either way ... Booting this modem is successful in terms of it acquiring upstream and downstream bonding channels. However the downstream LED never turns from green to blue indicating DOCSIS 3.1. After a fun journey to get the modems status page to load (had my LAN set to 192.168.0.x, changed it to 192.168.1.x to get 192.168.100.1 to work) ... this is what my event log looks like shortly after booting and everything is connected: 1-1-1970, 0:0:45 Notice(6) "Honoring MDD; IP provisioning mode = IPv6" 1-1-1970, 0:0:38 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:01:5c:85:d0:68;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:1:55 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:01:5c:85:d0:68;CM-QOS=1.1;CM-VER=3.1;" 1-1-1970, 0:1:51 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" That's it and the logs been quiet since. I get the following after each reboot and nothing more. Things seem a little out of order but this appears to start logging before the modem acquires TOD. Now this might not mean anything or means everything. I've been trying to figure out more on the CMTS and came across that its of a Cadant Inc being. Don't know what version and if it's really capable / ready for DOCSIS 3.1. After speaking with Comcast support they all say I should be getting DOCSIS 3.1 in my area because I have the Gigabit tier. But on the other hand it sounds like they really don't know what I'm talking about. Does that 'CM-VER=3.1' on the tail end mean anything? When I've tried googling this and it seems like everyone else's says 'CM-VER=3.0' Here is a snap shot of my signals incase anyone was wonder: Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables 24 Locked QAM256 549000000 Hz 4.5 dBmV 41.7 dB 0 0 1 Locked QAM256 405000000 Hz 7.5 dBmV 43.1 dB 0 0 2 Locked QAM256 411000000 Hz 7.3 dBmV 42.9 dB 0 0 3 Locked QAM256 417000000 Hz 7.1 dBmV 42.9 dB 0 0 4 Locked QAM256 423000000 Hz 7.0 dBmV 42.6 dB 0 0 5 Locked QAM256 429000000 Hz 7.2 dBmV 42.9 dB 0 0 6 Locked QAM256 435000000 Hz 7.1 dBmV 42.8 dB 0 0 7 Locked QAM256 441000000 Hz 7.1 dBmV 42.8 dB 0 0 8 Locked QAM256 447000000 Hz 6.9 dBmV 42.5 dB 0 0 9 Locked QAM256 453000000 Hz 6.8 dBmV 42.8 dB 0 0 10 Locked QAM256 459000000 Hz 6.4 dBmV 42.8 dB 0 0 11 Locked QAM256 465000000 Hz 6.1 dBmV 42.5 dB 0 0 12 Locked QAM256 471000000 Hz 5.6 dBmV 42.4 dB 0 0 13 Locked QAM256 477000000 Hz 5.4 dBmV 42.5 dB 0 0 14 Locked QAM256 483000000 Hz 4.9 dBmV 42.4 dB 0 0 15 Locked QAM256 489000000 Hz 4.6 dBmV 42.2 dB 0 0 16 Locked QAM256 495000000 Hz 4.3 dBmV 42.2 dB 0 0 17 Locked QAM256 507000000 Hz 4.1 dBmV 42.1 dB 0 0 18 Locked QAM256 513000000 Hz 4.1 dBmV 42.1 dB 0 0 19 Locked QAM256 519000000 Hz 4.2 dBmV 41.9 dB 0 0 20 Locked QAM256 525000000 Hz 4.2 dBmV 42.1 dB 0 0 21 Locked QAM256 531000000 Hz 4.3 dBmV 42.0 dB 0 0 22 Locked QAM256 537000000 Hz 4.4 dBmV 41.9 dB 0 0 23 Locked QAM256 543000000 Hz 4.4 dBmV 41.7 dB 0 0 Upstream Bonded Channels Channel Channel ID Lock Status US Channel Type Frequency Width Power 1 11 Locked SC-QAM 23700000 Hz 6400000 Hz 42.3 dBmV 2 9 Locked SC-QAM 36500000 Hz 6400000 Hz 42.0 dBmV 3 10 Locked SC-QAM 30100000 Hz 6400000 Hz 42.5 dBmV 4 12 Locked SC-QAM 17300000 Hz 6400000 Hz 42.0 dBmV That's my story. Anyone have a clue?

anyone here know the latest firmware for the Sb6183? was looking online and couldn't find it. the arris modems firmware isnt just a v1.06 or something they are long numerical and alphanumerical codes..

Does the TM1602AP2 have the Puma or broadcom chipset?

I bought my own modem and then discovered I now have an IPv6, globally unique IP Address. How can I revert back to IPv4, and also is it possible to force Spectrum into giving me a new IP Address every "x" months or so. Not a spammer, but the idea of having years of posts and online site visits etc... permanently recorded and referenced to a globally unique ID number is very disconcerting to me.

I recently purchased a Arris SB8200 Cable Modem. I was able to get it registered and activated on my comcast account without any trouble. Comcast has verfified that everything indicates no issues on their end when viewing this modem on my account. However, my internet connection keeps randomly dropping. I have tried resetting the modem and that fixes this for a short time, but then the connection drops again. I am using a Netgear R7000 router with this modem. I never had one issue when using my previous SB6183 modem. Could this be a faulty modem or a problem with my modem dropping back to Docsis 3.0. I am on the pro performance tier (100/5). Any ideas would be great.

I have the arris surf board sbg6700-ac and use it as a modem. My router is the netgear orbi. I was trying to set up a server for a game. The port forwarding wouldn’t work so I tried to put the surfboard on bridge mode. Now I can’t get internet even if I plug a laptop directly into the modem. This means that I can’t get into the modem settings to change it back to how it was before. Please help as people need to use the internet and I’ve tried everything I know.

I have a new CODA-4582U modem and Rogers isn't convinced that there's an issue with my internet despite it dropping/ slowing down drastically so I would a way to graph the signal over time. Is there a way to do that?

I've had my SB8200 about a month with Cox ISP and have a recurring problem where IPv4 stops working but IPv6 is fine. I can only access websites that have AAAA records in DNS with an IPv6 address. Restarting modem fixes issue - restarting my Netgear Orbi router doesn't help. Prior to SB8200 I had a Netgear CM600 and never had this issue. I don't have an OFDM channel yet, my SB8200 modem is connected on 32 downstream and 4 upstream channels. I telnetted into my Netgear Orbi router to do some troubleshooting. Everything looks good root@RBR50:/# route -nKernel IP routing tableDestination Gateway Genmask Flags Metric Ref Use Iface0.0.0.0 174.66.192.1 0.0.0.0 UG 0 0 0 brwan174.66.192.0 0.0.0.0 255.255.248.0 U 0 0 0 brwan192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0239.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 br0 Redacted my specific IP (xxx) root@RBR50:/# ip route default via 174.66.192.1 dev brwan 174.66.192.0/21 dev brwan proto kernel scope link src 174.66.196.xxx192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.1 239.0.0.0/8 dev br0 scope link root@RBR50:/# ip -6 route 2600:8806:8200:1b::/64 dev br0 proto kernel metric 256 2600:8806:9f00:200:2889:2343:2702:592b dev brwan proto kernel metric 256 fe80::/64 dev eth1 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 dev ath0 proto kernel metric 256 fe80::/64 dev ath1 proto kernel metric 256 fe80::/64 dev ath2 proto kernel metric 256 fe80::/64 dev ath01 proto kernel metric 256 fe80::/64 dev brwan proto kernel metric 256 fe80::/64 dev br0 proto kernel metric 256 default via fe80::6600:f1ff:fe3f:efd9 dev brwan metric 1 root@RBR50:/# cat /etc/resolv.conf nameserver 68.105.28.11nameserver 68.105.29.11nameserver 68.105.28.12nameserver 2001:578:3f::30 nameserver 2001:578:3f:1::30 Did some ping tests. I cannot ping default gateway 174.66.192.1 from my computers or from the router itself. I can ping IPv6 hosts out on the internet just fine, can't ping IPv4 hosts: root@RBR50:/bin# ping6 e16.ycpi.nya.yahoo.comPING e16.ycpi.nya.yahoo.com (2001:4998:1c:803::2003): 56 data bytes64 bytes from 2001:4998:1c:803::2003: icmp6_seq=0 ttl=58 time=33.9 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=1 ttl=58 time=41.1 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=2 ttl=58 time=33.8 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=3 ttl=58 time=33.4 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=4 ttl=58 time=33.5 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=5 ttl=58 time=33.2 ms^C--- e16.ycpi.nya.yahoo.com ping statistics ---6 packets transmitted, 6 packets received, 0% packet lossround-trip min/avg/max = 33.2/34.8/41.1 ms root@RBR50:/bin# ping e16.ycpi.nya.yahoo.com PING e16.ycpi.nya.yahoo.com (69.147.82.219): 56 data bytes The IPv4 ping test seems to be resolving via ipv6 resolvers based on how long it took to resolve. I feel like it timed out on the three v4 resolvers in /etc/resolv.conf before hitting ipv6 resolvers and getting a v4 IP address back from v6 resolver. So at this point, I restarted my router. Didn't help anything. GUI said it couldn't connect to internet. So I restarted my modem, and then it worked! Routing tables on the router and resolv.config looked identical after restarting modem - I received same IP address from Cox. I've had this particular IPv4/IPV6 issue happen about 4 times over course of ownership of this modem (so weekly). Each time, restarted modem fixes. This last time I didn't even both restarting router. I wonder if this is related to this other problem I have with SB8200 where I can't access admin page: https://www.dslreports.com/forum/r31725961-Modem-Admin-page-blocked-on-my-SB8200 I called ARRIS first, they said there is nothing to configure on modem so nothing to do other than call Cox. Called Cox, they didn't really have any ideas either. Said call next time it happens. I found similar complaints on Comcast forum (I have Cox service) from both users of the SB8200 and MB8600 (same chipset): http://forums.xfinity.com/t5/Your-Home-Network/Frequently-loosing-IPv4-while-IPv6-is-fine/td-p/2923874 http://forums.xfinity.com/t5/Your-Home-Network/Re-Frequently-loosing-IPv4-while-IPv6-is-fine/td-p/3016461 http://forums.xfinity.com/t5/Your-Home-Network/Motorola-MB8600-frequently-loses-IPv4-connection-but-IPv6-is-ok/td-p/2996458 Anyone else experiencing this?

I have a SB6141 I purchased in November 2015. It has performed flawlessly since that time. Recently I've been experience sporadic disconnects and reconnects throughout the day and night. My ISP (Suddenlink) has not been experience any issues so I know it's not on their end. My cable drop to the modem comes in directly through no splitters. I'm just wondering if the cable modem is going bad but it's not even three years old. I've posted some screen shots of my cable modem settings. I really don't want to call Suddenlink to have someone come out since they charge $120 to just step in my house. Thanks for any help.

On the Xfinity site, it states that the wired download speed is up to 373Mbps. https://mydeviceinfo.xfinity.com/device/arris-sb6183-417. But on the Arris site (and elsewhere) it states that the download speed is up to 686Mbps. http://www.arris.com/surfboard/products/cable-modems/sb6183/ Why the discrepancy?

I bought my own modem and then discovered I now have an IPv6, globally unique IP Address. How can I revert back to IPv4, and also is it possible to force Spectrum into giving me a new IP Address every "x" months or so. Not a spammer, but the idea of having years of posts and online site visits etc... permanently recorded and referenced to a globally unique ID number is very disconcerting to me.

Just thought some of you would find it interesting. My SB6141 was resetting a lot and the internet was dropping (lots of T3/T4 errors). Seemed a bit odd knowing they just re ran the main lines in the yards, and the hardware in the boxes out in the yard, and in my case they had to replace the line from the box through the yard to the house. Internet was pretty solid for a few months after that, but lately has gone to crap. Wasn't certain it was the modem but went ahead and bought an SB6183. My 7 year old loves taking things apart, so we took apart the old modem - most of the capacitors on the board were bulged/leaking at the top. Definitely was time for an upgrade.

Comcast replaced my Head-In line which got rid of all my line quality related errors, but I'm still getting very slow web page loading; whereas, it takes a minimum of 15 seconds to one minute just to get to a website, then up to four minutes to fully load it. I removed my router and connected directly to the modem, but I still have the slow loading. I have Comcast 1Gb plan and I get a constant 890 down / 42 up speeds. I tried to update the modem firmware, but was told that Comcast handles that. I don't get any buffering errors when watching on-line videos, just the very slow and extremely annoying page loading and surfing. My modem is still under warranty....should I take it back? Any other suggestions?

I recently purchased a Arris SB8200 Cable Modem. I was able to get it registered and activated on my comcast account without any trouble. Comcast has verfified that everything indicates no issues on their end when viewing this modem on my account. However, my internet connection keeps randomly dropping. I have tried resetting the modem and that fixes this for a short time, but then the connection drops again. I am using a Netgear R7000 router with this modem. I never had one issue when using my previous SB6183 modem. Could this be a faulty modem or a problem with my modem dropping back to Docsis 3.0. I am on the pro performance tier (100/5). Any ideas would be great.

I've had my SB8200 about a month with Cox ISP and have a recurring problem where IPv4 stops working but IPv6 is fine. I can only access websites that have AAAA records in DNS with an IPv6 address. Restarting modem fixes issue - restarting my Netgear Orbi router doesn't help. Prior to SB8200 I had a Netgear CM600 and never had this issue. I don't have an OFDM channel yet, my SB8200 modem is connected on 32 downstream and 4 upstream channels. I telnetted into my Netgear Orbi router to do some troubleshooting. Everything looks good root@RBR50:/# route -nKernel IP routing tableDestination Gateway Genmask Flags Metric Ref Use Iface0.0.0.0 174.66.192.1 0.0.0.0 UG 0 0 0 brwan174.66.192.0 0.0.0.0 255.255.248.0 U 0 0 0 brwan192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0239.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 br0 Redacted my specific IP (xxx) root@RBR50:/# ip route default via 174.66.192.1 dev brwan 174.66.192.0/21 dev brwan proto kernel scope link src 174.66.196.xxx192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.1 239.0.0.0/8 dev br0 scope link root@RBR50:/# ip -6 route 2600:8806:8200:1b::/64 dev br0 proto kernel metric 256 2600:8806:9f00:200:2889:2343:2702:592b dev brwan proto kernel metric 256 fe80::/64 dev eth1 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 dev ath0 proto kernel metric 256 fe80::/64 dev ath1 proto kernel metric 256 fe80::/64 dev ath2 proto kernel metric 256 fe80::/64 dev ath01 proto kernel metric 256 fe80::/64 dev brwan proto kernel metric 256 fe80::/64 dev br0 proto kernel metric 256 default via fe80::6600:f1ff:fe3f:efd9 dev brwan metric 1 root@RBR50:/# cat /etc/resolv.conf nameserver 68.105.28.11nameserver 68.105.29.11nameserver 68.105.28.12nameserver 2001:578:3f::30 nameserver 2001:578:3f:1::30 Did some ping tests. I cannot ping default gateway 174.66.192.1 from my computers or from the router itself. I can ping IPv6 hosts out on the internet just fine, can't ping IPv4 hosts: root@RBR50:/bin# ping6 e16.ycpi.nya.yahoo.comPING e16.ycpi.nya.yahoo.com (2001:4998:1c:803::2003): 56 data bytes64 bytes from 2001:4998:1c:803::2003: icmp6_seq=0 ttl=58 time=33.9 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=1 ttl=58 time=41.1 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=2 ttl=58 time=33.8 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=3 ttl=58 time=33.4 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=4 ttl=58 time=33.5 ms64 bytes from 2001:4998:1c:803::2003: icmp6_seq=5 ttl=58 time=33.2 ms^C--- e16.ycpi.nya.yahoo.com ping statistics ---6 packets transmitted, 6 packets received, 0% packet lossround-trip min/avg/max = 33.2/34.8/41.1 ms root@RBR50:/bin# ping e16.ycpi.nya.yahoo.com PING e16.ycpi.nya.yahoo.com (69.147.82.219): 56 data bytes The IPv4 ping test seems to be resolving via ipv6 resolvers based on how long it took to resolve. I feel like it timed out on the three v4 resolvers in /etc/resolv.conf before hitting ipv6 resolvers and getting a v4 IP address back from v6 resolver. So at this point, I restarted my router. Didn't help anything. GUI said it couldn't connect to internet. So I restarted my modem, and then it worked! Routing tables on the router and resolv.config looked identical after restarting modem - I received same IP address from Cox. I've had this particular IPv4/IPV6 issue happen about 4 times over course of ownership of this modem (so weekly). Each time, restarted modem fixes. This last time I didn't even both restarting router. I wonder if this is related to this other problem I have with SB8200 where I can't access admin page: https://www.dslreports.com/forum/r31725961-Modem-Admin-page-blocked-on-my-SB8200 I called ARRIS first, they said there is nothing to configure on modem so nothing to do other than call Cox. Called Cox, they didn't really have any ideas either. Said call next time it happens. I found similar complaints on Comcast forum (I have Cox service) from both users of the SB8200 and MB8600 (same chipset): http://forums.xfinity.com/t5/Your-Home-Network/Frequently-loosing-IPv4-while-IPv6-is-fine/td-p/2923874 http://forums.xfinity.com/t5/Your-Home-Network/Re-Frequently-loosing-IPv4-while-IPv6-is-fine/td-p/3016461 http://forums.xfinity.com/t5/Your-Home-Network/Motorola-MB8600-frequently-loses-IPv4-connection-but-IPv6-is-ok/td-p/2996458 Anyone else experiencing this?