[prev in list] [next in list] [prev in thread] [next in thread]
List: busybox
Subject: DHCPv4-o-DHCPv6 with udhcp client
From: Leonardo Jelenkovic <leonardo.jelenkovic () gmail ! com>
Date: 2014-03-24 17:10:00
Message-ID: CANJyNKuZqrt6_L4ue1T1oGb5uiJ0V1Ohx_KsVsDB60FCXRyXKQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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
[Attachment #5 (text/html)]
<div dir="ltr"><div>Hello</div><div><br></div><div>In one project we are trying to \
use udhcp client from busybox with</div><div>DHCPv6 as transport for DHCPv4 packets \
(where "upstream" is IPv6 only</div><div>and IPv4 is tunneled over it). \
Draft that describe this encapsulation</div> <div>is "DHCPv4 over DHCPv6 \
Transport"</div><div>(<a \
href="http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-06">http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-06</a>).</div><div>In \
short, DHCPv4 is placed in an option into DHCPv6 packet.</div> \
<div><br></div><div>That encapsulation/decapsulation is all that we added in (for \
now).</div><div><br></div><div>It is assumed that IPv6 is previously obtained (e.g. \
with DHCPv6) and</div><div>that IPv6 address of DHCPv4-o-DHCPv6 server is also \
known</div> <div>(both are command line parameters to \
udhcpc).</div><div><br></div><div>Tests are performed using modified version of ISC \
DHCP</div><div>(as DHCPv4-o-DHCPv6 server) that does \
same</div><div>encapsulation/decapsulation using DHCPv6 as transport.</div> \
<div><br></div><div>Since our system uses busybox we would like that our \
modification</div><div>(when mature enough) becomes part of busybox (udhcp \
client).</div><div><br></div><div>Is this idea acceptable for addition to \
busybox?</div> <div>If so, can you give us some comments on our \
implementation?</div><div><br></div><div>Current version is on:</div><div><a \
href="https://github.com/terastream/busybox">https://github.com/terastream/busybox</a></div><div>
<br></div><div>Current diff (only our modification):</div><div><a \
href="https://www.dropbox.com/s/tnp329x7gpewyqo/dhcp4-o-dhcp6.diff">https://www.dropbox.com/s/tnp329x7gpewyqo/dhcp4-o-dhcp6.diff</a></div><div><br></div><div>
Best regards,</div><div>Leonardo Jelenkovic</div></div>
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic