From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: if_nameindex/getifaddrs and dhcpcd issue
Date: Tue, 8 Apr 2014 11:38:41 -0400 [thread overview]
Message-ID: <20140408153840.GF26358@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAK4o1WzD22w+U6i_WyWQS3jXhx=kBm8jk1at-QPXru5hJB5ZwA@mail.gmail.com>
On Tue, Apr 08, 2014 at 03:16:10PM +0100, Justin Cormack wrote:
> On Tue, Apr 8, 2014 at 2:42 PM, Rich Felker <dalias@aerifal.cx> wrote:
> >> and it only needs to read ipv4 addresses,
> >> unless it is implementing dhcp6 too, maybe it does now. Again dhcp6
> >> needs netlink, the Musl ipv6 parts for getifaddrs already use /proc
> >> which is definitely unreliable for early boot config in a distro in my
> >> view.
> >
> > In what way does dhcp6 need netlink? What's made this discussion
> > difficult so far on IRC is assertions of that form (although not the
> > same one) without an explanation of why it's believed to be true, so
> > I'd like to keep rational discussion possible by making sure that such
> > claims are backed up by explanation rather than just stated as fact.
>
> I was under the impression that the ioctl-based interface for ipv6 is
> incomplete under Linux.
Probably "incomplete" in a sense that it can't do some special-purpose
stuff that most users don't need. Busybox entirely avoids netlink, as
far as I can tell, and it's perfectly acceptable for setting up ipv6,
at least in simple setups. You don't even need busybox's iproute2
workalikes; ifconfig and route work fine.
> That does not mean anything needs to be in
> libc though. ISC dhcp for v6 just calls out to ip in scripts, rather
> than ifconfig that it uses for v4, so it is indirectly uses netlink,
> but does not require any libc support, indeed all the C code is
> portable.
udhcpcd works the same; it doesn't make any changes to the interfaces;
it just speaks the dhcp protocol. This is really the correct
factorization.
Rich
next prev parent reply other threads:[~2014-04-08 15:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 9:11 Natanael Copa
2014-04-08 10:07 ` Justin Cormack
2014-04-08 12:25 ` Timo Teras
2014-04-08 14:23 ` Natanael Copa
2014-04-08 15:45 ` Rich Felker
2014-04-08 16:08 ` Timo Teras
2014-04-08 16:19 ` Justin Cormack
2014-04-08 22:41 ` Rich Felker
2014-04-09 7:17 ` u-igbb
2014-04-09 22:20 ` Rich Felker
2014-04-09 22:32 ` Justin Cormack
2014-04-10 7:40 ` u-igbb
2014-04-10 7:52 ` Rich Felker
2014-04-09 14:02 ` Timo Teras
2014-04-10 0:55 ` Rich Felker
2014-04-09 7:55 ` Natanael Copa
2014-04-08 12:54 ` Szabolcs Nagy
2014-04-08 13:42 ` Rich Felker
2014-04-08 14:16 ` Justin Cormack
2014-04-08 15:38 ` Rich Felker [this message]
2014-04-09 7:13 ` Natanael Copa
2014-04-09 22:18 ` Rich Felker
2014-04-08 21:16 ` Natanael Copa
2014-04-08 21:30 ` Justin Cormack
2014-04-08 22:59 ` Rich Felker
2014-04-08 14:27 ` Natanael Copa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140408153840.GF26358@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).