dhcpcd-discuss

Re: 9.3.0 and later can't connect to network with a "Connection refused" message

roy

Thu Oct 29 15:26:06 2020

You might want to pkill -9 any dhcpcd processes between tests as well.

Sent from Nine
________________________________
From: Roy Marples
Sent: Thursday, 29 October 2020 15:04
To: Dudemanguy; dhcpcd-discuss@xxxxxxxxxxxx
Subject: Re: 9.3.0 and later can't connect to network with a "Connection refused" message



On 29/10/2020 14:48, Dudemanguy wrote: 
> On 10/29/20 8:26 AM, Roy Marples wrote: 
>> Or just test git head with -DSECCOMP_FILTER_DEBUG in CPPFLAGS. 
>> The outcome should be the same :) 
> 
> Thanks, I just gave it a whirl and I got this in the log. 
> 
>  >sending commands to dhcpcd process 
>  >ps_seccomp_violation: unexpected syscall 41 (arch=0xc000003e) 

So the syscall is __NR_socket on amd64. 
We don't want to allow that and I do my testing on amd64 ... 
Odd. 

Can you repeat but run under strace -f please like so? 

strace -f dhcpcd $dhcpcd_args 2>/tmp/dhcpcd-strace.log 
Replace $dhcpcd_args with any args you need to send. 

And email me the log file? 

Thanks 

Roy 


Follow-Ups:
Re: 9.3.0 and later can't connect to network with a "Connection refused" messageDudemanguy
References:
Re: 9.3.0 and later can't connect to network with a "Connection refused" messageRoy Marples
Archive administrator: postmaster@marples.name