[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    RE: [PATCH 2/4] dhcp6c: Add sprint_nip6
From:       "Vladislav Grishenko" <themiron () mail ! ru>
Date:       2011-10-20 10:39:58
Message-ID: 006501cc8f14$9ed663b0$dc832b10$ () mail ! ru
[Download RAW message or body]


> > Shouldn't it be as feature and depend on IPV6?
> > http://code.google.com/p/wl500g/source/browse/trunk/busybox/303-
> udhcp-
> > 6rd.pa
> > tch#22
> 
> Well, udhcpc itself uses only IPv4, it's *other programs* who will use
$ip6rd
> value. Those other programs might be IPv6 capable, even if udhcpc is a
part
> of busybox which built without IPv6 support. For one, some people might
> build busybox with only one applet: udhcpc.
> 
> Making 6rd support an optional feature is ok with me.

Ok, thanks for the clarification. Personally we use it always enabled.

> > Next, http://www.comcast6.net/ ISP uses its own 6rd option number 0x96
> > with same format and purpose as 0xd4 from RFC.
> 
> Do they plan to switch to RFC-specified number?

Well, I don't know, here's some info
http://www.comcast6.net/6rd-config.php#config5
> If you choose DHCP, you must configure your DHCP server to pass down the
> 6RD Option. Since IANA has yet allocated the DCHP option number for 6RD,
> we use 150, which will work fine until the reserved option number has been
> assigned by IANA.
But the fact is they still hasn't switched to RFC, and probably will not,
because it's rumored they will drop 6rd and provide native ipv6 connectivity
instead.
So, by now, comcast 6rd option is in use

Best Regards, Vladislav Grishenko




_______________________________________________
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]