> May I suggest you continue this discussion privately with an ISC team member
> rather than on a public mailing list? Your sarcasm and very aggressive tone
> are not exactly appropriate and I don't think all members have to witness
> your personal rant against a software you dislike. Thanks.
> 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/)
> As per the Kea
>> 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
>> 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
>> "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
>> but i want several addresses AT THE SAME TIME. this is stated in rfc8415. and
>> here is what is said about rfc8415 in the kea documentation:
>>
>> The server will allocate, renew, or rebind a maximum of one lease for a
>> particular IA option (IA_NA or IA_PD) sent by a client. RFC
e is the config for the test:
vport0: flags=8943 mtu 1500
lladdr 00:00:00:00:00:01
index 10 priority 0 llprio 3
groups: vport
inet 192.168.85.1 netmask 0xff00 broadcast 192.168.85.255
inet6 fe80::200:ff:fe00:1%vport0 prefixlen 64 scopeid 0xa
> As a matter of clarification for the list, are the addresses you wish to
> assign across multiple address scopes, i.e. Site-local, Admin-local, Global,
> etc.?
addresses and their scope do not matter at all. it can be several local
networks, several global networks without routing out, there
> Sorry, I misunderstood your original post; I thought you said that you setup
> multiple Kea servers and wanted clients to get addresses from each of them,
> rather than having a single server with multiple subnets on the same
> interface. I apologize for that.
> In any case, the result you
e client to break up the prefix and assign the smaller
> subnets to the appropriate interfaces. The ISP router (or whatever) will add
> a route to your client for the entire prefix and your client will be
> responsible for what happens after that.
Identity Association for Non-temporary
> I am fairly certain that what you want to do is not possible. A client which
> receives multiple DHCP OFFER will choose one and complete the operation, and
> ignore the rest. It won't track all of them and obtain multiple addresses.
there doesn't have to be several of them, i just got
sorry, guys, but i'm going to ask the most popular question again, to which
there is still no working answer: how to set multiple subnets on a same
interface so that a client receives an address from each network? in other
words, to do what radvd does, but with the difference that it is not
13 matches
Mail list logo
