clean/split dhcp dmoessne config

[DanielFroehlich]

After migrating to KEA DHCP server onto sf1, we have lots of entries in the central /etc/kea/kea-dhcp4.conf
They belong to daniel and should move either in the "manual" config file or (I think I would prefer that) to a new "dmoessne-exclude.cong" (like we had back then with the inf1)

     /// Begin file /etc/dhcp/dhcpd-dmoessne-exclude-mac.conf
      # deny all KVM MAcs so they don't get a dhcp address
      /// match: substring(hardware, 1, 4)
      {
        "name": "dmoessne-reject"
//      "statement": {
//        "config": {
//          "value": "ignore",
//          "name": "allow-booting",
//          "code": 9
//        }
//      }
      },
...
...
...
...

[rbo]

What I learned the last couple of days/weeks with Kea is that.

The reject dhcp stuff created during the migration is suboptimal:

part of client-classes

      # reject dhcp from secondary interface ucs57
      {
        "name": "sub#coe-reject#ucs57",
        "test": "substring(pkt4.mac,0,6) == 0x58ac780318b2"
      },

Following is much better:

part of reservations:

{ "hw-address": "58:ac:78:03:18:b2","client-classes": [ "DROP" ] },

We should consider a general config cleanup here

[dmoessne]

Worklog:

# cp /etc/kea/kea-dhcp4.conf /etc/kea/kea-dhcp4.conf-2026-03-05
# cp /etc/kea/kea-dhcp4.conf /etc/kea/kea-dhcp4.conf-mod
# vim /etc/kea/kea-dhcp4.conf-mod

Removed all dmoessne related stuff (hopefully only) and moved the exclude config to : /etc/kea/blocked-hosts-dmoessne.json which is included via

727       <?include "/etc/kea/kea-dhcp4-reservations-automation.conf"?>
728       <?include "/etc/kea/kea-dhcp4-reservations-manual.conf"?>
729       <?include "/etc/kea/kea-dhcp4-reservations-ibmpower-auto.conf"?>
730       <?include "/etc/kea/blocked-hosts-dmoessne.json"?>   <<<<<<<<<<<<<<<<<

# cat /etc/kea/blocked-hosts-dmoessne.json
  { "hw-address": "xx:xx::xx:xx:f2", "client-classes": [ "DROP" ] },
  { "hw-address": "xx:xx::xx:xx:f3", "client-classes": [ "DROP" ] },
  { "hw-address": "xx:xx::xx:xx:f4", "client-classes": [ "DROP" ] },
  { "hw-address": "xx:xx::xx:xx:f5", "client-classes": [ "DROP" ] },
  { "hw-address": "xx:xx::xx:xx:58", "client-classes": [ "DROP" ] },
  { "hw-address": "xx:xx::xx:xx:59", "client-classes": [ "DROP" ] },
  { "hw-address": "xx:xx::xx:xx:48", "client-classes": [ "DROP" ] },
  { "hw-address": "xx:xx::xx:xx:49", "client-classes": [ "DROP" ] },
  { "hw-address": "xx:xx::xx:xx:f0", "client-classes": [ "DROP" ] },
  { "hw-address": "xx:xx::xx:xx:f1", "client-classes": [ "DROP" ] } 
# 

# kea-dhcp4 -t /etc/kea/kea-dhcp4.conf-mod
# cp /etc/kea/kea-dhcp4.conf-mod /etc/kea/kea-dhcp4.conf
# systemctl  restart kea-dhcp4

Revert:

If issues occur:

# cp  /etc/kea/kea-dhcp4.conf-2026-03-05 /etc/kea/kea-dhcp4.conf
# systemctl  restart kea-dhcp4

[dmoessne]

seems we got issues with OCP5 .. copied back old config and reloaded the config only

[rbo]

@dmoessne What's the last status? Did you add the ocp5control to "static" leases?