lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 2 Jun 2007 20:01:32 +1000
From:	Herbert Xu <>
To:	"David S. Miller" <>,
Subject: [0/4] [IPV4]: Fix compatibility issue with ipv4_devconf_dflt

Hi Dave:

When we moved the IPv4/IPv6 device creation from address addition time
to device registration time it changed the behaviour of the default
configuration values (e.g., /proc/sys/net/ipv4/conf/default).  Previously
you could specify default configuration values and as long as you do it
before any addresses are added (or when the device is brought up for IPv6)
it would apply to every single device other than loopback.

With the new scheme this no longer works for devices registered at boot
time (e.g., devices built-in to the kernel).  One such scenario can be
seen at

Since this is a kernel/user-space interface it'd be nice if we can keep
the compatibility while still achieving what we wanted.

The following series tries to do that for IPv4 by keeping track of what
the user has explicitly set and copying the default values over again
at the same points as before for values which have not been explicitly

If this looks OK I'll do the same thing for IPv6 as well.

Visit Openswan at
Email: Herbert Xu ~{PmV>HI~} <>
Home Page:
PGP Key:
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists