https://bugzilla.novell.com/show_bug.cgi?id=803050
https://bugzilla.novell.com/show_bug.cgi?id=803050#c3
Freek de Kruijf changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Version|RC 1 |Final
InfoProvider|f.de.kruijf@gmail.com |
--- Comment #3 from Freek de Kruijf 2013-03-13 13:10:20 UTC ---
I will check it in several distributions.
First: KDE Live
NetworkManager applet shows IPv6 disabled, however "ip a" shows a global IPv6
address derived from MAC address.
After setting Disabled to Automatic nothing changed in "ip a".
The Privacy Extensions shows Disabled
Changing Privacy Extensions to Enabled (prefer temporary address), which should
be the default, does not change the status of the network. I have to give the
command "systemctl restart network.service" to make it effective.
During this command I left the applet window open, but I had to close and open
it again to be able to edit "Wired connection 1" again.
Second: system generated with KDE Live
After generating the system I got a system without NetworkManager, but after
giving the published systemctl commands to enable NetworkManager, and starting
the network, without a reboot, I got a network with IPv6 in status Automatic
and with Privacy Extensions set to Enabled (prefer temporary address). So this
is OK with NetworkManager enabled.
I changed, using Network module of YaST, from managed by NetworkManager to
Traditional and back and in both situation the default of prefer temporary
address is used. So OK.
Third: system generated with DVD image
The situation is quite confusing.
I generated a system and during the generation I changed the network setting
from Traditional to NetworkManager. Due to the other bug the network was not up
after YaST finished. So I started the network using "systemctl start
network.service". I checked /proc/sys/net/ipv6/conf/eth0/use_tempaddr, which
was 2. However I did not have any global IPv6 address, only the link-local.
After that I changed in YaST from Traditional to NetworkManager and the applet
appeared immediately. Nothing changed in the output of "ip a", no global IPv6
address.
After that I did a generation and left Traditional as it was set. During the
second stage of YaST I checked on tty2 and noticed three IPv6 addresses,
including the random generated temporary address. Also the online update was
OK. After logging in obviously no active network due to other bug. Activating
the network with "systemctl start network.service" showed a net work with a
global IPv6 address derived from the MAC address, no third address.
I changed from Traditional to NetworkManager in YaST and observed the same. Now
it appears in the applet that IPv6 was Disabled, so I changed to Automatic and
prefer temporary address and IPv6 needed. After that no temporary address and
an unstable network. Only after inserting
FW_SERVICES_ACCEPT_EXT="fe80::/64,udp,546" in /etc/sysconfig/SuSEfirewall2, and
activating it, the interface became stable. This is another reported bug.
I restored the original SuSEfirewall2. After that I went back to Traditional in
YaST: three IPv6 addresses. Changed to NetworkManager: three IPv6 address
stable interface. So quite confusing.
Will repeat what I did with the DVD image and report later
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
