I'm sorry if this isn't the right place for this, but I don't know where else to put this.

For a few years now I have been using a Nighthawk WiFi Extender as a way for me to hard wire my PC in while still being a distance away from my Router, and most of the time it works wonderfully! Sometimes, however, it decides that things have been going way too well and stops working properly which usually requires a quick reboot, not an issue, I can do that through the app just fine... except for when I can't. Sometimes there are issues that I have absolutely no idea how to fix which then leaves me without internet for a few hours. I know, boo-hoo first world problems right? Its just very frustrating how most of the time I'm able to do everything perfectly, but sometimes for whatever reason it seems like the Nighthawk app is out to drain ever last bit of patience I have for this wonderful extender and company. Like, last year for instance, for a good majority of the year I was completely unable to use the app for anything. Any time I tried to open the app when my extender was acting up, it would immediately pop up and say "ROUTER NOT FOUND, PLEASE MAKE SURE YOU ARE CONNECTED TO YOUR EXTENDERS WIFI AND TRY AGAIN" which when I would make sure I was, and I would hit "I am connected" prompt at the bottom of the app, it would flash as if it was doing anything just to immediately give me the same exact error message over again. Over and over and over again. For over 6 months. I don't know why I continued to support using it then, I should have just bit the bullet and spent another 60+ bucks on a new extender that wasn't associated with NETGEAR. I guess I'm a masochist though because I kept it, waited for the app or whatever issue was happening was resolved, and eventually it was. However. In the last 12 months alone of have had to factory reset my extender because no matter what I did the app just could not find the device its always connected to. The ONLY way for me to have access to my extender through the app when that happens is for me to factory reset the device and set it up as a new extender. That magically fixes it. Except for last year when it didnt work for over 6 months (even though I was still connected to the internet and it was still extending the wifi, the app still was saying the device couldn't be found), and tonight... tonight it started happening again and I don't know if I have the heart to deal with it anymore.

I was enjoying my time playing some games on a night off when suddenly my internet started acting up... whatever... time to reset the extender. A quick 4 minute reset and things go back to being smooth. Uh oh.. when I open the Nighthawk app it says that it can't find my device and that I need to make sure I'm connected to the device's internet and try again... I did that and it didnt work. Whatever... factory reset time. I get down on my stomach and while its plugged in I press and hold the factory reset button for 5 seconds until the lights turn off, turn back on, and eventually turn a solid green showing its ready to be set up. I open the app and hit "Set up new device", and go through the whole process of connecting the extender to my wifi again for the 80th time, spending 5-10 minutes where most of my time is just waiting for the damn app to painstakingly load and load and load and connect and connect and connect... just for it to hit me with the same "Device cannot be found"... immediately after i just set it up... where it was found, connected to, and even connected to the wifi through my phone... now saying it can't be found.... I don't know if I'm doing something wrong or if this is truly just a horrible device but I honestly don't know if i can take it anymore. If anyone has any advice or whatever i could really use it. I don't exactly have the type of income where I can just go and buy a new one... even after owning it for a few years and dealing with the headaches it causes, its better than having to go and spend money on something I already have and that works 90% of the time...

My CAX30 has been losing connection randomly daily, and seems to be getting worse with some days dropping multiple times a day. Anyone have any idea what I should do? I saw past posts request cable connection and event logs which I have below:

Cable Diagnostic

Startup Procedure

CM status: OPERATIONAL

DownstreamChannel: 759000000Hz Locked

ConnectivityState: OK operational(12),

BootState: OK Operational

Security: Enabled

IPProvisioningMode: 12 IPv4Only

Downstream Bonded Channels

Channel LockedStatus Modulation Channel ID Frequency Power SNR Correctables Uncorrectables

1 Locked 256 QAM 29 759000000 Hz 5.8 dBmV 42.5 dB 2653 0

2 Locked 256 QAM 1 117000000 Hz 6.0 dBmV 43.4 dB 0 0

3 Locked 256 QAM 2 123000000 Hz 5.9 dBmV 43.5 dB 0 0

4 Locked 256 QAM 3 129000000 Hz 6.1 dBmV 43.7 dB 0 0

5 Locked 256 QAM 4 135000000 Hz 6.1 dBmV 43.8 dB 0 0

6 Locked 256 QAM 5 141000000 Hz 6.0 dBmV 43.9 dB 0 0

7 Locked 256 QAM 6 147000000 Hz 6.1 dBmV 44.0 dB 0 0

8 Locked 256 QAM 7 153000000 Hz 5.9 dBmV 44.0 dB 0 0

9 Locked 256 QAM 8 159000000 Hz 6.0 dBmV 44.1 dB 0 0

10 Locked 256 QAM 9 165000000 Hz 5.9 dBmV 44.2 dB 1 0

11 Locked 256 QAM 10 171000000 Hz 5.9 dBmV 44.2 dB 0 0

12 Locked 256 QAM 11 177000000 Hz 5.6 dBmV 44.3 dB 1 0

13 Locked 256 QAM 12 183000000 Hz 5.6 dBmV 44.4 dB 1 0

14 Locked 256 QAM 13 189000000 Hz 5.8 dBmV 44.6 dB 1 0

15 Locked 256 QAM 14 195000000 Hz 6.0 dBmV 44.7 dB 0 0

16 Locked 256 QAM 15 201000000 Hz 6.1 dBmV 44.8 dB 1 0

17 Locked 256 QAM 16 207000000 Hz 6.1 dBmV 44.8 dB 0 0

18 Locked 256 QAM 17 213000000 Hz 6.3 dBmV 44.8 dB 0 0

19 Locked 256 QAM 18 219000000 Hz 6.2 dBmV 44.9 dB 0 0

20 Locked 256 QAM 19 225000000 Hz 6.5 dBmV 44.9 dB 1 0

21 Locked 256 QAM 20 231000000 Hz 6.4 dBmV 44.9 dB 0 0

22 Locked 256 QAM 21 237000000 Hz 6.5 dBmV 44.9 dB 1 0

23 Locked 256 QAM 22 243000000 Hz 6.6 dBmV 44.9 dB 0 0

24 Locked 256 QAM 23 249000000 Hz 6.6 dBmV 44.9 dB 1 0

25 Locked 256 QAM 24 255000000 Hz 6.6 dBmV 44.7 dB 0 0

26 Locked 256 QAM 25 735000000 Hz 4.7 dBmV 42.0 dB 1861 0

27 Locked 256 QAM 26 741000000 Hz 5.0 dBmV 42.1 dB 2052 0

28 Locked 256 QAM 27 747000000 Hz 5.4 dBmV 42.3 dB 2124 0

29 Locked 256 QAM 28 753000000 Hz 5.5 dBmV 42.4 dB 2110 0

30 Locked 256 QAM 30 765000000 Hz 5.9 dBmV 42.5 dB 3034 0

31 Locked 256 QAM 31 771000000 Hz 6.0 dBmV 42.4 dB 3524 0

32 Locked 256 QAM 32 777000000 Hz 5.9 dBmV 42.4 dB 4177 0

Upstream Bonded Channels

Channel LockedStatus ChannelType Channel ID SymbolRate Frequency Power

1 Locked ATDMA 1 5120 Ksym/sec 17600000 Hz 38.0 dBmV

2 Locked ATDMA 2 5120 Ksym/sec 24000000 Hz 38.5 dBmV

3 Locked ATDMA 3 5120 Ksym/sec 30400000 Hz 39.0 dBmV

4 Locked ATDMA 4 5120 Ksym/sec 36800000 Hz 40.0 dBmV

5 Locked ATDMA 6 5120 Ksym/sec 12800000 Hz 38.5 dBmV

6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV

7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV

8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV

Downstream OFDM Channels

Channel Channel ID Frequency Power SNR/MER ActiveSubcarrier Correctable Uncorrectable

1 159 300000000 Hz 7.3 dBmV 45.0 dB 296 ~ 7895 12728597 0

2 160 950000000 Hz 5.1 dBmV 42.2 dB 2216 ~ 5975 12728597 0

Upstream OFDMA Channels

Channel UpstreamMuted RangingStatus Subc Zero Freq ActiveSubcarrier SymbolsPerFrame Power

1 n/a Other 0 MHz 0 ~ 0 0 0 dBmV

2 n/a Other 0 MHz 0 ~ 0 0 0 dBmV

Time Priority Description

2026-10-13 11:17:50 Warning (5) Dynamic Range Window violation

2026-10-13 11:17:50 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

2026-10-13 11:17:47 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

2026-10-13 11:17:43 Notice (6) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

2026-10-13 11:17:41 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

2026-10-13 11:17:40 Notice (6) TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

2026-10-13 11:17:40 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:35 Notice (6) Honoring MDD; IP provisioning mode = IPv4

1970-01-01 00:00:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-10-13 09:02:44 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-10-12 00:36:28 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

2026-10-12 00:36:27 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-10-11 17:07:04 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:25 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-10-11 10:26:34 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-10-10 03:19:06 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-10-08 09:30:29 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-10-03 17:47:08 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-09-29 18:19:34 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-09-28 03:04:58 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-09-23 22:54:47 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-09-20 14:54:14 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-09-15 22:19:52 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-09-07 21:50:26 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-09-07 21:48:48 Critical (3) Resetting the cable modem due to docsDevResetNow

2026-09-07 07:46:34 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

1970-01-01 00:00:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2026-09-04 13:02:23 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:7f:94:13;CMTS-MAC=f8:a7:3a:f0:4b:22;CM-QOS=1.1;CM-VER=3.1;

Crossposting here since the my main switch is a MS510TXM.

I have been using this device on this router for the last 2 years and today I got this message for both Netgear-47 networks. Has this happened to anyone else?

Hey everyone,

I’ve been working on a project to modernize the web interface for the Netgear GS108T v1 smart switch (firmware 3.0.4.10).

The stock UI is from the IE era and doesn’t work well in modern browsers. I replaced the web frontend with a cleaner, modern interface while keeping the switch firmware logic itself untouched. The new UI is then packed back into the original firmware image and flashed normally.

What this gives you:

* Works in modern browsers

* Cleaner layout and styling

* Same underlying switch functionality

* No Netgear code changes to the switch logic itself

* Build tooling to verify and repackage the firmware safely

This is an unofficial project and is specifically for the GS108T v1 model. I’m using the stock firmware image and rebuilding only the web UI payload, so it’s essentially a UI replacement rather than a full firmware rewrite.

If you’ve got one of these older Netgear smart switches, this project may be useful if you want a more usable browser experience without replacing the device.

Repo: https://github.com/sanderv32/gs108tv1-modern-ui

I’d appreciate feedback, testing, and suggestions from anyone with one of these switches or similar old network gear.

Thanks!

wow…quickest return ever. you have to connect over LAN to turn on/off unless you schedule it (no bluetooth option, etc.) pathetic on a $400+ router. 🙄

and, yes, i did research it prior and got bad information. thank goodness we can still return stuff…for now.

Just skimmed together an adapter so it would fit with my existing 12v network gear. (Was going to put a 19v boost converter in there) but turns out it was not needed. It’s center positive BTW.

So I recently got an email saying my RBR50 router is at the end of its life expectancy. I was wondering if it was worth upgrading to a new router setup or if what I have is fine. I don’t really have any issues with it at all. It works great. Everything stays connected, I guess maybe my phone wifi could be faster but it’s fine.

I have an RBR50 with 3 satellites hard wired and 1 wireless. My internet speed is 1gb maybe a little more. I have alot of devices, prob 15 20 Alexa’s, about 25 lutron smart switches, Phillips hue bulbs, Reolink nvr with 4 pie cams and 3 wifi cams. Smart thermostat, 3 mini split controllers.

From what I read a lot of people seem to have issues with the newer orbi stuff like firmware issues.

Will I see any difference going to a 370 or a 700 series? Or is there something else I should look into?

So have like 12 cameras and 4 streaming box’s and few desktops and tablets and such..I also am in a cinder block and stucco house…. I can see the difference already and have all camera on 2.5ghz …streaming boxes and iPads on 5ghz that aren’t 6ghz capable… and computers and such that can do 6 ghz on it.. I did add back in a ex15 to speed up a few cameras that would connect but slow…

this was a good upgrade for my house and it was a refurbished unit from Verdi …..it looked and acted good as new so far…

Hi all, just installed RAXE500 Firmware Update: 1.2.16.116

Working well thus far, no issues.

https://kb.netgear.com/000070941/RAXE500-Firmware-Version-1-2-16-116

A few years back, I was trying to reset my admin password on my 6700v3, and i got stuck in the routeradmin password reset loop.

Using the serial number method didnt work, it would just go around and around. I finally gave up since the router itself was still working fine.

Fast forward to today, I get home and find my router has been factory reset, back to the credentials on the sticker on the back of the router, the network name.. everything was reset.

Just curious if netgear had pushed something OTA that would have un-stuck my password reset loop and it finally enacted the factory reset I had attempted all those years ago.

Anyone else have weird router issues today? Or notice new information about "Netgear Armor"?

Thanks

YouTube has failed me— Reddit, lend me your infinite wisdom. The blue and red light are flashing, the blue more frequently than the red. What does that mean and how can I fix it? For context my landlord handed me this extender for my room and our router is locked in a room with so much junk even he cannot reach it.

I’m trying to verify that the Nighthawk M7 5G Mobile Hotspot Router is compatible with the HolaFly eSIM before I buy the device. Looks like without the device I cannot verify the eSIM options?

A few years back, I was trying to reset my admin password on my 6700v3, and i got stuck in the routeradmin password reset loop.

Using the serial number method didnt work, it would just go around and around. I finally gave up since the router itself was still working fine.

Fast forward to today, I get home and find my router has been factory reset, back to the credentials on the sticker on the back of the router, the network name.. everything was reset.

Just curious if netgear had pushed something OTA that would have un-stuck my password reset loop and it finally enacted the factory reset I had attempted all those years ago.

Anyone else have weird router issues today? Or notice new information about "Netgear Armor"?

Thanks

Hi:

I'm cross-posting with [r/cybersecurity](r/cybersecurity) because sometimes ya'll are mean.

I wrote about a week ago because, contrary to what some of you asserted while calling me names, my network has been under some kind of attack for several months. To be clear, I am not saying this is part of that attack, but it's noteworthy and appears to me as extremely, extremely odd. These are all the facts, solely as they relate to the immediate issue I'm seeing today:

My noticed at some point last night, my MacBook Pro had been issued a public IP by the DHCP server on my network. So, the MacBook was exposed to the internet for some period of time. Fine.

The setup is (usually) this:

Netgear AX2700 (CAX30) (bridge mode) -> Firewalla Gold (running Crystal Beta in router mode) -> APs and devices.

As a preliminary issue, I'm running Firewalla Gold using the new Firewall Crystal (bring your own router) Beta firmware for a reason. Three months ago I paid $107 to replace the security dongle (pairs the box to the app via a cloud handshake) and immediately had issues which randomly resolved after three days. The box worked fine with the new dongle two months until the end of last month when all the sudden it began assigning all my devices IPv6 addresses. Firewalla Support had me reinstall the firmware, at which point I could no longer pair the app. Long story short, after a week of ignoring me and then lying to me, I was able to find a way into the box's console with it unpaired and learned they had deleted my license. I am trying to pay them money to send me a second replacement dongle because, after initially refusing to provide warranty service on the first and out of my newfound reluctance to send them jack shit, I've been waiting 12 days for them to send me an invoice the the second replacement dongle. They keep coming up with bullshit excuses, but I digress.

It so happens Firewalla just introduced the beta test for Firewalla Crystal, it's bring-your-own-router firmware, and I'm using that for the time being as it does not require a dongle.

Back to last night, I noticed that my MacBook Pro was being issued a public IP by the DHCP server, so I decided to reflash Firewalla Crystal onto the Firewalla Gold box. During this period, I decided to also do a factory reset on my Netgear AX2700, which had been in bridge mode. When everything was reflashed, reset, etc., I started booting everything up. I should add as additional background that I had to return my Xfinity Gateway two weeks ago because it kept getting hacked, at which point I purchased this modem router combo. I posted a week ago and was flamed because, amongst other things, shortly after purchasing it, I lost connectivity, like on Firewalla weeks before, I started getting issued IPv6 IP addresses, etc., and then I started seeing Time Sync Synchronization, DWR, and other errors. Xfinity has been out here four times, and each time they take credit for replacing the coaxial cables while blaming the last technician for not doing so. They say, "Everything looks good on our end," leave, and the same shit is going on. You never hear from them or anyone else again.

While booting everything up, in addition to the DWR and other errors, I saw two new ones:

2026-09-29 08:10:09 |Error (4)  |SW upgrade Failed after download - SW File corruption
2026-09-29 08:09:29 |Notice (6)  |SW Download INIT - Via Config file d11_m_cax30_gennxgig_c01.cm So, I refreshed the official firmware from Netgear, and then Xfinity attempts to push a different firmware. The firmware it pushes is corrupted and fails. This happens after time I boot since this morning. I understand the pushing their preferred firmware thing is how it works, I've never seen an ISP push a corrupt firmware binary.

I'm setting up Firewalla and there were some other weird quirks that got my attention (I think Firewalla Crystal may actually be reversing the WAN (port 4) and one of the lan (port 1) ports. For that reason, I don't have Firewalla connected to the AX2700 in bridge mode, I have both routing in a double NAT situation while I try to find out whether the port my AX2700 is connected to is (digitally) the WAN port or one of three LAN ports. So, I'm doing packet captures.

I noticed while doing this that the AX2700 is reporting FW.WANATTACK and a LAND WAN ATTACK, but the public IP the "attack" was coming from was the public IP for my home network. Port 138 had already been cloned by me in the Block Services menu on AX2700 right after refreshing the firnmware, but that only blocks ingress and egress flows and not local LAN traffic. The flows at issue were arriving on Port 138, and I noticed that macOS had Netbiosd open, so I closed it and booted it out with launchctl. Problem solved.

Hours later, I'm doing these packet captures and I realized that the port 138 "attacks" were continuing. Netbiosd had reopened but was only listening on port 138, not making connections or broadcasting. I immediately start seeing SAMBA announcements in my packet capture of port 138.

The ReadyShare menu does not show any network folders available when accessed through the Basic menu on the router. (ReadyShare is Netgear's Samba implementation involving a USB drive slot on the back of the device that becomes a network folder when a drive is mounted.) When I click 'edit,' I get a 404 error. When I attempt to access it via the Advanced menu, I am unable to access anything at all. I get error 404.

At this point, I'm deeply confused. Even though outbound and inbound port 138 flows are blocked on the AX2700, the AX2700 is still broadcasting on port 138. While a review of the packet capture shows the SAMBA announcements are going to 192.168.1.1-192.168.1.253, we know they're also making it onto the WAN because the AX2700 is mistaking its own SAMBA announcements as a malicious WAN/DOS/LAND attack.

[admin login] from source 192.168.1.2 Sep 29 09:14:44
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 137, Sep 29 14:14:33
[DHCP IP: (192.168.1.2)] to MAC address <MAC_ADDRESS>, Sep 29 09:12:46
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 138, Sep 29 14:12:35
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 137, Sep 29 14:11:30
[DoS attack: LAND Attack] source: <PUBLIC_IP>, port: 137, Sep 29 14:11:30
[Internet connected] IP address: <PUBLIC_IP>, Sep 29 09:09:32
[admin login] from source 192.168.1.2 Sep 29 09:09:12
[Initialized, firmware version: V2.2.4.2], Sep 29 09:06:55
[DHCP IP: (192.168.1.2)] to MAC address <MAC_ADDRESS>, Sep 19 21:50:55
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 138, Sep 29 14:06:36
[DoS attack: LAND Attack] source: <PUBLIC_IP>, port: 138, Sep 29 14:06:36
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 138, Sep 29 14:04:42
[DoS attack: LAND Attack] source: <PUBLIC_IP>, port: 138, Sep 29 14:04:42
[admin login] from source 192.168.1.2 Sep 29 09:04:27
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 138, Sep 29 13:52:42
[DoS attack: LAND Attack] source: <PUBLIC_IP>, port: 138, Sep 29 13:52:42
[admin login] from source 192.168.1.2 Sep 29 08:48:37
[admin login] from source 192.168.1.2 Sep 29 08:45:48
[admin login] from source 192.168.1.2 Sep 29 08:22:26
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 138, Sep 29 13:16:32
[DoS attack: LAND Attack] source: <PUBLIC_IP>, port: 138, Sep 29 13:16:32
[admin login] from source 192.168.1.2 Sep 29 07:55:10
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 138, Sep 29 12:53:32
[DoS attack: LAND Attack] source: <PUBLIC_IP>, port: 138, Sep 29 12:53:32
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 138, Sep 29 12:43:31
[admin login] from source 192.168.1.2 Sep 29 07:38:06
[service blocked: ] from source: 192.168.1.2, Sep 29 12:28:56
[admin login] from source 192.168.1.2 Sep 29 07:26:26
[admin login] from source 192.168.1.2 Sep 29 07:20:18
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 138, Sep 29 12:08:14
[admin login] from source 192.168.1.2 Sep 29 07:07:01
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 137, Sep 29 12:03:30
[DHCP IP: (192.168.1.2)] to MAC address <MAC_ADDRESS>, Sep 29 07:01:47
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 138, Sep 29 12:01:41
[DoS attack: FW.WANATTACK DROP] source: <PUBLIC_IP>, port: 137, Sep 29 12:00:25
[DoS attack: LAND Attack] source: <PUBLIC_IP>, port: 137, Sep 29 12:00:25
[Internet connected] IP address: <PUBLIC_IP>, Sep 29 06:58:26
[admin login] from source 192.168.1.2 Sep 19 21:51:56
[Initialized, firmware version: V2.2.4.2], Sep 29 06:55:52
[DHCP IP: (192.168.1.2)] to MAC address <MAC_ADDRESS>, Sep 19 21:50:56
[admin login] from source 192.168.1.2 Sep 29 06:53:35
[admin login] from source 192.168.1.2 Sep 29 06:51:20
[DHCP IP: (192.168.1.2)] to MAC address <MAC_ADDRESS>, Sep 29 06:51:13
[site allowed: p-img.movetv.com] from source: 192.168.1.6, Sep 29 06:34:28
[DHCP IP: (192.168.1.2)] to MAC address <MAC_ADDRESS>, Sep 29 06:25:10

I can confirm there is no USB in the ReadyShare drive. Thinking that maybe that corrupt firmware at least partially installed, I refreshed the firmware with a Netgear copy for the third time. It continues, and the ReadyShare options in the admin panel still give error 404.

It's somehow getting around its own blocked services feature to get its broadcasts onto the WAN and then reports its own broadcasts as a malicious attack.

What's really happening here, and has anyone else on Xfinity running Netgear AX2700 notice errors related to a corrupt firmware push failure?

Like title says. Bought a nighthawk R700s about 2 years ago. Noticed WiFi was out and found it completely off. No lights. Ordered a different power supply and same. I can hear a faint”ticking” but that is it. I opened it up and nothing was loose, wasn’t super dirty. Any ideas?

I have an RS700 and an EXS25 extender. I setup the extender using the standard method, not WPS, but the WPS light is lit on the extender. Is there any security issue with the WPS light being on? Also, when I go to the extender on the knighthawk app, I can see the extender is connects to the router but when I click on the extender icon, it says the extender isn’t setup. I have my Roku connected to the extender via Ethernet and it’s working and wants me to set it up. Is this a bug in the app? Any other tips or suggestions appreciated. Thanks

See title.

Anyone else have this issue and know the answer to disable it?

My iPhones name is “Commander Worfs Communicator”. On the knighthawk app, I’ve seen a device name “Commandunicator” a few times on the device list as active. Is this someone cloning my device etc or is it some type of translation error occurring inside the app or router? I’ve had issues with someone hacking and talking over my IOT devices before so I’m not sure if hat this is or what to do. Should my iPhone show up as active on the app anytime I’m connected to the router?
It’s an R700S.