DHCPv4-o-DHCPv6 with udhcp client

[Leonardo Jelenkovic]

Since no comment was given on my first mail, I ask again.

Can our modification for DHCPv4-o-DHCPv6 connectivity
with udhcp client be merged with busybox (its udhcpc)?

All changes are additions that will be compiled only if feature
DHCP4o6C is turned on.

Updated draft, code and diff to current busybox source code
(small changes since last post) are on:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-08
https://github.com/terastream/busybox
https://www.dropbox.com/s/tnp329x7gpewyqo/dhcp4-o-dhcp6.diff

Best regards,
Leonardo Jelenkovic

On 24 March 2014 18:10, Leonardo Jelenkovic
<leonardo.jelenkovic at gmail.com> wrote:
>
> Hello
>
> In one project we are trying to use udhcp client from busybox with
> DHCPv6 as transport for DHCPv4 packets (where "upstream" is IPv6 only
> and IPv4 is tunneled over it). Draft that describe this encapsulation
> is "DHCPv4 over DHCPv6 Transport"
> (http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-06).
> In short, DHCPv4 is placed in an option into DHCPv6 packet.
>
> That encapsulation/decapsulation is all that we added in (for now).
>
> It is assumed that IPv6 is previously obtained (e.g. with DHCPv6) and
> that IPv6 address of DHCPv4-o-DHCPv6 server is also known
> (both are command line parameters to udhcpc).
>
> Tests are performed using modified version of ISC DHCP
> (as DHCPv4-o-DHCPv6 server) that does same
> encapsulation/decapsulation using DHCPv6 as transport.
>
> Since our system uses busybox we would like that our modification
> (when mature enough) becomes part of busybox (udhcp client).
>
> Is this idea acceptable for addition to busybox?
> If so, can you give us some comments on our implementation?
>
> Current version is on:
> https://github.com/terastream/busybox
>
> Current diff (only our modification):
> https://www.dropbox.com/s/tnp329x7gpewyqo/dhcp4-o-dhcp6.diff
>
> Best regards,
> Leonardo Jelenkovic