Issue with 2.1.3.4 in AP mode?

I believe i have found the issue.   I appears that the DHCP Server value in the nvram is not being reset when switched to AP Mode.  In my case it is set to a Comcast IP (something that was left over from the default router mode setup).  The DHCP value should be set to the Default Gateway value (in my case 192.168.1.1).  This is why the Orbi is not passing the IP address on to wireless clients.  please see in the attached picture. 

Anyoen else running AP mode care to confirm on their setup?

Running 2.1.3.4 in AP mode here. No issues.  DHCP shows as ON.  However, I think this pertains to the DHCP client and indicates the Orbi router is obtaining its LAN IP address via DHCP from my third party router.

This is not a global Orbi problem.  It sounds to me like your Orbi router may be set to a static IP that's left over from your old router and is not consistent with your current router.

I suggest you should go back into the Orbi AP Mode setup screen and ensure that "Get dynamically from existing router" is checked rather than "Use fixed IP Address (not recommended)"

---

jdpg2 wrote:

I believe i have found the issue.   I appears that the DHCP Server value in the nvram is not being reset when switched to AP Mode.  In my case it is set to a Comcast IP (something that was left over from the default router mode setup).  The DHCP value should be set to the Default Gateway value (in my case 192.168.1.1).  This is why the Orbi is not passing the IP address on to wireless clients.  please see in the attached picture. 

 

Anyoen else running AP mode care to confirm on their setup?

 

 

 

 

In AP mode it is set to get ip dynamically .  My Router is configured to "serve"  the same IP to the Orbi AP. 

Could you do me a favor and look at what is listed under  Advanced Home, in the Lan Port section ,  click on Connection Status and tell me if your "DHCP Server" value is the same as your "Default Gateway";?

I can't see what you posted until NETGEAR reviews and approves the picture.

Yes, my DHCP server is 10.0.0.1 and my default GW is 10.0.0.1.  My Orbi IP in AP mode is set to 10.0.0.201. This is picked up via DHCP and is a static reservation in my Mikrotik router.

We have a winner!!!!!... there is a bug in the FW...  thats the issue i am having the nvram value for DHCP Server is not being reset to my Default Gateway. ie the real DHCP ip address.

---

jdpg2 wrote:

We have a winner!!!!!... there is a bug in the FW...  thats the issue i am having the nvram value for DHCP Server is not being reset to my Default Gateway. ie the real DHCP ip address.

---

Could be a bug of some sort. Sounds like something that should be resolved by a factory reset and setting up from scratch.

You would hope so but i have done 2 resets now with no change.

Possible upgrade process issue. How did you upgrade your unit? Auto upgrade or manual? 

What specifc browser are you using? 

I use manual and have never seen this kind of problem. I believe others have used auto upgrade and it's worked for them in the beta thread...

I have been loading all of the FW updates (publically released and Beta) all via manual updates and most via clean resets.  This one is really strange since i just stopped working.

What specifc browser are you using? 

Ya this one is very strange...

Edge and or Chrome... really irrelevant since i have had succes with both.

See bad behaviors before with Chrome. Try this next time please, use IE11 and or FF. 

Hope it keeps working now. Glad you got it runing correclty. Hopefully won't happen again. 

Enjoy. 

To the guy using his Orbi with Comcast and in just AP mode.  I am able to use my Orbi setup in just AP mode and all my wireless devices are getting an IP from the Xfinity XB6, gigabit.

I have the Xfinity to a 8 port switch, then port to the Orbi as AP only. Port 2 goes to a wired device in office, port 3 to printer.

I am NOT using wired backplane on orbi. The upstairs satellite and den satellite are both working fine and running the new 2.13.4 firmware and using a wireless backplane.

Upstairs I have a wired port that runs to port 5 on the 8 port switch, that port goes to a switch that distributes wired ethernet to the den TV, den Xbox, AppleTV, and a upstairs tme machine backup drive on wired (old Airport Express with wireless turned off just using as timemachine drive).

So there are 3 switchs in the house in the mix, and IP passes to all fine wired.  Are you using a wired backplane in any manner AND have you made sure you don't have a RESERVED IP setup in your comcast router.  Your Orbi satellite is going to think its getting DHCP but the Comcast box when using RESERVED IP will always give it the same UP - like a static IP but forced on the device by the router not setup in the Orbi.

my set up is a bit different.  My Comcast GB router is in Bridge mode and connected to an Untangle Network appliance.  I have it wired to several unmanaged 8 port switches.  So DCHP (ip's)  are assinged by the Untangle device.  The issue i had was the update didnt set the wan DHCP server value to the Untangled IP , it had it set to some unknown default ip address.  Once i telneted in and edited it with Putty it worked fine.  I have since dont a full rest and restore again and it appears to be working fine.  The issue is if someone else has a similar  issue i am not sure they would have the IT experience to edit their nvram...