Firmware IP AP-MODE BUG R7800 version 1.0.2.44

[Retired_Member]

Today I upgraded our Routers from Firmware 1.0.2.38 to 1.0.2.44.
(I skipped 1.0.2.40 since there were a lot discussions claiming unexpected behaviours)

The result / Bug:
In AP-MODE the router either himself always gets the IP 0.0.0.0 or

the other case if it is already configured, the IP cannot be changed.

A rollback to Firmware version 1.0.2.38 solved the issue.

[FURRYe38]

Yes this issue is known and NG is aware of it:

https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-46sf.44387/#post-380645

and
https://community.netgear.com/t5/Ni...800-FW-1-0-2-44-Discussion/m-p/1504989#M82867

[Retired_Member]

Unfortunately your second link is down/broken.

The first link only leads to a custom FW. For our company we can't rely on that.

Is there a way to find out when this will be fixed in an official upgrade? I means it seems already to be a known bug from the version 1.0.2.40 before....

[antinode]

> Unfortunately your second link is down/broken.

      https://community.netgear.com/t5/x/x/m-p/1504989

   On these (Lithium) forums, the actual text between "/t5/" and the
topic number is not important, but the number of slashes is.

[FURRYe38]

Ya I forgot to get a permalink:

https://community.netgear.com/t5/Nighthawk-WiFi-Routers/R7800-FW-1-0-2-44-Discussion/m-p/1506328/hig...

IT was to let you all know that NG is aware of it and is working on it. 

Work around is this:

For users wanting AP mode to work on v4x FW, do the following: From NetGear Guy.

1. Load v1.0.2.38 and set to AP mode with static IP - working

2. Update to v1.0.2.44 (with out doing any factory resets) - working

Do not do the following or you will see the problem in AP Mode:

1. Reset to factory running v1.0.2.44

2. Set to AP mode with static IP and receive "site cannot be reached" You get and error or maybe see that you can't access the UI in AP mode router at all or can't find it's IP address on a connected client table like what happened with mine.

Hopefully this will be fixed in next OEM FW update for the R7800.

Reason for mentioning Voxels FW is that his FW in based on NG stock FW which also as this bug. 

Enjoy. 

[Retired_Member]

@Case850

First, because I can ^^

Is there something wrong with that?

I'm no expert but we use 5 of them in our company in AP-Mode using the same SSID and letting all the networking do our central server.

I thought AP-Mode would be the correct choice for that.

[seacowz]

I just spend two days discovering this bug on firmware V1.0.2.46.

[ablatt]

Is this fixed in 1.0.2.52?

[FURRYe38]

The OP has left the forum. Maybe you can let us know if it's fixed or not. I didn't see anything in the release notes about it.

---

@ablatt wrote:

Is this fixed in 1.0.2.52?

---

[ablatt]

It seems OK now.  I chose AP mode on initial setup after a reset to factory defaults and it used a DHCP address from my router.  I then went back in to settings through routerlogin.net, chose AP mode, and set a manual IP address on that same network and it took.

[FURRYe38]

Can you access the static IP address you set for AP mode?

---

@ablatt wrote:

It seems OK now.  I chose AP mode on initial setup after a reset to factory defaults and it used a DHCP address from my router.  I then went back in to settings through routerlogin.net, chose AP mode, and set a manual IP address on that same network and it took.

---

[ablatt]

Yes

[FURRYe38]

Good to hear.

Thank you for confirming this.