The "gi+1" feature looks interesting, but not critical for us. We are
happy to define a pool, even if it only contains a single address.
The important bit is that we want these requests to never fail because
of a previous lease. A "do-not-store-leases" subnet flag seems like an
acceptable approach. A "fixed-address" reservation might be even more
specific, provided it supported giaddr reservations and wouldn't fail
due to active leaseholders.
I looked over the documentation and code, and it seems to me like this
is not a current feature.
On 2021-07-21 16:21, perl-list wrote:
I assume what OP is talking about is the same behavior from ISC DHCP
where "fixed-address" did not store a lease so any device that matched
the conditions could get the IP.
----- Original Message -----
From: "Anders Rosendal" <[email protected]>
To: [email protected]
Cc: "kea-users" <[email protected]>
Sent: Wednesday, July 21, 2021 4:09:11 PM
Subject: Re: [Kea-users] Prevent lease storage for some subnets
Hi
Only a user myself, and have not read if this is possible, although I
totally
agree it's a good idea.
In an ISP environment it's fairly common to have /30 or /31 ptp-links
for mgmt
of cpe's. For these scenarios I have seen a few inhouse build
solutions which
do what we call "gi+1", i.e. when a discover/request comes in just
reply with
adding "1" to the gi-address of the request.
With this solution autoconfiguration of equipment can be performed,
also if the
access network allows the IP can be configured statically during
initial
autoconfiguration.
If this feature is not available, I do think it would be a useful
addition.
Regards Anders R
On Sat, 17 Jul 2021 at 14:31, < [ mailto:[email protected] |
[email protected] ] > wrote:
Hi all.
Our network has a lot of /30 and /31 subnets, designed for a single
device on a single switchport. So our kea configuration includes lots
of
subnets with only 1 address in the DHCP pool. We currently issue
addresses using the DHCP relay address, and this works very well.
But we have some mobile devices that move from port to port, and they
occasionally cannot receive an address because the last device to
attach
to that switchport is still holding the lease.
We would like to configure kea to prevent it from storing leases for
these subnets: if another device attaches to that switchport, we'd
like
kea to re-issue the address. (Note that we also have some traditional
networks, and we prefer kea to record and track leases normally for
those subnets).
Is this behavior currently supported? Or will it require new
development or external integration to remove the lease from the
database?
Thank you,
David Potter
_______________________________________________
ISC funds the development of this software with paid support
subscriptions.
Contact us at [ https://www.isc.org/contact/ |
https://www.isc.org/contact/ ]
for more information.
To unsubscribe visit [
https://lists.isc.org/mailman/listinfo/kea-users |
https://lists.isc.org/mailman/listinfo/kea-users ] .
Kea-users mailing list
[ mailto:[email protected] | [email protected] ]
[ https://lists.isc.org/mailman/listinfo/kea-users |
https://lists.isc.org/mailman/listinfo/kea-users ]
_______________________________________________
ISC funds the development of this software with paid support
subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
