Hi,
On 2/13/07, Stephen Hemminger [EMAIL PROTECTED] wrote:
You can disable it in /proc/sys/net/ipv6/conf/default/... and then
reenable it on the interfaces that you actually want.
Is there any technical reason to not have the sysconf entries
available at interface creation? It seems to me
Neil,
On 2/13/07, Neil Horman [EMAIL PROTECTED] wrote:
Can't this simply be fixed by adding a custom udev rule? Correct me if I'm
wrong, but the only reason that interfaces come up automatically after their
appropriate module is inserted is because most distos udev rules issue an ifup
$DEVICE
Yes, I understand that, but until the IFF_UP flag is set on the interface, it
doesn't really have any effect on the system as a whole. You should be able to
undo any default setting that you want before you call ifup on the interface, or
am I missing something?
If i understand what you are
On Tue, Feb 13, 2007 at 07:49:50PM +, Hugo Santos wrote:
Yes, I understand that, but until the IFF_UP flag is set on the interface,
it
doesn't really have any effect on the system as a whole. You should be
able to
undo any default setting that you want before you call ifup on the
On 2/13/07, Neil Horman [EMAIL PROTECTED] wrote:
1) Kernel network driver X detects that it has hardware to drive, and
consequently calls register_netdev. This creates the network interface and
registers all the appropriate proc and sysfs files, which are now accessible in
user space.
The
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
There is long standing issue in kernel which makes using /etc/sysctl.conf
useless for boottime configuration of specific interface properties and
breaks probably any software relying on unconditional existence of the
conf trees like it was in previous kernels (I alone have written several
pieces
On Tue, 13 Feb 2007 15:29:04 +0200
Hasso Tepper [EMAIL PROTECTED] wrote:
There is long standing issue in kernel which makes using /etc/sysctl.conf
useless for boottime configuration of specific interface properties and
breaks probably any software relying on unconditional existence of the
Stephen Hemminger wrote:
On Tue, 13 Feb 2007 15:29:04 +0200
Hasso Tepper [EMAIL PROTECTED] wrote:
There is long standing issue in kernel which makes using /etc/sysctl.conf
useless for boottime configuration of specific interface properties and
breaks probably any software relying on
On Tue, Feb 13, 2007 at 03:29:04PM +0200, Hasso Tepper wrote:
There is long standing issue in kernel which makes using /etc/sysctl.conf
useless for boottime configuration of specific interface properties and
breaks probably any software relying on unconditional existence of the
conf trees like
Neil Horman wrote:
On Tue, Feb 13, 2007 at 03:29:04PM +0200, Hasso Tepper wrote:
There is long standing issue in kernel which makes using /etc/sysctl.conf
useless for boottime configuration of specific interface properties and
breaks probably any software relying on unconditional existence of
On Tue, Feb 13, 2007 at 02:43:32PM -0500, Vlad Yasevich wrote:
Neil Horman wrote:
On Tue, Feb 13, 2007 at 03:29:04PM +0200, Hasso Tepper wrote:
There is long standing issue in kernel which makes using /etc/sysctl.conf
useless for boottime configuration of specific interface properties and
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.
-
13 matches
Mail list logo
