[BUG REPORT] RBRE960 Stops Responding to ARP Requests from WiFi Clients

Question

**Device:** Netgear Orbi RBRE960**Firmware:** V7.2.8.2**Mode:** Router Mode (no satellites)&nbsp;---&nbsp;**Summary**&nbsp;The RBRE960 intermittently stops responding to ARP requests from associated WiFi clients. Affected clients retain a valid DHCP lease and remain 802.11 associated, but lose all network connectivity because the router silently stops answering ARP broadcasts. The issue affects multiple device types and operating systems simultaneously and has been reproducible for over a year.&nbsp;---&nbsp;**Affected Devices**- Windows 11 laptop (Intel AX211 WiFi 6E)- Android Samsung Galaxy phones- Linux desktop- Most severely impacts WiFi 6E devices, but not exclusively- Wired devices are never affected&nbsp;---&nbsp;**Symptoms**- Device shows "Secured, No Internet" on WiFi- Device has a valid 192.168.x.x DHCP address- Device cannot ping the gateway- ARP cache on affected device is completely empty for all unicast entries including the gateway- Disconnecting and reconnecting WiFi immediately resolves the issue- Multiple devices can be affected simultaneously&nbsp;---&nbsp;**Root Cause Identified via Packet Capture**&nbsp;I captured traffic using tshark during a failure event. I am not comfortable sharing raw pcap files publicly. Below is sanitized tshark output limited to ARP traffic only, with MAC addresses anonymized.&nbsp;**Capture 1 — During failure, before any fix applied:**```1 0.000000000 [client-wifi-adapter] → Broadcast ARP Who has 192.168.1.1? Tell 192.168.1.32[repeats 24 times over 23+ seconds][zero ARP replies received from router at any point]```**The Orbi sends zero ARP replies across the entire 23+ second capture.**&nbsp;**Capture 2 — During static ARP entry injection:**```1 0.000000000 [client-wifi-adapter] → Broadcast ARP Who has 192.168.1.1? Tell 192.168.1.32[repeats 3 times then stops after static entry injected]```Immediately after the static ARP entry was injected for the gateway, ARP broadcasts ceased and full bidirectional traffic (DNS, TCP, TLS) resumed within milliseconds — confirming ARP resolution was the sole point of failure.&nbsp;---&nbsp;**ARP Table During Failure**&nbsp;The following shows the ARP table on the affected device during the failure. Note the complete absence of any unicast entry for the gateway:&nbsp;```Interface: 192.168.1.32Internet Address Physical Address Type224.0.0.22 01-00-5e-00-00-16 static224.0.0.251 01-00-5e-00-00-fb static239.255.255.250 01-00-5e-7f-ff-fa static255.255.255.255 ff-ff-ff-ff-ff-ff static```&nbsp;After static ARP entry injected and connectivity restored:```Interface: 192.168.1.32Internet Address Physical Address Type192.168.1.1 [router-mac] static224.0.0.22 01-00-5e-00-00-16 static224.0.0.251 01-00-5e-00-00-fb static239.255.255.250 01-00-5e-7f-ff-fa static255.255.255.255 ff-ff-ff-ff-ff-ff static```&nbsp;---&nbsp;**Network Configuration**- DHCP pool: 192.168.1.2 - 192.168.1.254- Active devices: ~8 (well within pool)- IPv6: Disabled- UPnP: Enabled- No satellites&nbsp;---&nbsp;**What This Is Not**- Not DHCP exhaustion (253 address pool, 8 active devices)- Not IPv6 conflict (disabled)- Not a client driver issue (affects Windows, Android, and Linux simultaneously)- Not a signal or band issue (clients remain 802.11 associated throughout the failure)- Not ISP related (wired devices are never affected)- Not a single device issue (multiple devices affected simultaneously)&nbsp;---&nbsp;**Workaround**Manually injecting a static ARP entry for the gateway on each affected device restores connectivity without requiring a reconnect:```netsh interface ipv4 add neighbors "Wi-Fi" 192.168.1.1 [router-mac]```This is not a viable long term solution, particularly for Android devices without root access.&nbsp;---&nbsp;**Request**This is a fundamental Layer 2 failure — a router that does not respond to ARP requests from its own associated WiFi clients is non-functional for those clients. Please escalate to the firmware team.

FURRYe38 · Answer

Brand and model # of the ethernet and wifi adapters that are connecting to the system?
&nbsp;
Same thing happens with newer FW?&nbsp;
New - Orbi RBK750/850/860/960 Series Firmware Version 7.2.8.5 Released | NETGEAR Communities
Just becuase it's not seen on the RBRs web page, doesn't mean you have the latest. NG sometimes only pushes to small batches of systems or if your system isn't registered in there update database, then your system may not see anything they post or push. I recommend always looking at NGs support download web page or check here in the forums for FW updates.&nbsp;
&nbsp;
I've had my 963 series online this past year. No issues seen with v7.2.8.5 loaded on it.&nbsp;
**Network Configuration**
- DHCP pool: 192.168.0.100 - 192.168.0.200
- Active devices: ~50 (well within pool) a few outside of the pool using static IP configurations.
- IPv6: Disabled
- UPnP: Enabled
- 2 satellites ethernet connected
&nbsp;
&nbsp;

CrimpOn · Answer

Thanks for posting this.&nbsp; It typically helps to validate the any situation exists with the current firmware version (i.e. 7.2.8.5).
Look forward to seeing information after the system is updated to the current firmware.
&nbsp;

SkylerPeterson · Answer

There is no update on the Netgear Firmware update page, see below. I will manually pull it, update and see if it persists. There are a number of devices impacted, laptops and cell phones are the most prevalent. One of the WiFi adapters is an Intel Wi-Fi 6E AX211 160MHz. Laptop is running Windows 11.

Status:

	Model Name	Device Name	Current Firmware Version	Status
Router	RBRE960	---	V7.2.8.2	No New Firmware Available

SkylerPeterson · Answer

I am now update to firmware version V7.2.8.5_5.1.21. I will do a full power cycle of my modem and router and report back if issue continues.

SkylerPeterson · Answer

I have completed the update to firmware version V7.2.8.5_5.1.21. I have also done a full restart of my modem and router. I will post again if/when the issue persists.

Forum Discussion

[BUG REPORT] RBRE960 Stops Responding to ARP Requests from WiFi Clients

10 Replies