Implemented [add feature] cant set static IP outside the DHCP range for clients
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
using omada controller 4.2.11 and a tl-r605
I have servers, and some devices that need to be static ip.
I would like to set a static IP to my clients within [192.168.2.1-99] outside the dhcp range of [192.168.2.100-254] but it would not let me do it directly
there is a way to do it but it takes too much time just changing the DHCP range again and again
hope this feature is added
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Seems like controller version 5.x has introduced the possibility to assigne an ip outside of the DHCP range.
Here is the release note from the latest OC200 Firmware that includes Controller v5.0.29 : https://static.tp-link.com/upload/firmware/2021/202112/20211224/Release%20Note_OC200_v5.0.29.pdf
- Copy Link
- Report Inappropriate Content
@langamer101 What you actually do in this situation is make a DHCP. reservation, you are not configuring a static IP on the host/device.
- Copy Link
- Report Inappropriate Content
Dear @langamer101,
I would like to set a static IP to my clients within [192.168.2.1-99] outside the dhcp range of [192.168.2.100-254] but it would not let me do it directly
there is a way to do it but it takes too much time just changing the DHCP range again and again
hope this feature is added
Thank you for your valued feedback. This has been forwarded as a feature request to the product team for further evaluation.
Update: This (set static IP outside the DHCP range) has been added on Omada Controller v5.0 and above.
- Copy Link
- Report Inappropriate Content
I want to support this request. It would be very convenient to be able to reserve IPs outside the DHCP range. Unify already does this, so I'm sure Omada can do it too ;-)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@jcouzy How can i do that?
- Copy Link
- Report Inappropriate Content
Unfortunately, I can't help you with your problem, because I have almost the same one.
- Copy Link
- Report Inappropriate Content
+1 to this request.
I like to arrange my network with static leases in one range and dynamic leases offset in a separate range so they can't occupy the IP of a known device if it is briefly offline.
- Copy Link
- Report Inappropriate Content
@langamer101 I'm having the same issue as well, the only way I have found around it is to temporarily adjust your DHCP range to include the address you want then readjust after setting the static ip you want on the device
- Copy Link
- Report Inappropriate Content
Seems like controller version 5.x has introduced the possibility to assigne an ip outside of the DHCP range.
Here is the release note from the latest OC200 Firmware that includes Controller v5.0.29 : https://static.tp-link.com/upload/firmware/2021/202112/20211224/Release%20Note_OC200_v5.0.29.pdf
- Copy Link
- Report Inappropriate Content
I realize that this has been added.
This said, for my own education, how were DHCP reservations not satisfying your needs?
The only reply that indicates a rationale (beyond I'd like to) is:
"I like to arrange my network with static leases in one range and dynamic leases offset in a separate range so they can't occupy the IP of a known device if it is briefly offline."
My understanding is that DHCP reservations would handle that.
The DHCP server should never give out an IP that's reserved to another device, whether it currently leases the IP or not.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 7
Views: 3040
Replies: 11
Voters 7
