Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=250919
--- Comment #45 from Peter Bieringer <pb(a)bieringer.de> 2011-04-28 16:18:13 EDT ---
Regarding
https://bugzilla.redhat.com/show_bug.cgi?id=250919#c43
using udev for setting the sysctl toggle for IPv6 privacy won't work on Fedora
14 out-of-the-box:
the IPv6 module is loaded by initial RAM disk *after* udev initialization,
means if e.g. an udev rule like following
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*",
RUN+="sysctl net.ipv6.conf.%k.use_tempaddr=2"
won't work.
The only workaround I found was:
- create a new RAM disk with "--with ipv6"
- extend boot option with "rdloaddriver=ipv6"
- use full qualified path for sysctl
So udev initialization is imho no option at all for setting IPv6 privacy,
especially, if this should be controllable per device.
If one would use the udev mechanism for per interface settings, each time a new
RAM disk must be created...
Imho, ifcfg-INTERFACE would be still a good location for such interface
settings to keep configuration in one place.
Regarding
https://bugzilla.redhat.com/show_bug.cgi?id=250919#c44
In an extended version of ifup-ipv6 (on deepspace6), another "privacy" mode is
supported, which is based on setting a random private MAC address on the
interface before bringing up. Therefore the intention of using "rfc3041" as
method was that IPV6_PRIVACY should be flexible to support others than the RFC
3041 one.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.