Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. ISC DHCP 4o6 (Francis Dupont)
2. Re: ISC DHCP 4o6 (Francis Dupont)
----------------------------------------------------------------------
Message: 1
Date: Thu, 23 Jul 2015 15:34:40 +0000
From: Francis Dupont <[email protected]>
To: [email protected]
Subject: [kea-dev] ISC DHCP 4o6
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
In order to help the design of DHCP 4o6 support in Kea, here are some
notes about the DHCP 4o6 support in ISC DHCP.
First ISC DHCP uses a monolithic configuration file so the first question
is about handling both DHCPv4 and DHCPv6 in the same server process
with one configuration file and one lease file for both.
The answer is it can work but it is nearly impossible to use. There is
a negative proof of this in the #36639 ticket / rt36639 branch.
So I went to a 2 server design: one for DHCPv6 and one for DHCPv4,
all DHCP 4o6 messages are given to the companion server using a pair
of consecutive bound sockets (make easier to detect when the companion
is not available). A minimal information is prepended to help the
subnet selection, itself a mixed of DHCPv6 and DHCPv4 usual checks.
For similar reasons I found the 2 process design easier for the client:
the DHCPv6 client handles standard DHCPv6 messages and communicates
with a DHCPv4 client (usually a child launched through a script)
for DHCP 4o6.
Of course there is nothing for relays as DHCP 4o6 is transparent
for DHCPv6 relays...
The whole stuff has been under review since September 2014 and is
available in ticket #35711 / branch rt35711b (note the 'b').
Regards
Francis Dupont <[email protected]>
------------------------------
Message: 2
Date: Fri, 24 Jul 2015 08:28:42 +0000
From: Francis Dupont <[email protected]>
To: Francis Dupont <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] ISC DHCP 4o6
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
The format of messages used by ISC DHCP 4o6 is:
- interface name on 16 octets
- client IPv6 address on 16 octets
- full message (i.e., including DHCPv6 relay stuff if any)
Note it can be useful to start with a compatible format/procedure
for Kea so the IPv6 and IPv4 parts can be developed independently
(or even in parallel, i.e., we have a divide & conquer opportunity).
Regards
Francis Dupont <[email protected]>
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 16, Issue 11
***************************************
