Hello 3,
As Simon has previously pointed out a number of times, a client must send
multiple IA_NA’s in a request to get multiple addresses. This is discussed in
section 6.6 Multiple Addresses and Prefixes of RFC8415
(https://datatracker.ietf.org/doc/rfc8415/
Hello,
kea-dhcp6 complains abuout ip_vti0 interface down
2022-11-17 01:15:25.038 WARN [kea-dhcp6.dhcpsrv/2451.140297934552384]
DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: the interface ip_vti0 is down
2022-11-17 01:15:30.713 WARN [kea-dhcp6.dhcpsrv/2451.140297934552384]
The great thing about Kea is that it is very flexible and you can make it
work in a wide variety of ways and find the setup that works best for your
situation.
In our case we have a hybrid setup. The kea-dhcp4.conf file has all the
global settings, and we define the hosts-database for storing
>> seriously? i just killed rad and reconnected the client. shall i tell you
>> what has changed? NOTHING! do you think the dhcp client in windows is wrong?
>> if so, then will have to redo the rfc for windows, and not windows for rfc.
>> lol
> Did you tell the client to release its leased
> Allocating multiple addresses from one pool or multiple pools is a different
> question to shared networks.
> You can have multiple pools within one prefix; you can have a single pool in
> each of multiple prefixes; or any combination (e.g. multiple pools from
> multiple prefixes). One reason
3 wrote:
>> RA are absolutely needed for DHCPv6 to work. Properly working clients won't
>> do anything but sit there with an fe80:: address on its interface if no RA
>> tells it what else to assign and how to do so
>> (https://www.rfc-editor.org/rfc/rfc5175.html) leaving your only option to
3 wrote:
>>> "shared network" is not about how to allocate multiple addresses(it doesn't
>>> matter if we have one pool or several), but about how to combine several
>>> pools into one.
>> Almost - it’s about how to have multiple (IPv4) subnets/(IPv6) prefixes on
>> one wire.
> where do you
>> where do you see even a word about this in the documentation? in any
>> documentation, not only for kea, the "shared network" is referred to as a
>> pooled pool of addresses from which the dhcp server will take an address to
>> assign to the client. could you quote exactly the place where it
Thanks Dan!
So you have a hybrid configuration ?
What do you mean by "main configuration" ? Topology (shared-networks and
subnets) in json file and host-reservations in a database ?
Do you update the database using "reservation-add"
> where do you see even a word about this in the documentation? in any
> documentation, not only for kea, the "shared network" is referred to as a
> pooled pool of addresses from which the dhcp server will take an address to
> assign to the client. could you quote exactly the place where it says
We also have all the main configuration in plain json files. Like you, we
require hosts on some of our networks to be registered. Our registration
system stores the MAC addresses in the Kea database. For the past year or
so, this has worked really well for us.
I would highly suggest looking
>> "shared network" is not about how to allocate multiple addresses(it doesn't
>> matter if we have one pool or several), but about how to combine several
>> pools into one.
> Almost - it’s about how to have multiple (IPv4) subnets/(IPv6) prefixes on
> one wire.
where do you see even a word
3 wrote:
> "shared network" is not about how to allocate multiple addresses(it doesn't
> matter if we have one pool or several), but about how to combine several
> pools into one.
Almost - it’s about how to have multiple (IPv4) subnets/(IPv6) prefixes on one
wire.
> A client connected to a
I am wondering whether it is not more efficient to perform a
"config-write" followed by a "config-reload"
rather than a "config-set" ?
From: Kea-users on behalf of Veronique
Lefebure
Sent: Thursday, November 17, 2022 9:19 AM
To: Dan Oachs
Cc:
Hi,
We don't use any database for storing the KEA configuration: we use plain json
configuration files.
We need to update the configuration very regularly because we allow only known
clients (pre-registered mac addresses), hence the list of host-reservations is
quite volatile.
Véronique
15 matches
Mail list logo
