From: Hasso Tepper <hasso@estpak.ee>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Hugo Santos <hugosantos@gmail.com>, netdev@vger.kernel.org
Subject: Re: /proc/sys/net/ipv[46]/conf/ issue unsolved
Date: Tue, 13 Feb 2007 22:29:57 +0200 [thread overview]
Message-ID: <200702132229.58111.hasso@estpak.ee> (raw)
In-Reply-To: <20070213201006.GG25362@hmsreliant.homelinux.net>
Neil Horman wrote:
> 5) the ifup $DEVICE from (4) goes through the network interface bring up
> process, and consequently sends the ioctl SIOCSIFFLAGS to the kernel, setting
> the IFF_UP flag on the appropriate interface, kicking of whatever default
> processes need to be as defined by the settings found in
> /proc/sys/net/conf/<interface>/*
... which is created _only_ if address of specific address familiy exists
already. If address is obtained via IPv6 autoconf (very common case for
IPv6 hosts) or via IPv4/IPv6 DHCP with netlink aware mechanism (also very
common nowadays - network manager) you don't have any addresses on interface
at this point therefore /proc/sys/net/ipv[46]/conf/<interface>/ are NOT
created. That's the point - you can't configure anything before the first
"carrier up" event - ie. cable is plugged on.
regards,
--
Hasso Tepper
Elion Enterprises Ltd. [AS3249]
IP & Data Networking Expert
next prev parent reply other threads:[~2007-02-13 20:30 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
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 [this message]
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=200702132229.58111.hasso@estpak.ee \
--to=hasso@estpak.ee \
--cc=hugosantos@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).