The client device should request an IP from the DHCP Server… if there is already a lease for a specific client then in order to get a new different IP the client must release the one it has and then renew to a new one…
Your DHCP server has nothing to do with that…
The proccess is ( How DHCP Server works ):
Client Discovers a DHCP server
DHCP Server Offers an address
DHCP Client Requests the address offered
DHCP Servers sends an Ack
Dont know if it will work, but maybe try and change something under system tab, i.e. un-tick and re-tick something and then click apply to save changes, maybe then it will then renew DHCP lease
I obviously can’t speak for Mikrotik … however, it’s been implied a few times that SwOS is not going to get any UI other than web UI. CRS series can run both SwOS and ROS, both offering same functionality but with different UI selections. Low-end switches and CSS series can only run SwOS though …
Web UI of SwOS is designed with simplicity in mind. Vast majority of people don’t link CLI and simplicity … ROS, OTOH, is designed to be extremely flexible. Multiple UI choice goes hand-in-hand with flexibility.
As for getting a new IP from the DHCP server, assuming you are using DHCP reservations in the DHCP server, simply give the MAC for the switch a new IP. Next time that the switch requests a new IP, it will get the new address. Nothing to do in SwitchOS. Obviously this is not instantaneous, but the switch will get a new address.
The RB260 is an extremely low-end product and I would not expect any software development aside from security bug fixing.
You even need to know if you have “old” or “new” hardware, we have a couple of RB260GS running but they are “old” and can only run 1.x software not 2.x where the latest development was.
As mentioned, the more capable switches can run RouterOS instead of SwitchOS and it has a telnet interface.
My CSS106-5G-1S has a reboot button on the bottom right of the SYSTEM tab.
So that is one way to initiate a release/renew, at the expense of the reboot time, and all counters being reset.
Oh, but I see you have a PoE model, so that is the problem you are trying to avoid.
I wonder it you could change the ip acquisition method to static, then back to DHCP with fallback.
I just tried this with a RB260GS (CSS106-5G-1S) with SwOS v2.18 non-poe
TL;DR changing from DHCP with fallback to static, applying all, then changing from static to dhcp with fallback and pressing apply will force a new DHCP DORA sequence, and it will change the ip address if the dhcp server changes. The uptime as reported by winbox does not change, so my guess is that it will not drop PoE output on the RB260GSP version.
-- more details follow for the interested.
I had mine set to DHCP with fallback x.x.x.211 as the reserved address in dhcp server as well as fallback address. I changed it the RB260GS from dhcp with fallback to static (using the address it currently had x.x.x.211, which you can see with winbox, even though you can't connect to it with winbox). Then press apply all. Then changed back to DHCP with fallback and pressed apply. Then looked at log from dhcp server, and the RB260GS had initiated a new DORA sequence.
I will now change the reserved address, and verify it will obtain a new address.
Ok, changed DHCP server to use a different ip (x.x.x.221) for the RB260GS mac address, then connected to ip address shown by winbox (still x.x.x.211), went to system tab, and changed ip to static (it had the same address as previous reservation), then press apply all. Then changed from static to dhcp with fallback (but left fallback address to the original value x.x.x.211). Then pressed apply all. Web page lost connection, winbox refresh showd that the RB206GS had new ip address from dhcp server (x.x.x.211). Connected to new IP address (x.x.x.211). (it used the dhcp, not the fallback address). Winbox "uptime" had not changed, so my guess is that this would not have dropped PoE on the RB260GSP.
Then reconfigured reserved address back to the original x.x.x.211 in the dhcp server. Then on RB260GS set to static again and pressed apply all. winbos refresh shows that the address set by static was used. Connected to original x.x.x.211 address, then changed from static to dhcp with fallback, then pressed apply all. Looked at dhcp log and saw that new DORA was done (although it obtained the same address as it currently had the static set to, which was expected).