Issue with Static DHCP assignment (2.1.2.18)

I found similar issue with my NG wireless bridge. Set it for Static IP address of 192.168.0.11. Scope on router is 192.168.0.100 thru .200. However the IP address displayed on the routers connected list is a 169.#.#.# self assigned address. The bridge and everything works fine. It's just not correctly displaying the address for the device in the UI. I submitted a report on this.

Any static IP addressed devices should work with the address and the Orbi router should display the address correctly, even if it's not in side the DHCP IP pool scope I believe. Using addresses with in the scope should be used for IP reservations of course. 

I recommend submitting this  as well. 

---

KenStormwrote:

Bug?

Scenario:

A network device has already been on the network and given an IP address by Orbi DHCP.

You assign a static IP (in order to group similar items) which is outside the range of the DHCP scope.

Outcome:

No matter how many restarts of the client network device, Orbi still gives it its original DHCP address as obtained from Orbi.

Resolution:

Requires that the Orbi router is restarted in order to force it to issue the required static IP address.

BUG? - Should the network device on restart not obtain the IP allocated to it from Orbi not the original one allocated from the DHCP scope? 

 

---