NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
When trying to "apply" changes, get a "400 Bad Request"
Hi,
I have the same issue...
Firmware up to date (V7.2.6.21_5.0.20)
When trying to "apply" changes, get a "400 Bad Request"
When selecting, then deselecting the "Support Automatic Pri...
ElDje wrote:
When selecting, then deselecting the "Support Automatic Private IP Addressing (APIPA)" , then "Apply" works...
Could you please humor an Old Guy and make a screen shot of the Help information that pops up from the bottom of the screen when the arrow is selected? I understand what APIPA is, but am totally confused about the meaning of "Support..."
These automatic IP addresses are in a totally different IP subnet from the normal private IP address spaces:
I have two different Orbi routers, and neither has this option on the LAN Setup page. Nor can I find any mention of this option in the RBR850 User Manual. Sort of hoping that there is information in the Help screen that may explain what this option accomplishes.
There was a post on the forum back in 2022 asking about this, but no answer.
https://community.netgear.com/t5/Orbi-WIFI-6-AX-AND-Wi-Fi-6E-AXE/APIPA/td-p/2257586
There is a Knowledge Base article saying that firmware v4.6.9.11 adds support for APIPA:
https://kb.netgear.com/000065128/RBR840-RBS840-Firmware-Version-4-6-9-11
Thanks
p.s. If this is obvious and I am just "dumber than dirt", somebody please point me in the right direction.
APIPA was a unknown feature that came in on v.11 back then. We asked NG was that was about but i don't honestly remember the feedback as as to why they put it in, it's been too long. This feature should not be in current v7 FW as NG removed it.
The user should factory reset the RBR and setup from scratch. Be sure to clear out all browser caches as well before starting the setup routine using a web browser and PC.
The user should be able to use any of the 3 IP class referenced as they are mentioned for home IP configurations.
APIPA == Zero-configuration networking
Microsoft refers to this address autoconfiguration method as Automatic Private IP Addressing (APIPA).
Not sure what this would mean for the Orbi Router NAT implementation - in the eyes of the limited memory space 8-)
As FURRYe38 pointed out, the issue is moot since the feature appeared only briefly and is not present in any current Orbi firmware. I was drawn to this option because it was mentioned in the discussion that enabling the feature had an effect on the problem, and I could not find it on my Orbi routers. This led to the question, "What does it mean to support APIPA?"
- APIPA becomes relevant only when devices do not receive responses to DHCP requests and are not set up with static IP addresses.
- Under normal circumstances, Orbi routers act as DHCP servers.
- When Orbi routers are placed in Access Point mode, the upstream router usually acts as the DHCP server.
- Or, users can run their own DHCP server.
- So, what if there is no DHCP server on the network?
In that case, every device creates its own IP address. As long as communication on the LAN is based on using broadcasts, it can be a functional network. "Hey is anyone out there a printer?" "I am. My IP is 169.254.x.x" Use ARP to find the MAC address of that IP and now the device can print. "Are there any media servers?" "Yes, we are at IP...." And so on.
So what part does an Orbi router play in this? Does it create a APIPA LAN address? Is there a way to use IP broadcasts to find an internet gateway? What does it mean to support APIPA?
Guess we'll never know.
