Migrate to KEA IPV4

[JoK]

I got a small network with some static IP adresses and the rest dynamic, no VLANS and pretty much straight forward. I do have a FW Alias and LAN rules to prevent some static IP adresses from access Internet, they are LAN only.

My Q is, is migrating to KEA from ISC DHCP as stright forward as my LAN?? can I just disable ISC and activate KEA, set up the same static IP's and count on the FW Alias/Rule to work as before??

Any experience in this??

Thanks in advance :-)

[julsssark]

You didn't mention how your aliases are setup. Assuming they are a set of host IP addresses, everything will work fine when you switch to KEA as long as you make the same static IP assignments in KEA.

I just switched to KEA this morning. My network is IPv4 only, some VLANs and about 40 static IP assignments. I also have some aliases (host IP addresses) that are used for firewall rules. I don't use any advanced DHCP features. It took about 30 minutes to manually set KEA up. There is a script that would probably be faster for larger networks. Everything has been working fine all day.

In case anyone is wondering, hostnames are displayed correctly in AdGuard. I think this was added a few months ago.

[DEC670airp414user]

I manually added the subnets one weekend.

then copied over the Mac address / IP into a word document and copied them into reservations (about 25 to be exact)

I turned off ISC.  and enabled Kea.     some devices needed to be rebooted.

but everything worked as it should.    IOT firewall blocking for certain devices using alias also worked

it was easy for me

I wish I could manually add ONE DNS server to certain clients not them ALL.   but maybe that will be fixed going forward

[JoK]

Thanks for your replies, yes my alias is set up as IP adresses and the plan i to keep these static IP. Glad to hear that there is no issue doing this.

Thanks again

[JoK]

Oh, one last q. My network use IP range from 192.168.1.1 - 192.168.1.255. My subnet setting should then be 192.168.1.1/24 right?

I use the first 20 IP for static IP. so my Range starts at 192.168.1.21….as my “pool” did with ISC, is this correct?

TIA

John

[julsssark]

I used 192.168.1.0/24 for the subnet.

Yes, you are correct about the pool. Your pool should be the first to last address that you want to dynamically assign. Do not include any addresses that you want to assign a static IP. I personally start the dynamic addresses at .100 so I have room to add fixed addresses later.

[JoK]

Yeah that makes sense, but I have a small network and there is no way that i need room for more than 20 fixed IP adresses. It pretty much only router, switch, wifi, server and a few cams.

Thanks for your help.

[JoK]

Whats the difference in setting the subnet to 192.168.1.0/24 vs 192.168.1.1/24??

Sorry, im not sharp in this and want to be ready before migrating to KEA

[Patrick M. Hausen]

Semantically both are equivalent. Because "/24" means "cut off after 24 bits counting from the left". So the last octet is supposedly 0 in both cases, not 1 or anything different that you might place in there.

But ... how exactly any arbitrary piece of software deals with e.g. 192.168.1.1/24 is entirely context and implementation dependent. So better to leave the bits that are defined to be 0 by the prefix length at literal 0, too.

[julsssark]

.0 is used for defining a subnet. .1 is the address of your router.

See the Kea OPNsense docs: https://docs.opnsense.org/manual/dhcp.html#kea-dhcp

[JoK]

Thanks guys, 192.168.1.0/24 will be my subnet....:-)

[JoK]

Oh...thats was easy and painless....

Got bored and did the migration, most of the work was to add the static IP/Macs, works like a charm :-)

Thanks guys

[julsssark]

Glad it went well.