Re: RC3 trouble?
Roy Marples
Thu Dec 07 17:08:19 2017
On 07/12/2017 07:55, Neal P. Murphy wrote:
Did I screw up the kernel config this time? I had to redo the config so the kernel would run on the Atom N270 I have; I may've botched something else in it.
Built rc4 just like rc3, definitely using 3.4.x kernel headers. Built and installed the latest SWE3.1-SP4 build running Linux 3.16.51.
...
Dec 07 01:52:35 [18035]: dhcpcd-7.0.0-rc4 starting
Dec 07 01:52:35 [18035]: eth3: if_disable_autolinklocal: Operation not supported
If the headers match or are older than the kernel, I really don't
understand why you see that error :/
Dec 07 01:52:35 [18035]: dhcp6_listen: Address already in use
Wait, what's that 'address already in use' doing there? Both rc3 and rc4 do that. 'ss -ln' yields:
----
udp UNCONN 0 0 fe80::290:bff:fe17:f27d%eth3:546 :::*
Oho! "/usr/sbin/dhcpcd -4 ...." opens that socket. Replace that prog with rc3 and....
Nice find!
Fixed in b86b4ac47fa09edafa6ce3c009751557fe1a6138
With the ipv4-only not opening ipv6, I get:
----
dhcpcd-7.0.0-rc4 starting
eth3: if_disable_autolinklocal: Operation not supported
eth0: executing `/etc/rc.d/rc.update6red' PREINIT
eth0: executing `/etc/rc.d/rc.update6red' CARRIER
eth1: executing `/etc/rc.d/rc.update6red' PREINIT
eth1: executing `/etc/rc.d/rc.update6red' NOCARRIER
eth2: executing `/etc/rc.d/rc.update6red' PREINIT
eth2: executing `/etc/rc.d/rc.update6red' CARRIER
eth3: executing `/etc/rc.d/rc.update6red' PREINIT
eth3: executing `/etc/rc.d/rc.update6red' CARRIER
DUID 00:01:00:01:21:ba:a9:8c:00:90:0b:17:f2:7d
eth0: IAID 0b:17:f2:7a
eth2: IAID 0b:17:f2:7c
eth3: IAID 0b:17:f2:7d
eth3: IAID 4b:17:f2:7d
eth3: IAID 00:00:00:01
eth3: delaying IPv6 router solicitation for 1.0 seconds
eth3: reading lease `/var/db/dhcpcd/eth3.lease6'
eth3: soliciting a DHCPv6 lease
eth3: delaying SOLICIT6 (xid 0x664120), next in 0.6 seconds
eth1: waiting for carrier
eth3: broadcasting SOLICIT6 (xid 0x664120), next in 1.1 seconds
eth3: soliciting an IPv6 router
eth3: sending Router Solicitation
eth3: broadcasting SOLICIT6 (xid 0x664120), next in 2.2 seconds
eth3: Router Advertisement from fe80::201:5cff:fe8e:ea46
eth3: adding default route via fe80::201:5cff:fe8e:ea46
eth3: executing `/etc/rc.d/rc.update6red' ROUTERADVERT
eth3: broadcasting SOLICIT6 (xid 0x664120), next in 4.4 seconds
eth3: ADV 2001:558:6036:65:8d7e:3f36:aa01:26cc/128 from fe80::201:5cff:fe8e:ea46
eth3: broadcasting REQUEST6 (xid 0x2545a1), next in 1.1 seconds
eth3: accepted reconfigure key
eth3: REPLY6 received from fe80::201:5cff:fe8e:ea46
eth3: adding address 2001:558:6036:65:8d7e:3f36:aa01:26cc/128
eth3: pltime 3600 seconds, vltime 3600 seconds
eth3: renew in 1800, rebind in 2880, expire in 3600 seconds
lo: adding reject route to 2601:5ca:4400:960::/60
eth3: writing lease `/var/db/dhcpcd/eth3.lease6'
eth3: delegated prefix 2601:5ca:4400:960::/60
eth0: adding address 2601:5ca:4400:962::1/64
eth0: pltime 3600 seconds, vltime 3600 seconds
eth0: waiting for DHCPv6 DAD to complete
eth2: adding address 2601:5ca:4400:964::1/64
eth2: pltime 3600 seconds, vltime 3600 seconds
eth2: waiting for DHCPv6 DAD to complete
eth1: has no carrier, cannot delegate addresses
eth0: adding route to 2601:5ca:4400:962::/64
eth2: adding route to 2601:5ca:4400:964::/64
eth3: waiting for DHCPv6 DAD to complete
eth3: DHCPv6 DAD completed
eth3: executing `/etc/rc.d/rc.update6red' BOUND6
..DHCP6 lease bound (BOUND6) and prefix delegated; update RED6 info
forking to background
forked to background, child pid 21990
----
Looks better.
When I stopped it, dhcpcd left the /64 on eth3 but removed the /128 and removed the /64s on eth0 and eth2. It also left these routes behind:
----
2001:558:6036:65:8d7e:3f36:aa01:26cc dev eth3 proto kernel metric 256 expires 3347sec
2601:5ca:4400:960::/64 dev eth3 proto kernel metric 256
unreachable 2601:5ca:4400:960::/60 dev lo proto dhcp metric 201 error -101
----
I still can't replicate that.
Could you clear the addresses and routing (or just reboot the box) and
retest please?
Ideally with the latest git head with the fixes in.
If it fails, the same dhcpcd log as the what you have here is also neeed!
Thanks
Roy
Archive administrator: postmaster@marples.name