dhcpcd-discuss

On 2020-05-06.09:08, Scott Leggett wrote:
> On 2020-05-05.20:07, Roy Marples wrote:
> > On 05/05/2020 19:03, Roy Marples wrote:
> > > On 05/05/2020 17:40, Scott Leggett wrote:
> > > > Hi,
> > > > 
> > > > I've noticed some interesting behaviour in dhcpcd 9.0.2.
> > > > 
> > > > I was investigating a series of log messages like this:
> > > > 
> > > >    May 05 20:55:00 gateway dhcpcd[7402]: enp1s0: failed to renew DHCP, rebinding
> > > >    May 05 21:21:15 gateway dhcpcd[7402]: enp1s0: failed to renew DHCP, rebinding
> > > >    May 05 21:47:30 gateway dhcpcd[7402]: enp1s0: failed to renew DHCP, rebinding
> > > >    May 05 22:13:45 gateway dhcpcd[7402]: enp1s0: failed to renew DHCP, rebinding
> > > 
> > > I have replicated that also with privsep disabled but not with the
> > > default of it enabled.
> > > 
> > > Is your dhcpcd setup for privsep?
> 
> You are correct, privsep is disabled in my build.
> 
> The reason I have disabled privsep is that I'm using systemd on linux.
> While the separate process running as an unprivileged user is nice, the
> chroot behaviour is basically redundant in my case and it means I have
> to allow chroot() and mount() syscalls in the service's namespace.
> 
> > Fixed here:
> > https://roy.marples.name/cgit/dhcpcd.git/commit/?id=904b0f7288119a7ddcd9aa862530746031cb9e36
> 
> Thanks for they very quick response! I'll try the patch and report back.
> 

I've tried this (built from current master at
dhcpcd-9.0.2-39-g6c1e0dbd), and I still get both odd behaviours: The
weird source port, and the error log.

I'll try doing a bisect to figure out where this behaviour started.

-- 
Regards,
Scott Leggett.

Attachment: signature.asc
Description: PGP signature