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.