dhcpcd-discuss

Hi Roy,

Thanks for the response, and a quick one at that.

On the server in question the Arch release (from uname -r) is 
5.4.8-arch1-1. and dhcpcd --version gives dhcpcd 8.1.5.

To the best of my knowledge, both are pretty well up to date. I have 
attempted to make and keep them so.

I understand the scepticism though. Arch when I took on the server was 
indeed ancient. It is good practice to run pacman -Syy at least as often 
as pacman -Syu to keep the repos up to date as the hosts often backdate 
them to their defaults as they run their maintenance schedules.

Thanks,

Mike


On 09/01/2020 00:20, Roy Marples wrote:
> Hi Mike
>
> On 08/01/2020 21:42, Mike Goodman wrote:
> > Trying to retrieve an IPv6 allocation from a server host. dhcpcd 
> > appears to be set up correctly and is running. However, running the 
> > command systemctl status dhcpcd@enp1s0.service reports running OK then 
> > 10 identical lines containing "Jan 08 22:21:54 sd-136208 dhcpcd[409]: 
> > ipv6_newaddr: Invalid argument"
> >
> > In response and following the ArchWiki dhcpcd page, I commented out 
> > the DUID statement and uncommented the clientid statement in 
> > /etc/dhcpcd.conf, rebooted and got the same response. Not at all sure 
> > it was the right thing to do and I can always change it back again if 
> > wrong.
> >
> > The latest command and output:
> >
> > ~]# systemctl status dhcpcd@enp1s0.service
> > * dhcpcd@enp1s0.service - dhcpcd on enp1s0
> >       Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; 
> > enabled; vendor p>
> >       Active: active (running) since Wed 2020-01-08 21:54:21 CET; 
> > 28min ago
> >      Process: 353 ExecStart=/usr/bin/dhcpcd -q -w enp1s0 (code=exited, 
> > status=0/>
> >     Main PID: 409 (dhcpcd)
> >        Tasks: 1 (limit: 4703)
> >       Memory: 2.2M
> >       CGroup: /system.slice/system-dhcpcd.slice/dhcpcd@enp1s0.service
> >               `-409 dhcpcd: enp1s0 [ip4] [ip6]
> >
> > Jan 08 22:21:54 sd-136208 dhcpcd[409]: ipv6_newaddr: Invalid argument
> > Jan 08 22:21:57 sd-136208 dhcpcd[409]: ipv6_newaddr: Invalid argument
> > Jan 08 22:22:00 sd-136208 dhcpcd[409]: ipv6_newaddr: Invalid argument
> > Jan 08 22:22:04 sd-136208 dhcpcd[409]: ipv6_newaddr: Invalid argument
> > Jan 08 22:22:09 sd-136208 dhcpcd[409]: ipv6_newaddr: Invalid argument
> > Jan 08 22:22:13 sd-136208 dhcpcd[409]: ipv6_newaddr: Invalid argument
> > Jan 08 22:22:18 sd-136208 dhcpcd[409]: ipv6_newaddr: Invalid argument
> > Jan 08 22:22:21 sd-136208 dhcpcd[409]: ipv6_newaddr: Invalid argument
> > Jan 08 22:22:25 sd-136208 dhcpcd[409]: ipv6_newaddr: Invalid argument
> > Jan 08 22:22:30 sd-136208 dhcpcd[409]: ipv6_newaddr: Invalid argument
> >
> > This may be related to an earlier discussion regarding dhcpcd making 
> > multiple rapid requests but I thought that had been fixed. Having said 
> > that, I am not sure I followed the detail correctly as all this is 
> > very new to me.
> >
> > Could/would somebody please point me in the right direction on this?
>
> At a guess you're running an Arch LTS kernel.
> I don't support the unholy mess of an old kernel with new kernel headers.
>
> If you're not, please state running kernel version and dhcpcd version.
>
> Roy