From: "Jan Kundrát" <jkt@flaska.net>
To: "Alexander E. Patrakov" <patrakov@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IPv6: metrics of default routes on different interfaces (Ethernet vs. wifi)
Date: Sun, 28 Aug 2011 20:49:25 +0200 [thread overview]
Message-ID: <4E5A8DB5.2020100@flaska.net> (raw)
In-Reply-To: <4E5A6353.5020202@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
On 08/28/11 17:48, Alexander E. Patrakov wrote:
> It is not in the kernel. You have to grep through the source of whatever
> utility you are using to configure your interfaces. For dhcpcd, the code
> is around line 200 in net.c:
Doh, that completely explains what I'm seeing. The IPv6
autoconfiguration is not handled by userspace at all, AFAIK.
Thanks for correcting my assumptions, now I know where to work further.
With kind regards,
Jan
--
Trojita, a fast e-mail client -- http://trojita.flaska.net/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2011-08-28 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-28 15:02 IPv6: metrics of default routes on different interfaces (Ethernet vs. wifi) Jan Kundrát
2011-08-28 15:48 ` Alexander E. Patrakov
2011-08-28 18:49 ` Jan Kundrát [this message]
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=4E5A8DB5.2020100@flaska.net \
--to=jkt@flaska.net \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox