NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Access Point Mode Oddness
So, my architecture is a little complicated.
Internet: Cox 2.5 gig
Router: Network appliance running pFSense 24.03-RELEASE (amd64)
WiFi: Orbi 970 series in access point mode only. Firmware: V9.12.3.3_1.2.20
Like every story before, things were working perfectly until an ethernet adapter failed on me. That forced me to reinitialize the Orbi (which was in AP mode). Since then, every time I factory reset it and then changed to AP mode it does the same thing
Upon reinitialization - and then placing into AP mode (again), the orbi app shows RED - No internet. I have factory reset and reinitialized more times than I wish to count in last 24 hours.
The odd thing is that WIFI appears to be working... somewhat.
Here is how it is wired:
Cable modem -> Network Appliance running pFSense
pFSense -> unmanaged switch
Unmanaged switch -> Orbi base (connected at bottom RJ45 connection <yellow>)
Lan Port on Orbi -> one of the two satellites.
(Other satellite is wireless backhaul)
DHCP is provided by piHole running on separate network machine
DNS is provided by piHole running on separate network machine
This architecture was working perfectly until reinitialization.
Any initial ideas, comments or questions?
Help is appreciated.
5 Replies
Before changing to AP mode, does the Orbi complain about "no internet"?
The Orbi router and satellites have IP addresses reserved in the Pi-Hole DHCP server, correct?
After switching from 'router' to 'AP' mode, is the Orbi rebooted?
Yes, I have rebooted several times after converting over. Before converting, it works perfectly as expected. Once in AP mode the wheel falls off and it reports red on the ap... but I am thinking the devices and wifi may be actually working so I am not sure if it an app problem or a wifi issue.
Its been a while but I seen a different use with a similar issue running pfsense. (couldn't find the post but I didn't look to hard). If I remember correctly, it was an issue with pfsense. Not sure if it was an upgrade that happened behind the scenes.
