On Thu, Oct 20, 2011 at 9:53 AM, Vladislav Grishenko <[email protected]> wrote: >> > It also used in unaccepted(yet?) udhcpc 6RD support patch from OpenWRT >> > > https://dev.openwrt.org/browser/trunk/package/busybox/patches/244-udhcpc_add > _6rd_option.patch >> >> Hmm. I applied that patch to git. > > Two little additions: > 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. > 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? -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
