Messages

Open the ur config-OPNsense*.xml, the reservation uuid is unique per reservation and should have one subnet uuid if they belong to that subnet.

      </reservations>
          <reservation uuid="6a688941-02f8-46aa-abc6-8121fa434809">
            <subnet>7046c7cb-a9fb-4a50-8a49-3b6e77d42809</subnet>
            <ip_address>192.168.1.100</ip_address>
            <hw_address>90:a1:b1:c1:d1:e11</hw_address>
            <hostname/>
            <description/>
       </reservations>

But that shouldn't even required - as OPNsense is mainly a web-based OS.  Mentioned about his before.

[your]

> Personally, I don't think Kea is ready to be added to OPNsense at this time.

Fair enough, but stating 3 obvious points and concluding we should not ship it which means we will stop improving it in the first place is a bit strange IMHO.

If you meant to say it's not ready for your use your wording could benefit from improvements.

No disrespect, just stating the obvious (again).

Cheers,
Franco

As a software developer/engineer myself, when including new features that *typically* gets put into an alpha or beta build or some other testing environment - NOT the mainstream/stable one.  That is bad practice.  As for the "obvious" points, they were mainly from other users.

Kea IS CLEARLY not ready, as it can't replace the original ISC DHCP.

I can understand you want feedback, but you also see where I'm coming from right?  I can symbolise.

Please talk to me as an human being.

This is why I've switched to AdGuard Home for my network.  As it supports more modern things, in regards to DNS.

Only noticed this recently as Gmail changed there list of SMTP servers...

I made another list of comma-separated values like I have before to paste into the alias but now it doesn't parse it all - just one big lump incorrectly.

I even tried to "copy" an existing one and pasting it back - it does the same :/.


What's going on with this?

[Edit]

I've been a LONG time user of OPNsense, ever since m0n0wall suggested this alternative (back on WRAP hardware), many years ago.

Just registered for the first time to elaborate on some points (as I've just seen this in the changelog): -

• I know why Kea is being added as the older ISC DHCP package has been EoL'ed
  But, the UI for Kea (as provided by OPNsense) is NOT functionally equivalent to the original ISC DHCP in many ways, including not being able to exclude "known clients" and I don't even see a IPv6 option too.
• There DOES need to be the ability to move over settings from ISC DHCP, as like others mentioned earlier - I've got multiple interfaces/VLANS.
• Numerous users have also reported so many features NOT available so far.  For example, defining TFTP, DNS, NTP addresses, etc

Personally, I don't think Kea is ready to be added to OPNsense at this time.

Just my two pence.


Edit: To mention about the lack of services Kea doesn't.  At least in the OPNsense way.