Solution ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect

  @Fae 

solved it for the cameras (vlan2) but did NOT solve it for the Unraid server (vlan3), it always gets dynamic IP what ever I set. 

  @Fae I am experiencing issue which I never had before. er605 was configured for 4 wan's, everything seemed to work. Then I disconnected second and third wan to see if there are any issues if one connects/disconnects without reboot. So far everything worked. Then I disconnected fourth wan, that worked too with only main wan connected, no issues with loadbalancer, everything worked. After that, I connected 4g lte router which was never connected (huawei b618s), meaning only wan and first lan/wan port were connected. That is where I got issue which is not explainable. All devices which connect do have connection, on er605 those two show as connected. Wireless connected devices work without issues, wired devices work without issues. But my notebook from which I configured everything says that it can not resolve DNS, resulting in not working internet. 

So far, I though, this might be some DNS issues which I oversaw or configuration error, however, everything is correct and on all devices internet works. I've tried then setting cloudflares DNS for WAN's in advanced settings, this again works on all devices, but not on the notebook, neither wired nor wireless. Then I used ISP's DNS, resulting in same. As last, I've set all wan's and lan to use cloudflare and again, all devices work just not the notebook.

Notebook has no special settings, it gets the ip and dns over dhcp. OS is ubuntu 22.10. To exclude any possible config issue on a notebook, I've started live from usb, the issue persisted, no internet.

The only what works on that notebook is pinging dns ip's, but dns resolution does not work. From all IP's, only those which one sets as DNS are reachable.

This is first time in my life to experience the issue and there was nothing more which can be checked, driving me mad. Then I downgraded everything to latest no beta (omada and router firmware), suddenly internet worked on that notebook. Then I updated both to latest beta again, here it worked too, then I reproduced same steps with connecting/disconnecting wan's and bang, I've run into same issue. I have for now no clue what is wrong, but for some reason device from which I configure  network can't resolve DNS, and it is only that one device. To be sure, I reverted again and reproduced the issue.

@fae I am only today on this location (it is 600km away from my home) and if you have any suggestions or some new beta which I could test, then I could do it only today. It is not really critical, the company where it runs is ok with it as long as all other devices work, but they feel very uncomfortable running beta's. I have no remote access to the company, I will get it, but probably it will take few days, however, I do not feel comfortable to upgrade and downgrade omada and er605 over remote, as if anything goes wrong, company will be cut off the internet. Could you try to reproduce steps above?

EDIT: for some reason, steps above messed up dns configuration, I've fixed it by resetting router and setting up new omada controller. Reproducing steps above resulted yesterday in no error.

  @Fae you are welcome. I just wrote about issues into which I ran into, it does not always need to be some issue with the firmware if the default process breaks (like requirement for resetting to factory defaults, after upgrade, otherwise one needs to reboot for second time and reissue with dhcp new leases). I guess knowing it is more part of FAQ for this specific firmware. In many cases devs write not only changes since last version, but also faq/notes about that specific build (if there are any). If somebody else reports same issue like I, then you already can make this note for a faq for next release notes.

EDIT: if devs write such notes and warnings, then autoupgrade process in omada should warn user about it and wait with processing until user confirms it (by clicking yes button or something), ensuring that one has read the warning and that auto upgrade does not break. I do not imply my issue here, but I do current stable release which is autoupdated to all routers despite that you already know about the bug (I at least conclude it since there is already beta with a fix). In some way it is not responsible for company of a size like tp-link, however, mistakes happen, especially in development and deployment process.

From this thread for me it's not clear if this bug has caused only the IP reservation not taking effect or the router itself becoming unaccessable after the firmware update to v1.2.0 official firmware? ...as it happened in my case.

  @Arion 

Arion wrote

From this thread for me it's not clear if this bug has caused only the IP reservation not taking effect or the router itself becoming unaccessable after the firmware update to v1.2.0 official firmware? ...as it happened in my case.

 

Bug which is fixed is pretty well explained, but it is not really explained what exactly caused it, also not what exactly was fixed. I am not aware of the issue "unaccessable" and in which combination (oc controller or omada on non tp-link device) etc.. but dhcp reservation works and described bug is fixed. I upgraded from latest stable, first time I oversaw that in omada one can flash manually, I reseted the router to factory settings and upgraded via standalone mode. After first reboot, clients still had wrong addresses due to the fact they were leased by standalone mode. Next device I flashed over omada controller software 5.0.30, there were no issues at all. Next with 5.1.7 if I remember well which also worked without any issues and last with latest omada beta, also no issues. All those test were done on different devices in different networks, but in all cases SoC boards (rockpi4, rpi4 and rpi3) were used for omada controller software. I did not test OC2xx/OC3xx from tp-link but assume there should be no issues.

  @Fae Any idea when the non beta version will come out for this?