On Wed, Jan 16, 2013 at 1:07 PM, Chiradeep Vittal <chiradeep.vit...@citrix.com> wrote: > I would assume a 'modern' OS as well. Centos 6.2 / Ubuntu 12.04 / Windows > 2008(and above). > Did you configure /etc/dhcpv6/dhcpc6.cnf with: > duid LL eth0
Which guest OS/dhclient you're referring to? --Sheng > > > > On 1/15/13 7:01 PM, "David Nalley" <da...@gnsa.us> wrote: > >>On Tue, Jan 15, 2013 at 9:10 PM, Sheng Yang <sh...@yasker.org> wrote: >>> On Mon, Jan 14, 2013 at 3:34 PM, Sheng Yang <sh...@yasker.org> wrote: >>>> On Mon, Jan 14, 2013 at 10:51 AM, Sheng Yang <sh...@yasker.org> wrote: >>>>> >>>>> On Mon, Jan 14, 2013 at 10:45 AM, Chiradeep Vittal >>>>> <chiradeep.vit...@citrix.com> wrote: >>>>>> >>>>>> You can if you assume that it is of LL-type. Windows requires a >>>>>>registry >>>>>> fix to generate an 'LL' type DUID. >>>>> >>>>> >>>>> Does dhcp6c support it? Didn't see a word from the document about >>>>>DUID type, >>>>> and it genereate LLT type by default Probably I should try another >>>>>dhcpv6 >>>>> client. >>>>>> >>>>>> >>>>>> You can also get dnsmasq to ignore the duid and use the mac. >>>>> >>>>> >>>>> Haven't confirmed it's possible to use the mac, asking dnsmasq mailing >>>>> list... >>>> >>>> Get answer from Dnsmasq's author Simon, it's impossible to use MAC to >>>> identify client right now, since there is no such dhcpv6 standard. >>>> >>>> So it looks like we need stick to DUID-LL. >>> >>> I am failed to generated DUID-LL from the latest version of dhcp6c in >>> CentOS 5.6. Is DUID-LL poorly supported by dhcpv6 client? Any other >>> suggestion? >>> >>> User may need to install new dhcpv6 client to use with CloudStack, >>> that sounds not that good... >>> >>> I am working on the FS right now, since we have the key steps(except >>> DUID-LL, which should be a dhcpv6 client issue), and likely able to >>> get it done tomorrow. >>> >>> Since we're working on advance shared network, it's easier to deal >>> with createNetwork API rather than createVlanAndIpRange API. >>> >> >>Unless something has changed recently, EL5 had horrendous IPv6 >>support, and many things that should have worked, simply didn't. >> >>--David >
