Clarification on Dynamic IP range and reserved IP range

I am working on a home lab setup with a handful of mini micro machines.

The goal was to have a home network off my Asus router assigned in the standard 192.168.1.* space.

Then have the MAAS controller be on 192.168.0.1 and assign machines in the 192.168.0.* space.

On my router I statically set the maas controller address and added it to my Asus router so DHCP points to my maas controller prior to using its own.

All was well and good. Almost.

I can netboot all of my mini micros and commission them in MAAS. So cool.

But when MAAS assigns ip addresses it is assigning them on the home network 192.168.1.xxx.

I think the problem is my subnet settings.

In my subnet I pointed to the Asus router (which is on 192.168.1.1 the home network) as the gateway and that gave me a subnet cidr of
192.168.0.0/23 which is
192.168.0.0 - 192.168.1.255

If I try to make my subnet 192.168.0.0/24 to be just the .0 addresses then it complains because my gateway is not in the subnet.

Should I have my gateway not point to the Asus?

and

My goal was to have MAAS assign in the range of 192.168.0.100 to 0.110

You can create a dynamic range from 192.168.0.100 to 192.168.0.110 and a reserved range from 192.168.1.1 to 192.168.1.255

Thank you. I will do that now. Then I will recreate my Juju install and see how it works.

That worked but it makes me wonder if I am mistaken on the dynamic range setting. I thought that was going to be where IP addresses are assigned from. I will google that more. Thanks.

The dynamic range is the one used to boot ephemerally a machine (for example when you commission on) or when you assign an interface to the type DHCP.

The reserved range is used to tell MAAS not to use any IP address there.

Every other IP address not in the dynamic range nor the reserved range can be used by MAAS when you an interface of type “AUTO-IP”

@heneryhawk,

Your setup looks like the case of implementing 2 dhcp service e HA set in same network segment of /23 (1 svc running in MAAS e 1 svc running probably is set on home router).

Additionally to what was exchanged in above, you also have to setup the ip range exclusion on your home router of the ip range used by MAAS. [ e.g. home router dhcp, serves only range 192.168.1.1-192.168.1.254 or define exclusion of range 192.168.0.1-192.168.0.254 (e.g 50-50 ip range split of /23 for each dhcp). In this way you know exactly where the IP came from and which dhcp svc.

Yes, I have an Asus home router running Merlin that is capable of declaring a second DNS service in addition to itself and using that declaration as primary with itself being secondary. Per Chris’ Blog MAAS for the Home.

The goal is to have MAAS serve the metal machines it spawns while the Asus home router manages everything else (ie my wife is using her work machine while VPN’ed in to her company, LoL, I have booted her off her work before)

Then, you should not enable DHCP on MAAS. If you follow that blog you are actually setting up your home router to do all the job.

You should just setup your home router to avoid using the x.0.1 - x.0.254 addresses (because MAAS will use them to assign a static ip to your machines) and in MAAS you should setup the reserved range from x.1.1 to x.1.254.

If you want to understand a bit better what you are doing, you can watch Show and Tell: Using external DHCP with MAAS

1 Like