NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dogvomit
Oct 02, 2026Aspirant
RS700 is sending BPDU packets only when in AP mode
I have an issue with RS700 where it sends BPDU packets and causes the switch port to put ports into err-disable state, but only when it is set to AP mode. Switch is required to have BPDU Guard enabled.
The RS700 has firmware 1.0.11.8, which is the latest shown on Netgear support page.
I opened a support ticket for this issue but did not receive a resolution.
Anyone familiar with this behavior? I have seen other discussions where trial firmware was provided to fix this issue on other models.
9 Replies
- dogvomitAspirant
I encountered an issue involving the Netgear RS300 operating in Access Point (AP) mode. I am also opening a support ticket for this behavior but thought I would post here in case anyone else has experienced a similar issue.
Problem Description
When an RS300 running firmware 1.2.7.2 is connected to a Cisco switch port configured with BPDU Guard, the Cisco port immediately transitions to an err-disabled state.
Cisco switch log:
%SPANTREE-2-BLOCK_BPDUGUARD:Received BPDU on port Gi6/46 with BPDU Guard enabled. Disabling port. %PM-4-ERR_DISABLE:bpduguard error detected on Gi6/46, putting Gi6/46 in err-disable stateWireshark Analysis
To isolate the problem, I disconnected the Cisco switch and connected only:
RS300 (AP Mode) | +--- Windows Laptop running Wireshark
No other networking devices were connected.
The RS300 LAN MAC address is:
28:94:01:0e:04:78
Using Wireshark with the filter:
stp
I observed the RS300 transmitting STP Configuration BPDUs approximately every two seconds.
Observed BPDU details:
Destination MAC: 01:80:C2:00:00:00
Protocol: Spanning Tree Protocol (STP)
BPDU Type: Configuration
Root Identifier:28672 / 0 / 28:94:01:0e:04:78
Bridge Identifier:28672 / 0 / 28:94:01:0e:04:78
The Root Identifier and Bridge Identifier match the RS300 LAN MAC address, indicating that the RS300 is originating the STP BPDUs and acting as the root bridge.Firmware Comparison
I currently have two RS300 units available:
RS300 #1
Firmware:
1.0.1.90
Behavior:
AP Mode enabled - No STP/BPDU packets observed in Wireshark. Does not trigger Cisco BPDU Guard
RS300 #2
Firmware:
1.2.7.2
Behavior:
AP Mode enabled - Transmits STP Configuration BPDUs. Triggers Cisco BPDU Guard
This suggests a behavioral change or regression between firmware versions.Downgrade Attempt
I attempted to downgrade the RS300 running firmware 1.2.7.2 to firmware 1.0.1.90.
The downgrade was rejected by the device and did not complete successfully. - FURRYe38Guru - Experienced User
Keep in contact with NG support on this. Won't be anything we can do on the FW side of things.
Only suggestion would be to put in a non managed switch that doesn't require BPDU Guard, something in between the RS in AP mode and your main switch that does require BPDU Guard.
- dogvomitAspirant
Thanks for the suggestion, I tried a non-managed switch in between and it simply passes the STP packets through and causes the Cisco switch to put the port in err-disable state. I also verified the RS700 is generating the BPDU packets in AP mode by connecting a laptop to the WAN port and capturing a Wireshark trace. It shows the source as the RS700 MAC.
Interestingly, I also have an RS300 that works fine in AP mode (no BPDU packets). Purchased a second RS300 thinking it would work, but it does not. New RS300 has a newer firmware (1.2.7.2) vs the working RS300 that has 1.0.1.90. Firmware 1.0.1.90 is not generating BPDU packets in AP mode. I compared all settings side by side and they are the same (except for SSID). New RS300 will not accept the older 1.0.1.90 firmware.- FURRYe38Guru - Experienced User
Can you downgrade the RS700 to older FW?
- dogvomitAspirant
I am experiencing a similar issue.
I have an issue with RS700 where it sends BPDU packets and causes the switch port to put ports into err-disable state, but only when it is set to AP mode. Switch is required to have BPDU Guard enabled.
The RS700 has firmware 1.0.11.8, which is the latest shown on Netgear support page.I opened a support ticket for this issue but did not receive a resolution.