dhcpcd-discuss

Roy Marples wrote:
> Ed W wrote:
> > Additional:  It appears that you need both UCLIBC_USE_NETLINK=y and 
> > UCLIBC_SUPPORT_AI_ADDRCONFIG=y in your uclibc config
> >
> > ...Unfortunately when I enable the second option then I'm getting 
> > segfaults whenever I try and do anything network related which 
> > actually uses the device, eg ifconfig is fine, bringing up the 
> > interface is fine, but "ping" segfaults, as does "telnet".
> >
> > dhcpcd I think is working fine (oddly enough), and I can't reproduce 
> > this on my build environment (which is fairly similar bar the kernel)
> >
> > Clearly this is unrelated to dhcpcd now, and may well be a kernel 
> > option related issue, but perhaps someone has some ideas where to 
> > look?  Obviously it's going to be a pain to turn on symbols and try 
> > to get a backtrace on the embedded board
> >
> > For ref this is a gentoo+hardened kernel, with a hardened gcc3.4 
> > toolchain, uclibc 0.30.1 + bb 0.14.2
> >
> > Anyone got any ideas on what to check or perhaps experienced 
> > something similar...

Just for the benefit of the archives, the solution to this problem was a 
uclibc issue:

The issue is already fixed in svn uclibc, but for some reason it didn't 
make it into uclibc 0.9.30.1

http://lists.uclibc.org/pipermail/uclibc-cvs/2008-December/025767.html

Gentoo bug filed here:
http://bugs.gentoo.org/show_bug.cgi?id=278610


Ed W