@terziyski 

Thank you. Yes, I think you're right when you say it's a lot for the C80. That's one of the reasons I'm trying to replace it with the AX6000.
I'm not going to use the 1022 devices, but I like to structure my entire network in a way that I recognize the devices according to the IP group. They are not vLAN, but something that gives me a similar perspective. Here's an example of my configuration:

Routers, Switches
192.168.0.1 - 192.168.0.19
AP's, Rext
192.168.0.21 - 192.168.0.39
Printers
192.168.0.41 - 192.168.0.49
Servers PDC & Mngm
192.168.0.51 - 192.168.0.69
NAS
192.168.0.71 - 192.168.0.79
Servers Production
192.168.0.81 - 192.168.0.99
Servers Test
192.168.0.99 - 192.168.0.51
Fixos DW
192.168.0.101 - 192.168.0.149
Fixos MW
192.168.0.151 - 192.168.0.254
DHCP
192.168.1.1 - 192.168.1.254
Devices on the farm (outside houses)
192.168.2.1 - 192.168.2.254
IoT devices
192.168.3.1 - 192.168.3.149
Cameras
192.168.3.151 - 192.168.3.254

I know I can configure the IPs manually but there are several situations where this becomes very annoying.
So, my doubt continues to be. Is it possible to have the AX6000 work like the C80 as far as IP reservations are concerned? If it is not possible, is there any other router, in the same range as the AX6000, that has this possibility?
Thank you.

  @PNorberto 

Hi,

I don't own the Archer AX6000 in particular, but on other TP-Link routers that behave like the Archer AX6000 the following workaround can be used.

1) Change the DHCP server's address pool to cover the whole address range of the subnet. (192.168.0.2 - 192.168.3.254)
2) Configure all the address reservations the way you need them.
3) Change the DHCP server's address pool back to the range you'd like to use. (i.e. 192.168.1.101 - 192.168.1.249)

If you need to add further address reservations at a later time, then you will have to use this workaround again.