Reply

Re: Updated Firmware to 2.3.2.134 on XR500- WAN port no longer able to act as a Access port in AP Mo

Spacey67
Aspirant

Updated Firmware to 2.3.2.134 on XR500- WAN port no longer able to act as a Access port in AP Mode

To start this off my home network is segmented this way:

Motorola MB8611 Modem 3.1 2.5Gb NIC (192.168.100.1)

PFSense Firewall (10.0.0.0/24) running pfblockerng and Suricata, on Asrock NUC dual 2.5GB NICs

LAN side goes into Netgear XR500 Wireless Gaming router in AP mode and the WAN port on the XR500 acted like a bridge and worked perfectly fine until todays update, where now it refuses to accept any uplink cable in the WAN port of the XR500 and shuts down the rest of the ports despite being in AP mode , why did this behavior change with this update?

Here is what's plugged into the AP and what is handled by what:

-PFSense handles DHCP 10.0.0.1
-PiHole DNS server 10.0.0.3
-Netgear GS308E Switch 8 ports (Native Vlan, 10.0.0.20)
-TP-Link TL-SG108Ev4 8 ports (Native Vlan, 10.0.0.4)
-Both setup to be 802.1Q Vlan aware, storm control off, port mirroring off, IGMP snooping enabled

-PFSense handles DHCP 10.0.0.1
-PiHole DNS server 10.0.0.3
-Netgear GS308E Switch 8 ports
-TP-Link TL-SG108Ev4 8 ports
-Synology NaS 10.0.0.21
-MoCa adapter split upstairs going to basement via coax to a Netgear RAX 10 Wireless Router in AP mode
-Both Switches are untagged I have vLAN segments 10.0.10.0/26, 10.0.20/.0/26 10.0.30.0/26, MP Snooping on both, Ports configured are segmented for 3 ESXi Hosts
-Synology NaS 10.0.0.21 Bonded 2 Nics
-MoCa adapter split upstairs going to basement via coax to a Netgear RAX 10 Wireless Router in AP mode
-Both Switches are untagged I have vLAN segments 10.0.10.0/26, 10.0.20.0/26 10.0.30.0/26,

The only way I'm able to get my network to work now because of this update is leaving the WAN port empty putting the PFSense LAN into port 1 on the XR500- but this not only is the first issue, everything is extremely slow and even after checking MTUs I still can't access the XR500 from any port.

Help needed and appreciated

Message 1 of 4
Netduma-Fraser
NetDuma Partner

Re: Updated Firmware to 2.3.2.134 on XR500- WAN port no longer able to act as a Access port in AP Mo

As AP mode disables most features it may be best to contact Netgear directly, it's not something we (Netduma) can specifically help with
Message 2 of 4
Spacey67
Aspirant

Re: Updated Firmware to 2.3.2.134 on XR500- WAN port no longer able to act as a Access port in AP Mo

You guys program the firmware updates what do you mean contact netgear? AP mode with the WAN port worked as an actual port in the last stable version perfectly fine.

Message 3 of 4
Netduma-Fraser
NetDuma Partner

Re: Updated Firmware to 2.3.2.134 on XR500- WAN port no longer able to act as a Access port in AP Mo

We do the DumaOS side of the updates, Settings and Hardware is Netgear so we haven't made the AP mode at all.

I'm not really sure what you mean regarding the WAN port, that has to be used for the router to get internet and distribute that to connected devices.
Message 4 of 4
Discussion stats
  • 3 replies
  • 532 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 6E