Re: DHCPv6 Rapid Commit
Nick Williams
Wed Feb 03 12:47:20 2016
> On Feb 3, 2016, at 4:51 AM, Roy Marples <roy@xxxxxxxxxxxx> wrote:
>
> Hi Nicholas
>
> On 02/02/2016 15:47, Nicholas Williams wrote:
>> So, something isn't right I don't //think// I'm doing something wrong,
>> but it sure seems like it. Or there's a bug? I put this in my
>> configuration file:
>>
>> interface eth2
>> option subnet_mask
>> option broadcast_address
>> option routers
>> option domain_name_servers
>> option domain_search
>> option domain_name
>> option interface_mtu
>> dhcp6_option name_servers
>> dhcp6_option domain_search
>
> option dhcp6_name_servers
> option dhcp6_domain_search
OHHHHHHHH! I’ve been misunderstanding the documentation all along and putting the dhcp6_ //before// “option” and “nooption.” I assume, then, than it’s actually supposed to be “nooption dhcp6_name_servers”, not “dhcp6_nooption name_servers?” LOL [hangs head in shame]
>> And it had this result:
>>
>> $ sudo dhcpcd eth2
>> unknown option: dhcp6_option
>> unknown option: dhcp6_option
>> DUID 00:01:00:01:1e:43:88:3a:08:00:27:21:d4:16
>> eth2: IAID 27:21:d4:16
>> eth2: soliciting an IPv6 router
>> eth2: Router Advertisement from fe80::87:17f5:6412:6666
>> eth2: adding address 2600:1004:b140:f81a:a00:27ff:fe21:d416/64
>> eth2: requesting DHCPv6 information
>> eth2: rebinding lease of 172.20.10.6
>> eth2: probing address 172.20.10.6/28 <http://172.20.10.6/28>
>> forked to background, child pid 3013
>>
>> For some reason, dhcpcd doesn't recognize the dhcp6_option settings?
>>
>> But I can get and use an IPv6 address through dhcpcd, so clearly it's
>> not somehow compiled without DHCPv6 support.
>
> Going to guess that you've requested IA_PD but not IA_NA?
> Try requesting both.
> If it still fails, save me from guessing and attach your full
> dhcpcd.conf please.
> Also, please attach all logs including after forking, because your log
> snippet showed working DHCPv4 only, which we're not interested in.
Well the problem is probably moot now, since I was putting the dhcp6_ in the wrong place. Nevertheless, that _was_ my entire dhcpcd.conf file above. I’ll respond to the other thread with long information, because that’s the only problem I’m still having.
Thanks,
Nick
Archive administrator: postmaster@marples.name