Hi @raptorq99,

It's been a while since using Web UI, but I think you just need to delete the static1 and static2 entries in the DHCP pool config.

  @D-C 

Hey DC,

thanks for the reply. Well are you saying I can only use one Pool if I want to manually bind IP adresses? Does it have to be the whole Class C net /24 then? Or do you mean that the manually bound adresses must not belong to any defined pool?

Edit: Alright, I figured it out :-) Thanks to your suggestion I deleted the 2 other subnets and used only one pool for 10.0.187.0/24. To make sure only 10.0.187.101-199 are used for dynamic DHCP I added the rest of the subnet, which I wanna use static (manually bound) to the "Excluded IP Adress Config". Seems to work, tested two devices that are in the manually bind list, and both receive the DHCP IP that I defined. Will have to test the dynamic part now, but I am pretty sure that should work as well.

Take care,

raptor

raptorq99 wrote

  @D-C 

 

Hey DC,

 

thanks for the reply. Well are you saying I can only use one Pool if I want to manually bind IP adresses? Does it have to be the whole Class C net /24 then? Or do you mean that the manually bound adresses must not belong to any defined pool?

 

Take care,

 

raptor

Yes, @raptorq99, my understanding is the manually bound adresses must not belong to any defined pool.

The pool would contain ranges of ip addresses available to assign dynamically only.  Multiple pools allow for non-contiguous ranges if needed and the reserved or static IP values would not overlap with the any of the ranges in the pool.  That's how it's always worked for me so I never thought to do it any differently.

@raptorq99, I've not use the DHCP feature built into the switch much and seems the TP-Link logic is a little different than other services I use regularly.  I wrongly assumed it was the same, so appologies for any confusion.