dhcpcd-discuss

Hi

On 05/05/2017 22:25, JED wrote:
> I'm trying to shoot a bug on my Raspberry Pi where dhcpcd has SEGV when
> I convert root file system to f2fs. Why running on f2fs instead of ext4
> breaks dhcpcd I have NO idea, but I'm not sure I care. BTW, I get this:
> > May  4 01:27:33 rasp8apr systemd[1]: dhcpcd.service: main process
> > exited, code=killed, status=11/SEG

Well, I'd need a backtrace to fix that.

> I'm trying 7.0.0-beta3 to avoid shooting an old bug, since the latest
> Raspbian
> > Raspbian Jessie with PIXEL
> > Image with PIXEL desktop based on Debian Jessie
> > Version: April 2017
> > Release date: 2017-04-10
> > Kernel version: 4.4
> uses
> > root@rasp8apr:~# dhcpcd --version
> > dhcpcd 6.7.1
> > Copyright (c) 2006-2015 Roy Marples
> and you've fixed LOTS of things since then. If this is the wrong way to
> proceed, I'm ready for any suggestions.
>
> However
> > root@rasp8apr:~/dhcpcd-7.0.0-beta3# ./configure
> > configure args:
> > Deriving operating system from ... armv7l-unknown-linux
> > Configuring dhcpcd for ... linux
> > Enabling INET support
> > Enabling ARP support
> > Enabling ARPing support
> > Enabling IPv4LL support
> > Enabling INET6 support
> > Enabling DHCPv6 support
> > Enabling Authentication
> > Using compiler .. cc
> > cc (Raspbian 4.9.2-10) 4.9.2
> > dhcpcd-definitions.conf will be embedded in dhcpcd itself
> > Testing for nl80211 ... yes
> > Testing for IN6_ADDR_GEN_MODE_NONE ... no
> > Testing for getifaddrs ... no
> > libc support for getifaddrs is required - aborting
>
> What do I need do to fix this? Web searches turned up this message in
> different versions of this script but no answers.

Post your config.log file, either as an attachment here or to 
https://dev.marples.name/paste/

That will hopefully tell us why it fails to detect it in libc.

> BTW: Your ftp server seems to not support passive ftp, perhaps because
> of closed ports. I just used https instead. Example of that problem, but
> you probably don't care too much and I worked around it...
> > root@rasp8apr:~# wget
> > ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0-beta3.tar.xz
> > converted
> > 'ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0-beta3.tar.xz'
> > (ISO-8859-1) ->
> > 'ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0-beta3.tar.xz' (UTF-8)
> > --2017-05-05 12:33:06--
> > ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0-beta3.tar.xz
> >            => 'dhcpcd-7.0.0-beta3.tar.xz'
> > Resolving roy.marples.name (roy.marples.name)... 81.108.15.115
> > Connecting to roy.marples.name (roy.marples.name)|81.108.15.115|:21...
> > connected.
> > Logging in as anonymous ... Logged in!
> > ==> SYST ... done.    ==> PWD ... done.
> > ==> TYPE I ... done.  ==> CWD (1) /pub/dhcpcd ... done.
> > ==> SIZE dhcpcd-7.0.0-beta3.tar.xz ... 203440
> > ==> PASV ... couldn't connect to 10.73.2.61 port 49001: Connection
> > timed out
> > Retrying.
> >
> > --2017-05-05 12:35:20--
> > ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0-beta3.tar.xz
> >   (try: 2) => 'dhcpcd-7.0.0-beta3.tar.xz'
> > Connecting to roy.marples.name (roy.marples.name)|81.108.15.115|:21...
> > connected.
> > Logging in as anonymous ... Logged in!
> > ==> SYST ... done.    ==> PWD ... done.
> > ==> TYPE I ... done.  ==> CWD (1) /pub/dhcpcd ... done.
> > ==> SIZE dhcpcd-7.0.0-beta3.tar.xz ... 203440
> > ==> PASV ... couldn't connect to 10.73.2.61 port 49005: Connection
> > timed out
> > Retrying.
> Just to see, I later told wget --no-passive-ftp and that works, too. It
> just took me a while to find that option in the 1440 lines of man file,
> since PASV wasn't in there and I had to remember exactly what that was
> about. Memory is the second thing to go.

PASV works from all remote hosts I have access to back to my host.... I 
don't know why it fails for you.
I'll try opening more ports and see if that helps.

Roy