@patmolloy 

 

Hey

 

1) How do I reserve DHCP address in the way I did in standalone mode. I don't see this anywhere. Is it hidden or just not there.

 

The only way to set a manual reservation is by selecting the device itself and under CONFIG enable use fixed IP

 

 

2) How do I actually see the DHCP reservations at *all*. I also don't see this.

 

Yeah its not there sadly, really should be a list of DHCP and Reservations somewhere on the SDN.   This has been mentioned a few times by forum members (myself included) and I am lead to believe its on the radar for a future release version.

 

 

3) Is there *any* DHCP reservation process supported in this configuration?

 

See answer 1..  its there but not clear or easy.. totally agree!

 

 

Oh dear. I feared as much. I might just go standalone for now and forego OpenVPN. I don't quite understand the interplay, however. If I *do* set up reservations standalone and assuming the adoption process actually works (i.e. I don't get that reversion to the 192.168.0.1 address which is tedious), would those reservations persist. Or is the adoption process destructive to this (and other things already configured in standalone mode)? Thanks so much for your most helpful (if disappointing!) reply! Pat

@patmolloy 

 

Hey

 

The adoption process is totally controlled by the SDN, therefore anything you set in local mode will be removed in favor of the SDN config.  So basically yeah its destructive, granted ive never tested DHCP reservations  specifically, but cant see why it would be any different

 

The 192.168.0.1   thing you mentioned is again the controller setting, it defaults to that upon adoption but you can change it via the SDN.    We all had that before!      If memory serves me right, changing the LAN interface IP in the SDN is the way round that...

@Philbert  Thanks. Oh dear, I appear to have fallen into rookie bear traps!! Ah well, spending 2+ hrs typing in all the DHCP reservations was, erm, therapeutic :-)

 

Don't really approve of the destructive nature of the adoption. May be a good tech reason for it, but deeply user unfriendly IMO.

 

Pat

Yeah. I use a few SDN vendors and they all do some type of reset during adoption, dont think TP Link are unique in that. It does kinda make sense why they do it, however its not ideal agreed. Be nice if there was some way to migrate stuff out of the local config and into SDN... likely wishful thinking!

Thanks. So helpful. Sincerely appreciate you taking the time. Kudos.