Re: Timeouts & IPv6 prefix delegation problems
Nickolai Dobrynin
Wed Sep 23 01:02:04 2015
Hi Roy,
Thanks much for the reply - I think I *am*, in fact, getting
DHCPv6 replies. Apparently, my ip6tables were messed
up. They made it look like there were no replies. Please
pardon the confusion. With this said, the new outcome
(i.e. with ip6tables switched off) is all but identical. The
new dhcpcd.log looks unchanged in the beginning and
then:
wlp2s0: soliciting a DHCP lease
# Shouldn't wlp2s0 (LAN) be soliciting a DHCPv6 lease instead?
enp1s10: soliciting a DHCPv6 lease
enp1s10: DHCPv6 REPLY:
# The last 2 lines go on endlessly.
'tcpdump -i enp1s10 ip6' prints ('enp1s10' is my WAN interface):
02:19:56.830282 IP6 Speedport.ip > ff02::1: ICMP6, neighbor
advertisement, tgt is Speedport.ip, length 32
02:19:58.542047 IP6 router > ff02::2: ICMP6, router solicitation, length 16
02:19:58.543047 IP6 Speedport.ip > router: ICMP6, neighbor
solicitation, who has router, length 32
02:19:58.543080 IP6 router > Speedport.ip: ICMP6, neighbor
advertisement, tgt is router, length 24
02:19:58.547533 IP6 Speedport.ip > ff02::1: ICMP6, router
advertisement, length 64
02:19:58.833650 IP6 router.dhcpv6-client > ff02::1:2.dhcpv6-server:
dhcp6 solicit
02:19:58.839224 IP6 Speedport.ip.49520 > router.dhcpv6-client: dhcp6 reply
# The last 2 lines appear many many times.
(Speedport.ip is the modem I got from the ISP).
For the last two lines of the config, i.e.
#ia_pd 1 wlp2s0
ia_pd 1/::/64 wlp2s0/0/64
I tried using the first line only, then the second one only - NO DIFFERENCE.
My routing prefixes are always 64 bits long, so perhaps the second line makes
more sense?
Thanks again,
Nickolai
On Tue, Sep 22, 2015 at 11:35 PM, Roy Marples <roy@xxxxxxxxxxxx> wrote:
> Hi Nickolai
>
>
> On 2015-09-22 02:23, Nickolai Dobrynin wrote:
>>
>> I am running dhcpcd-6.9, and I can't get
>> IPv6 prefix delegation working. I have two interfaces:
>> 'enp1s10' for WAN, 'wlp2s0' for LAN (and 'enp3s0'
>> which is unused).
>>
>> At some point during boot, dhcpcd hangs, forks into
>> background, and no prefix gets delegated to wlp2s0:
>>
>> Sep 22 02:35:26 dev: loaded udev
>> Sep 22 02:35:26 enp3s0: adding address fe80::bd54:908d:64f5:41f0
>> Sep 22 02:35:26 enp1s10: adding address fe80::7376:ac2d:a96a:6a6f
>> Sep 22 02:35:26 wlp2s0: adding address fe80::608f:65e4:4fa2:b831
>> Sep 22 02:35:26 enp3s0: waiting for carrier
>> Sep 22 02:35:26 enp1s10: waiting for carrier
>> Sep 22 02:35:26 wlp2s0: waiting for carrier
>> Sep 22 02:35:26 wlp2s0: carrier acquired
>> Sep 22 02:35:26 DUID 00:01:00:01:1d:7a:83:94:00:15:f2:d4:79:34
>> Sep 22 02:35:26 wlp2s0: IAID 93:54:1d:3e
>> Sep 22 02:35:26 wlp2s0: carrier lost
>> Sep 22 02:35:26 wlp2s0: deleting address fe80::608f:65e4:4fa2:b831
>> Sep 22 02:35:29 enp1s10: carrier acquired
>> Sep 22 02:35:29 enp1s10: IAID 00:00:00:01
>> Sep 22 02:35:29 enp1s10: rebinding lease of 192.168.2.107
>> Sep 22 02:35:29 enp1s10: leased 192.168.2.107 for 1814400 seconds
>> Sep 22 02:35:29 enp1s10: adding route to 192.168.2.0/24
>> Sep 22 02:35:29 enp1s10: adding default route via 192.168.2.1
>> Sep 22 02:35:30 enp1s10: soliciting an IPv6 router
>> Sep 22 02:35:31 enp1s10: soliciting a DHCPv6 lease
>> Sep 22 02:35:31 enp1s10: Router Advertisement from fe80::1
>> Sep 22 02:35:31 enp1s10: adding address
>> 2003:56:ce64:dc90:a703:3afe:75fa:da67/64
>> Sep 22 02:35:31 enp1s10: adding route to 2003:56:ce64:dc90::/64
>> Sep 22 02:35:31 enp1s10: adding default route via fe80::1
>> Sep 22 02:35:56 timed out
>> Sep 22 02:35:56 forked to background, child pid 1776
>> Sep 22 02:35:57 control command: dhcpcd -m 3 enp1s10
>> Sep 22 02:35:58 wlp2s0: carrier acquired
>> Sep 22 02:35:58 wlp2s0: adding address fe80::e92b:ce84:16b3:90c0
>> Sep 22 02:35:58 wlp2s0: IAID 93:54:1d:3e
>> Sep 22 02:35:58 wlp2s0: soliciting a DHCP lease
>> Sep 22 02:36:08 wlp2s0: using IPv4LL address 169.254.43.159
>> Sep 22 02:36:08 wlp2s0: adding route to 169.254.0.0/16
>> Sep 22 02:36:08 wlp2s0: removing route to 169.254.0.0/16
>
>
> Looks to me like you didn't receive any DHCPv6 reply, which is the reason
> why.
> Can you verify this with a tcpdump?
>
>> My dhcpcd.conf is:
>>
>> hostname
>> duid
>> persistent
>> option rapid_commit
>> option domain_name_servers, domain_name, domain_search, host_name
>> option classless_static_routes
>> option ntp_servers
>> require dhcp_server_identifier
>> slaac private
>> nohook lookup-hostname
>>
>> # The stuff below was suggested by
>> #
>> https://wiki.archlinux.org/index.php/IPv6#Prefix_delegation_.28DHCPv6-PD.29
>> noipv6rs
>> waitip 6
>>
>> interface enp1s10
>> ipv6rs
>> iaid 1
>>
>> #ia_pd 1 wlp2s0
>> ia_pd 1/::/64 wlp2s0/0/64
>
>
> Looks fine.
> I'm going to guess it doesn't work either with the ia_pd 1 wlp2s0 line
> uncommented and the other commented out?
>
> Roy
Archive administrator: postmaster@marples.name