[Bug 803050] New: Issues with settings for IPv6 in NetworkManager
https://bugzilla.novell.com/show_bug.cgi?id=803050 https://bugzilla.novell.com/show_bug.cgi?id=803050#c0 Summary: Issues with settings for IPv6 in NetworkManager Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: f.de.kruijf@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 In the UI for NetworkManager one can change some settings in connection with automatic generation of the host part of the IPv6 address. There are 3 settings. The default is that this part is generated from the MAC address of the interface. This is not the recommended way, instead this part should be generated randomly and also used as the default source address. Changing this parameter in the UI and pressing OK brings up a hidden prompt for the root password. This prompt should pop-up more prominently. After that the status of the connection shows a restart of that connection. However one need to reboot to make the change effective. There is no warning that this is necessary as is/was present when enabling or disabling IPv6 in the network module of YaST2. Reproducible: Always Steps to Reproduce: 1. Observe the value in /proc/sys/net/ipv6/conf/eth0/use_tempaddr (standard 0) 2. Change the parameter after Privacy Extensions: e.g. to Enabled (prefer temporary addresses) and activate it (obviously this must be a change) 3. Observe the value in /proc/sys/net/ipv6/conf/eth0/use_tempaddr should be changed to 2, however it has not changed 3. reboot 4 Observe the value in /proc/sys/net/ipv6/conf/eth0/use_tempaddr (it should now show 2) Expected Results: At least a warning that the system must be rebooted before the change takes effect. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=803050 https://bugzilla.novell.com/show_bug.cgi?id=803050#c1 Freek de Kruijf <f.de.kruijf@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Issues with settings for |Issues with settings in |IPv6 in NetworkManager |NetworkManager Severity|Normal |Major --- Comment #1 from Freek de Kruijf <f.de.kruijf@gmail.com> 2013-02-21 13:38:25 UTC --- I am also using NetworkManager to set fixed addresses for both IPv4 and IPv6. However after changing one or more of these settings, like an IP address, and not making the mistake to miss the pop-up for the root password, which is hidden behind the NetworkManager window, the new setting(s) are stored in the file(s) in /etc/NetworkManager/system-connections/ but they are not activated. I have to give the command "systemctl restart network.service" to make the new settings active. Maybe one can Disable Networking and enable it again in the widget, to activate the new setting(s), but my expectation is that after clicking OK these new setting(s) become active. Now that NetworkManager is the default after an installation, this should be fixed before the final release, so I raise the priority. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=803050 https://bugzilla.novell.com/show_bug.cgi?id=803050#c Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |os.gnome.maintainers@gmail. |ovo.novell.com |com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=803050 https://bugzilla.novell.com/show_bug.cgi?id=803050#c2 Li Bin <bili@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |bili@suse.com InfoProvider| |f.de.kruijf@gmail.com --- Comment #2 from Li Bin <bili@suse.com> 2013-03-13 02:31:10 UTC --- Freek, Could you check it in Final release? The GM version. Thanks! -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=803050 https://bugzilla.novell.com/show_bug.cgi?id=803050#c3 Freek de Kruijf <f.de.kruijf@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Version|RC 1 |Final InfoProvider|f.de.kruijf@gmail.com | --- Comment #3 from Freek de Kruijf <f.de.kruijf@gmail.com> 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.
https://bugzilla.novell.com/show_bug.cgi?id=803050 https://bugzilla.novell.com/show_bug.cgi?id=803050#c4 --- Comment #4 from Freek de Kruijf <f.de.kruijf@gmail.com> 2013-03-13 22:05:58 UTC --- Again system generated with DVD image. Choose no autoconfiguration, as before and as I always do, YaST sets the default on Traditional after I could log in I started the network using "systemctl start network.service" and I got an IPv4 address via DHCP. However only a link-local IPv6 address. I stopped the network.service, but a ping to the gateway still worked. Did a reboot and the network interface was up, however no global IPv6 address. Somewhat later I did get the two global IPv6 addresses. Searching the log it appears that the IPv6 addresses appeared 10 minutes after getting the IPv4 address. This is obviously a bit off topic, because the bug is about the behavior of NetworkManager. I assume this will be solved when allowing the DHCP6 packets through the firewall. So I changed from traditional to Networkmanager. In the applet the status of IPv6 was Disabled so I changed it to Automatic and Privacy Extensions was set to Enabled (prefer temporary address). Now the interface immediately got the three IPv6 addresses, however each 45 seconds the interface gets restarted because UDP 546 (DHCP6) is dropped in the firewall. I would have expected that the interface did have the above settings already set; it should have a default setting like in the system generated with KDE Live. The reason is that YaST does not generate /etc/NetworkManager/system-settings/<interface name>, so in NM the interface does not have any setting. The above seems to be in contrast to comment 3, but the situation is a bit different. In comment 3 there was no reboot after the first log in. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=803050 https://bugzilla.novell.com/show_bug.cgi?id=803050#c5 Freek de Kruijf <freek@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |FIXED --- Comment #5 from Freek de Kruijf <freek@opensuse.org> 2014-08-07 19:11:03 UTC --- Not an issue anymore. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com