netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Bieringer <pb@bieringer.de>
To: Hasso Tepper <hasso@estpak.ee>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC IPv6] Disabling IPv6 autoconf
Date: Tue, 29 Aug 2006 13:31:27 +0200	[thread overview]
Message-ID: <44F4258F.5070406@bieringer.de> (raw)
In-Reply-To: <200608291421.18069.hasso@estpak.ee>

Hasso Tepper schrieb:
> Olaf Kirch wrote:
>> When the Xen people looked for a way to disable IPv6 autoconf of the
>> bridge, they didn't find any way to do it without bringing up the
>> device first (and thereby triggering DAD).
> 
> Because no /proc/sys/net/ipv6/conf/<interface> exist (yes, I know it's 
> user visible effect)? This is just odd IMHO. I asked why it was changed 
> and how userspace should behave now regarding this, but got no answer.
> 
> Simple scenario with GNU/Debian:
> 
> Computer is booted with no ethernet link. Ethernet interface should get 
> address via autoconf. No link => no IPv6 addresses on interface => 
> no /proc/sys/net/ipv6/conf/<interface>. Bootup scripts (procps.sh reading 
> sysctl.conf existing in most of distributions AFAIK) can't set/get 
> anything in /proc/sys/net/ipv6/conf/<interface> because it doesn't exist.
> 
> How userspace should behave now? Mandating daemon which listens interface 
> events via netlink?

BTW: this is also the reason why autoconf or accept_ra cannot be
disabled by e.g. initscripts *per* interface before bringing one up.

This issue was discussed some time ago with Pekka and reported in
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169809

There is still no solution for that afaik.

	Peter
-- 
Dr. Peter Bieringer                     http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D                       mailto:pb@bieringer.de
Deep Space 6 Co-Founder and Core Member  http://www.deepspace6.net/
OpenBC                    http://www.openbc.com/hp/Peter_Bieringer/
Personal invitation to OpenBC  http://www.openbc.com/go/invita/3889

  reply	other threads:[~2006-08-29 11:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29  8:24 [RFC IPv6] Disabling IPv6 autoconf Olaf Kirch
2006-08-29  9:34 ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-29  9:54   ` David Miller
2006-08-29 10:39     ` Herbert Xu
2006-08-29 10:45       ` Olaf Kirch
2006-08-29 10:55     ` Pekka Savola
2006-08-29 11:10       ` Olaf Kirch
2006-08-29 11:13       ` Peter Bieringer
2006-08-29 16:30     ` Alexey Kuznetsov
2006-08-29 10:44   ` Olaf Kirch
2006-08-29 15:51     ` Stephen Hemminger
2006-08-29 11:21 ` Hasso Tepper
2006-08-29 11:31   ` Peter Bieringer [this message]
2006-08-29 13:04     ` Herbert Xu
2006-08-29 13:59       ` Hasso Tepper
2006-08-30  0:12         ` Herbert Xu
2006-08-30  3:26           ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-30  5:41           ` Hasso Tepper
2006-08-29 18:10 ` Thomas Graf
2006-08-29 20:00   ` Olaf Kirch

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=44F4258F.5070406@bieringer.de \
    --to=pb@bieringer.de \
    --cc=hasso@estpak.ee \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).