Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. New security vulnerability announcement (CVE-2021-25217) and
      releases of ISC DHCP (4.4.2-P1 and 4.1-ESV-R16-P1) (Michael McNally)
   2. OMAPI Reservations and peer/failover (Gregory Sloop)


----------------------------------------------------------------------

Message: 1
Date: Wed, 26 May 2021 13:30:38 -0800
From: Michael McNally <mcna...@isc.org>
To: dhcp-users@lists.isc.org
Subject: New security vulnerability announcement (CVE-2021-25217) and
        releases of ISC DHCP (4.4.2-P1 and 4.1-ESV-R16-P1)
Message-ID: <985c53ea-aa0c-542e-1831-5f3701f59...@isc.org>
Content-Type: text/plain; charset=utf-8; format=flowed

Hello dhcp-users subscribers -

It has been a long time since we last announced a security vulnerability
in ISC DHCP or since we published new releases of the software.

Our practice is to announce such events on the dhcp-announce list and
operate this list to host community discussion, but because of the length
of time since the last such announcements we believe it's quite conceivable
that there are subscribers here who are not subscribed to the announcement
list as well.

If you are such a person, we encourage you to subscribe to dhcp-announce
(it's VERY low traffic, the most recent messages before today were sent
in January 2020) but it is where we make important announcements about
the products.

Subscription can be accomplished via the list's main page:

   https://lists.isc.org/mailman/listinfo/dhcp-announce

and if you missed today's messages you can find them in the list archives:

CVE-2021-25217 announcement:
    https://lists.isc.org/pipermail/dhcp-announce/2021-May/000431.html

DHCP 4.4.2-P1 and 4.1-ESV-R16-P1 release announcement:
    https://lists.isc.org/pipermail/dhcp-announce/2021-May/000432.html


Sincerely,

Michael McNally
Internet Systems Consortium


------------------------------

Message: 2
Date: Wed, 26 May 2021 15:04:04 -0700
From: Gregory Sloop <gr...@sloop.net>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: OMAPI Reservations and peer/failover
Message-ID: <654688848.20210526150...@sloop.net>
Content-Type: text/plain; charset="iso-8859-15"

I finally got around to attempting to set the reservation flag on some dhcp 
leases using omapi.
(I'd asked about how to do this with OMAPI ages ago ... since I can do it live 
and not have to stop the DHCP servers and hand edit the leases file.)

I'm running a pair of peers/failover/load-balance machines for dhcp.

So, I set the reserved flag on one server, but the leases file on the other 
server doesn't see/reflect the reservation for that same lease. 
(I see the lease on both machines, but there's no reservation on the second 
server. The one I didn't target with the omapi connection/change.)

Do I have to run OMAPI against both servers? 
(I guess I kind of thought since it's a change to the lease, it would get 
communicated between the peers. That looks like a bad assumption.)

Can someone, (probably ISC) confirm the "right" way to do this?

TIA
-Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20210526/15ba4bd4/attachment-0001.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 151, Issue 10
*******************************************

Reply via email to