dhcpcd-discuss

Hi

On 29/10/2020 02:43, Dudemanguy wrote:
> Over at Artix Linux, we recently upgraded dhcpcd from 9.2.0 to 9.3.1 and
> started receiving reports from users that their network connection no
> longer works (happened to myself as well actually). I did a little bit
> of testing myself and found 9.3.0 had the same issue. The logs we get
> from dhcpcd looks something like:
>
>  >2020-10-28 11:32:40.049433743  dhcpcd-9.3.1 starting
>
>  >2020-10-28 11:32:40.058365491  dev: loaded udev
>
>  >2020-10-28 11:32:40.059291853  DUID 
> 00:04:59:12:9a:dd:f0:4f:11:e5:b9:11:62:cb:f2:00:40:19
>
>  >2020-10-28 11:32:40.212571619  in-wireless-0: starting wpa_supplicant
>
>  >2020-10-28 11:32:40.600666932  no interfaces have a carrier
>
>  >2020-10-28 11:32:40.600941554  ps_ctl_listen: read: Success
>
>  >2020-10-28 11:36:02.941921111  dhcpcd_signal_cb: write: Connection refused
>
>  >2020-10-28 11:36:02.990960188  main: control_open: Connection refused
>
> It appears that the dhcpcd master process doesn't get launched and thus,
> no network connection. This so far only appears to affect a subset of
> users. Not sure if this is a total coincidence or not but everyone that
> has reported this uses ipv6 thus far... Any pointers would be
> appreciated.

I suspect this is the new SECCOMP support I added in 9.3.x
SECCOMP sadly has to be programmed for the CPU and even then it's depdendent on 
how libc has been coded for it.
I recently fixed support for PPC64 which may fix your problem as well.
I also added a debugger to allow debugging for it too.

https://roy.marples.name/cgit/dhcpcd.git/commit/?id=b152e3eb9b6db28bb33f169c946a08d292c62af1

If you could test that and if it still fails then add -DSECCOMP_FILTER_DEBUG to 
your CPPFLAGS and rebuild to get dhcpcd to log diagnostics (not recommended for 
production builds).

I aim to release a new version shortly and would appreciate prompt feedback on 
this as I would surely love to have your issue fixed for it.

Roy