Messages

Success here too.  no issues going to OPNSense 25.1 on my CWWK J6412 based HW.

can you also show the services>Kea DHCPv4>subnets details for the subnet that you set up?  Hit the edit button to see details. 

Are these reservation IP addresses also held static on the client devices or are they (client devices) set for DHCP ? 

Meh, OpenVPN tries to kick it into DCO mode... Can you add this to advanced settings and try again?

disable-dco

This also worked for me.  Thanks for posting.

just wanted to say thanks.  This post solved the problem I was having with ignored reservations.

All working now after following this thread.

Smooth here too using CWWK box on bare metal.

I just used the web GUI to upgrade.

A few clicks and done.  After backing up the config.

Did you try flushing the ARP table?

Leave it unchecked.

from the documentation...

The Kea Control Agent (CA) is a daemon which exposes a RESTful control interface for managing Kea servers. When building a high available dhcp setup, the control agent is a requirement for these kind of setups.

not sure why your destination is ! LAN NET.  I used "*" (any) for my destination and it worked fine. 

I didn't see any other material differences from what I did.

there is a config.xml file where you can change

Code Select Expand

<hostname>OPNsense</hostname

but did you keep a backup xml??  you could modify the backup and load it back in.

Hansen97124

Search on the subbnet uuid. 19b11319-3d95-40c0-8668-56b15a05a6c0

It should match ur network u declared earlier.

It didn't match.  This was the major hint that I needed to get to the solution described in the post just above this one. 

Thanks again.

EDITED:  I Figured it out!!

Previously, I Had a problem with KEA DHCP reservations being ignored.  (several posts above)

Simple mistake.  For subnet I entered

192.168.1.0/24  instead of
192.168.1.1/24

I honestly thought it needed to be "zero" at the end, and not "one" for subnet name.   The docs section for KEA DHCP even uses 192.168.1.0/24 as the prime example.   

Maybe someone may be able to explain why mine has to be 192.168.1.1/24 in order to get reservations to work.  <please>   

Live and learn.   Back to using KEA DHCP. 

Thanks all for the help!!

below is an example of from the config file.

looks ok to me.  Still not sure why the reservations are being ignored.   The client camera is set to DHCP, as it should be.

Code Select Expand

<reservation uuid="de71a788-801a-450f-b238-9ed0c4ee8656">
            <subnet>19b11319-3d95-40c0-8668-56b15a05a6c0</subnet>
            <ip_address>192.168.1.241</ip_address>
            <hw_address>9c:8e:cd:1e:xx:xx</hw_address>
            <hostname>amcrest1080</hostname>
            <description>amcrest1080</description>
          </reservation>


(changed MAC address to xx:xx at the end.   No other changes made to the code.)

Is anyone else having issues with KEA reservations being ignored.

On my LAN, I have a win 10 PC and several IP security cameras that have a KEA reservation, but another (different) IP address is being automatically assigned.