All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hasso Tepper <hasso@estpak.ee>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: /proc/sys/net/ipv[46]/conf/ issue unsolved
Date: Tue, 13 Feb 2007 22:16:13 +0200	[thread overview]
Message-ID: <200702132216.13828.hasso@estpak.ee> (raw)
In-Reply-To: <20070213090224.2826859f@localhost.localdomain>

Stephen Hemminger wrote:
> > You can disable it in /proc/sys/net/ipv6/conf/default/... and then
> > reenable it on the interfaces that you actually want.

And YOSHIFUJI Hideaki answered to this:

> The point is:
> 
>  - Until we have live address(es), we do not create inet6_dev{} for that
>    device.
>  - We do NOT run DAD until the link is ready (netif_carrier_ok()).
> 
> This means, we do NOT have any addresses until the link is once up,
> and thus, because the sysctl entries live in inet6_dev{}, we do not
> install net.ipv6.conf.ethX from values of net.ipv6.conf.default until
> then.

Ie. to make it very clear - I can't reenable it on the interface before
the first "carrier up" event (cable is plugged on). That's the point -
AFAICS the only way I can configure interface differently than default is
via daemon listening interface events via netlink. I can't do it in any
way before.


regards,

-- 
Hasso Tepper
Elion Enterprises Ltd. [AS3249]
IP & Data Networking Expert

  parent reply	other threads:[~2007-02-13 20:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 13:29 /proc/sys/net/ipv[46]/conf/ issue unsolved Hasso Tepper
2007-02-13 17:02 ` Stephen Hemminger
2007-02-13 18:04   ` Vlad Yasevich
2007-02-13 18:07   ` Hugo Santos
2007-02-13 20:16   ` Hasso Tepper [this message]
2007-02-13 18:58 ` Neil Horman
2007-02-13 19:24   ` Hugo Santos
2007-02-13 19:45     ` Neil Horman
2007-02-13 19:49       ` Hugo Santos
2007-02-13 20:10         ` Neil Horman
2007-02-13 20:18           ` Hugo Santos
2007-02-13 20:29           ` Hasso Tepper
2007-02-13 19:43   ` Vlad Yasevich
2007-02-13 20:15     ` Neil Horman

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=200702132216.13828.hasso@estpak.ee \
    --to=hasso@estpak.ee \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.