Omada ER7412-M2 Firmware Updates
Omada ER7412-M2 Firmware Updates
@Clive_A As we wrote here I have a question to the ER7412-M2 about the firmware updates.. just don't wanna full fill now the other ones inbox..
https://community.tp-link.com/en/business/forum/topic/786140?replyId=1528274
Do you know when the ER7412-M2 will get a new firmware/ new pre-releases or betas?
Because currently I'm missing functions most models of the Omada series got already.. like SD-WAN or FQDN for Wirequard and Virtual WAN
But don't get me wrong I don't wanna know a date more if it can be expected soon like in a month or if there is nothing planed/ the devs did not announce something..
The reason why I'm asking because there are quite a few issues like with detecting if devices are online or the one in that linked post with the fixed DHCP addresses..
Like since as you said the version is already pretty old (think something like 10 months ago the pre-release/ beta of that version started) and these issues were fixed.
It is also I need a new router with 2 (or more) 2.5gigabit (or more of course) LAN/ WAN ports that is why I'm asking.. and since I need some of these functions for that use case definetly I'm thinking of buying the bigger ER8411 for that case now, even if I wouldn't need so much performance there..
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Julian2111
Thanks for posting in our business forum.
Julian2111 wrote
Alright, understandable.. Thanks for the information Currently I can't really test that DHCP issue since I replaced all devices recently that have a static DHCP address. But in case I have the time to test it, so I basically have to create some kind of a video clip were I show e.g. of my windows PC and the Controller the config before.. then I change it's fixed ip and show how I use "ipconfig -renew" and then I show the DHCP module log? When I had that issue I replaced my SIP router and my a few IP cameras, they always had fixed IPs over DHCP.. I just removed the old entry in DHCP reservation added a new one with their LAN mac. I never added those to IP-Mac binding so that is not the issue. I plugged in the SIP router and the cameras and they had an IP of my DHCP pool (172.16.1.110-172.16.1.140) instead of their fixed IP e.g. 172.16.1.33, I rebooted the router and they got the correct IP address.. since I replaced each by one it was for every device the same..
There are two situations regarding the DHCP reservation. You can reserve an IP address:
#1 Beyond the DHCP range.
#2 Within the DHCP range.
And there are two known behaviors:
For #1, this is a known behavior and bug, and like we discussed in the other thread. This requires a reboot and will be fixed in the future firmware update.
For #2, when the relation of IP1-MAC1 is changed to IP1-MAC2, MAC2 cannot get the proper IP1. But you have to wait for the DHCP lease time to be over. Release or renew on the client is not effective. Gotta wait for the lease time to be over and your MAC2 can get the correct IP1.
This is the expected behavior. NOT a bug.
The dhcpserver changes from the permanent status to a valid lease time(depends on your DHCP settings). When you just finish changing the IP address, that IP1 has not unbound itself from the MAC1(lease time is not over yet. As said, it is just from the permanent to the lease time.)
So the device does not get the proper IP.
A reboot would fix it. Or wait for the lease time of the IP1-MAC1 lease to be over.
- Copy Link
- Report Inappropriate Content
Hi @Julian2111
Thanks for posting in our business forum.
I do not provide any ETA or schedule for the firmware release. I do not decide when the firmware when to be released, and my information is delayed or may be changed without any notice to me. Due to the previous conversation with certain users who seriously complained about the schedule we informed, and the delay in the update, I decided not to share any information about the firmware release even if I am aware of it.
Even for the dev team, the schedule is dynamic. Something might happen and the timeline would be different.
Generally, we have a major update every 6 months. Minor update every quarter. Beta/Pre-release without a pattern to follow.
As for 7412-M2, your case seems to be the first one I have noticed. I do not find any emails about this model having trouble with the DHCP.
I assume we need some investigation. Maybe remote debug.
707-M2's DHCP issue has been confirmed. And will be fixed in the next release.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @Julian2111
Thanks for posting in our business forum.
Julian2111 wrote
Alright, understandable.. Thanks for the information Currently I can't really test that DHCP issue since I replaced all devices recently that have a static DHCP address. But in case I have the time to test it, so I basically have to create some kind of a video clip were I show e.g. of my windows PC and the Controller the config before.. then I change it's fixed ip and show how I use "ipconfig -renew" and then I show the DHCP module log? When I had that issue I replaced my SIP router and my a few IP cameras, they always had fixed IPs over DHCP.. I just removed the old entry in DHCP reservation added a new one with their LAN mac. I never added those to IP-Mac binding so that is not the issue. I plugged in the SIP router and the cameras and they had an IP of my DHCP pool (172.16.1.110-172.16.1.140) instead of their fixed IP e.g. 172.16.1.33, I rebooted the router and they got the correct IP address.. since I replaced each by one it was for every device the same..
I will ask the test team to try it out. I am not aware of any 7412-M2 having trouble with the DHCP. 707-M2 was experiencing it because a new feature was added to the system which caused it.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @Julian2111
Thanks for posting in our business forum.
Julian2111 wrote
If not I can record what I did, then they can watch and retry that.. Not sure if it matters but my Software Controller is running in a docker container in my synology NAS
We will simply test the software controller and the same model for a generic DHCP reservation setup. And see if the device can always request and get the proper IP.
- Copy Link
- Report Inappropriate Content
@Clive_A Ok, thanks for giving that to
the test team and let me know (if it doesn't take to much time away) what they found
- Copy Link
- Report Inappropriate Content
I need a new router with 2 (or more) 2.5gigabit (or more of course) LAN/ WAN ports that is why I'm asking.
I chased this down a while ago looking for help on how to implement a one-armed-router. From what I gathered, every WAN connection needs one port. This implies that every Omada gateway can handle at most one > 1 Gb WAN connection; nothing will handle multiple 2.5 Gb WAN links.
- Copy Link
- Report Inappropriate Content
@Dr_Marty Oh sorry I expressed myself bad.. I meant for the lan more than 1gig fiber internet is here currently not possible
- Copy Link
- Report Inappropriate Content
Hi @Julian2111
Thanks for posting in our business forum.
Julian2111 wrote
Alright, understandable.. Thanks for the information Currently I can't really test that DHCP issue since I replaced all devices recently that have a static DHCP address. But in case I have the time to test it, so I basically have to create some kind of a video clip were I show e.g. of my windows PC and the Controller the config before.. then I change it's fixed ip and show how I use "ipconfig -renew" and then I show the DHCP module log? When I had that issue I replaced my SIP router and my a few IP cameras, they always had fixed IPs over DHCP.. I just removed the old entry in DHCP reservation added a new one with their LAN mac. I never added those to IP-Mac binding so that is not the issue. I plugged in the SIP router and the cameras and they had an IP of my DHCP pool (172.16.1.110-172.16.1.140) instead of their fixed IP e.g. 172.16.1.33, I rebooted the router and they got the correct IP address.. since I replaced each by one it was for every device the same..
There are two situations regarding the DHCP reservation. You can reserve an IP address:
#1 Beyond the DHCP range.
#2 Within the DHCP range.
And there are two known behaviors:
For #1, this is a known behavior and bug, and like we discussed in the other thread. This requires a reboot and will be fixed in the future firmware update.
For #2, when the relation of IP1-MAC1 is changed to IP1-MAC2, MAC2 cannot get the proper IP1. But you have to wait for the DHCP lease time to be over. Release or renew on the client is not effective. Gotta wait for the lease time to be over and your MAC2 can get the correct IP1.
This is the expected behavior. NOT a bug.
The dhcpserver changes from the permanent status to a valid lease time(depends on your DHCP settings). When you just finish changing the IP address, that IP1 has not unbound itself from the MAC1(lease time is not over yet. As said, it is just from the permanent to the lease time.)
So the device does not get the proper IP.
A reboot would fix it. Or wait for the lease time of the IP1-MAC1 lease to be over.
- Copy Link
- Report Inappropriate Content
I just want to jump in here on something
I have a 605v2 at a remote site. I have noticed that it seems to prefer to give out DHCP leases that are higher than the highest "reserved address". Its not an issue for me, this place has at most 10 users, but still an interesting observation.
In my case:
LAN 192.168.100.0 /23
Devices with STATIC get put on 192.168.100.1-50 manually
DHCP Range is 192.168.101.1-250
I have some devices i cannot set a static on directly, so have reservations set in the 192.168.101.200-220 range
Often times, the router stars giving out DHCP leases 192.168.101.221 and higher, which is above the highest reservation. Rebooting it usually stops it doing that for a while.
However, in my case, all reservations do work and every device gets what its meant to.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 189
Replies: 11
Voters 0
No one has voted for it yet.