dhcpcd-discuss

Re: dhcpcd dumplease reports "dhcpcd not running"

Roy Marples

Thu Nov 19 19:19:39 2020

On 19/11/2020 16:49, Matthew Clarkson wrote:
We are using glibc 2.3.0. I'm pretty sure that it is related to the terminal being used. When connected with ssh there is no ioctl call, but when using a serial terminal there is. Also, with TCGETS added to the filter, the strace of the ioctl is ioctl(1, TCGETS, {B115200 opost isig icanon echo ...}) = 0, the third argument is definitely related to our serial port configuration: B115200 is the baud rate. I haven't found the exact line of code, but I feel like it's understandable now.

That's awesome information.

I can't find any use of TCGETS ioctl or the tcgetattr() within glibc itself and I know for sure it's not dhcpcd so I'm don't know how it's actually being called. Still, it's perfectly fine to allow this and I've adjusted the comment so that it contains this rationale.

So far adding fcntl64, fstat64, and TCGETS to the filter is working reliably.

Thanks for the help on this one.

I just provided guidance, you did all the work on this - thanks!

Hopefully a new release over the weekend.

Roy

References:
dhcpcd dumplease reports "dhcpcd not running"Matthew Clarkson
RE: dhcpcd dumplease reports "dhcpcd not running"Matthew Clarkson
Re: dhcpcd dumplease reports "dhcpcd not running"Roy Marples
Re: dhcpcd dumplease reports "dhcpcd not running"Roy Marples
RE: dhcpcd dumplease reports "dhcpcd not running"Matthew Clarkson
Re: dhcpcd dumplease reports "dhcpcd not running"Roy Marples
RE: dhcpcd dumplease reports "dhcpcd not running"Matthew Clarkson
Re: dhcpcd dumplease reports "dhcpcd not running"Roy Marples
RE: dhcpcd dumplease reports "dhcpcd not running"Matthew Clarkson
Re: dhcpcd dumplease reports "dhcpcd not running"Roy Marples
RE: dhcpcd dumplease reports "dhcpcd not running"Matthew Clarkson
Archive administrator: postmaster@marples.name