https://bugzilla.novell.com/show_bug.cgi?id=704666 https://bugzilla.novell.com/show_bug.cgi?id=704666#c2 --- Comment #2 from Freek de Kruijf 2011-07-12 20:41:58 UTC --- I did the procedure again, but now the IPv6 address did not appear after starting Firefox. It took ~6 minutes before the IPv6 global address appeared. See the following log: Jul 12 21:27:01 eik114 avahi-daemon[1933]: Registering new address record for fe80::e2cb:4eff:fecd:d7b6 on eth0.*. Jul 12 21:27:01 eik114 avahi-daemon[1933]: Registering new address record for 192.168.1.32 on eth0.IPv4. Jul 12 21:33:46 eik114 avahi-daemon[1933]: Registering new address record for 2001:980:7480:1:e2cb:4eff:fecd:d7b6 on eth0.*. Jul 12 21:33:46 eik114 avahi-daemon[1933]: Withdrawing address record for fe80::e2cb:4eff:fecd:d7b6 on eth0. -- 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=704666 https://bugzilla.novell.com/show_bug.cgi?id=704666#c4 --- Comment #4 from Freek de Kruijf 2011-07-18 20:47:02 UTC --- After reading the man page "man ifcfg" I changed the file /etc/sysconfig/network/ifcfg-eth0 into: BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.1.40/24' IPADDR_1='2001:980:7480:1:192:168:1:40/64' SCOPE_1='global' MTU='' NAME='82540EM Gigabit Ethernet Controller' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='nfsroot' USERCONTROL='no' After "ifdown eth0" and "ifup eth0" the eth0 does have three global IPv6 addresses; the two in the previous comment and the newly specified one. -- 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=704666 https://bugzilla.novell.com/show_bug.cgi?id=704666#c6 --- Comment #6 from Freek de Kruijf 2011-07-18 21:27:32 UTC --- I would suggest to add some explaining text in the dialog for adding extra interface IPv6 addresses and behind the Help button on that dialog. I did not get any information on the default gateway for IPv6 from my ISP. So I entered the the first 64 bits in hex followed by :: as the gateway address, which seems to work. However I have the feeling that this is not necessary, because the host gets it routing information through a multicast on the link. So maybe the gateway for IPv6 should not be there. -- 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=704666 https://bugzilla.novell.com/show_bug.cgi?id=704666#c8 --- Comment #8 from Freek de Kruijf 2011-07-20 20:23:39 UTC --- Indeed entering the /64 part of the IPv6 address followed by ::, so with all zero suffix, as the gateway address solved the problem of ping6 not working right after booting. Also connecting to the website that shows my IP v6 address now showed the fixed address set using YaST. However later it showed the address with the MAC address again. So the bug report reduces to a request for more documentation. -- 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=704666 https://bugzilla.novell.com/show_bug.cgi?id=704666#c10 Li Bin changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bili@novell.com |mt@novell.com --- Comment #10 from Li Bin 2011-07-25 07:22:24 UTC --- Assign to DHCP's maintainer. Marius, Do you know about this issue? 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=704666 https://bugzilla.novell.com/show_bug.cgi?id=704666#c12 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@novell.com, | |mvidner@novell.com --- Comment #12 from Marius Tomaschewski 2011-08-09 16:55:47 UTC --- When RUN_PARALLEL="yes" in set in /etc/sysconfig/boot (default) it is normal (intentional) that the X11 session already starts before the network is up (still waiting for dhcp lease). You may set RUN_PARALLEL=no. Not normal is such a long delay of > 1 minute. See also bug 697929 -- there is no check / ifup does not wait until IPv6 address becomes usable (still in tentative mode). But it doesn't explain the long delay. Please disable SuSEfirewall2 using following commands: insserv -r /etc/init.d/SuSEfirewall2_init insserv -r /etc/init.d/SuSEfirewall2_setup and reboot. Does it help? (In reply to comment #4)

After reading the man page "man ifcfg" I changed the file /etc/sysconfig/network/ifcfg-eth0 into: BOOTPROTO='static' IPADDR='192.168.1.40/24' IPADDR_1='2001:980:7480:1:192:168:1:40/64' STARTMODE='nfsroot'

After "ifdown eth0" and "ifup eth0" the eth0 does have three global IPv6 addresses; the two in the previous comment and the newly specified one.

Is STARTMODE='nfsroot' intentional or is it just set up by yast2 because of bug 677251? In "nfsroot" mode, IP addresses are never removed (a filesystem or volume is assumed to be accessed using one of them). When you don't need this special feature, switch back to STARTMODE=auto. (In reply to comment #9)

I did a test by configuring nothing in the network, so I got a system with one Ethernet interface, which is set to get all its parameters through DHCP, both v4 and v6. But also DNS and routing come through DNS.

OK.

Getting the IPv4 parameters is almost immediately, just a few seconds during booting, however getting the IPv6 parameters takes sometimes 10 minutes.

Hmm... Which router are you using? Please install "radvd" and dump the config provided by the router using "radvdump eth0".

After searching a lot of IPv6 information I found a commented out line in /etc/dhclient6.conf, which after removing the two hashes, solved the problem of the long delay. The line reads "##send dhcp6.rapid-commit;". It still takes more than getting the parameters for IPv4, but as soon as I can log in, the IPv6 network is ready. So I recommend to have these hashes removed, or maybe conditionally removed.

Yes, for 12.x we can enable rapid commit as default I think -- it should be supported by all dhcp6 servers. (In reply to comment #11)

I reinstalled openSUSE 12.1 M3 and watched the appearance of the Scope:Global IPv6 addresses. At first the appearance was fast. However after a reboot it took about 9 minutes. I removed the two hashes in /etc/dhclient6.conf and rebooted again. There was no apparent change in the time it takes to finally get the Scope:Global IPv6 addresses. The setup is traditional ifup with one Ethernet interface and DHCP4 and 6 enabled in YaST Network Settings. For some reason, I don't understand why, the interface gets two IPv6 addresses. But the removal of the hashes does not (always) work.

If you get one or multiple IPv6 addresses depends on the configuration of the router. Read about "AdvAutonomous" (client allowed to assing address itself) and the "AdvManagedFlag" and "AdvOtherConfigFlag" (-> dhcpv6) in radvd.conf(5) manual page. When you're using DHCPv4 and DHCPv6, the BOOTPROTO should be set to 'dhcp' or to 'dhcp4+dhcp6'. The later one forces to wait until both, dhcp4 and 6 clients finished the IP configurations. In BOOTPROTO='dhcp' mode, success of one of them is sufficient. -- 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=704666 https://bugzilla.novell.com/show_bug.cgi?id=704666#c14 --- Comment #14 from Freek de Kruijf 2011-08-12 08:06:23 UTC --- I try to focus on the long delay, so at this moment I won't send you most of the requested information, although I have collected it. My router is FRITZ!BOX 7340 which is maintained more or less by my ISP. I disabled IPv6 in the host system and started Wireshark to capture IPv6 traffic only. So nothing was captured until I started VirtualBox 4.1.0 with openSUSE 12.1 M3. In Wireshark packet 5 and 6 are ICMP6 Router solicitations from the MAC address of the VM. Packet 7 is the answer, ICMP6 Router advertisement, and contains the global prefix. This is at 8:39:11.91x This is repeated at 8:38:15.92x and 8:39.19.93x After this I don't see any ICMP6 packets, I do see DHCP6, MDNS and LLMNR packages. At 8:48.50.93x there is a ICMP6 Router advertisement, without a solicitation package, which contains again the global IPv6 prefix. It has the same length as the earlier ones and seems to contain the same information. After this I see 4 ICMP6 Neighbour solicitation packets with two different IPv6 addresses. At that time I also see in /var/log/messages the avahi message about the global IPv6 adresses. Below are all the avahi messages: Aug 12 08:39:28 os121m3 avahi-daemon[2944]: Server startup complete. Host name is os121m3.local. Local service cookie is 3421843115. Aug 12 08:39:29 os121m3 avahi-daemon[2944]: Service "os121m3" (/etc/avahi/services/udisks.service) successfully established. Aug 12 08:39:29 os121m3 avahi-daemon[2944]: Service "os121m3" (/etc/avahi/services/ssh.service) successfully established. Aug 12 08:39:29 os121m3 avahi-daemon[2944]: Service "os121m3" (/etc/avahi/services/sftp-ssh.service) successfully established. Aug 12 08:48:51 os121m3 avahi-daemon[2944]: Registering new address record for 2001:980:7480:1:a00:27ff:febe:a79d on eth0.*. Aug 12 08:48:51 os121m3 avahi-daemon[2944]: Withdrawing address record for fe80::a00:27ff:febe:a79d on eth0. Aug 12 08:48:52 os121m3 avahi-daemon[2944]: Registering new address record for 2001:980:7480:1:2821:77cd:3f97:83a3 on eth0.*. Aug 12 09:48:46 os121m3 avahi-daemon[2944]: Registering new address record for 2001:980:7480:1:4905:132b:bb6b:81cc on eth0.*. Aug 12 09:48:50 os121m3 avahi-daemon[2944]: Withdrawing address record for 2001:980:7480:1:2821:77cd:3f97:83a3 on eth0. As you can see, it takes 9 minutes 22 seconds before the global IPv6 address is established. I will attach the gziped libpcap file from Wireshark. -- 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=704666 https://bugzilla.novell.com/show_bug.cgi?id=704666#c16 --- Comment #16 from Freek de Kruijf 2011-08-12 13:04:46 UTC --- After removing dhcp6 in the configuration of the eth0 interface the global IPv6 address appears immediately (after 2 seconds). So not starting DHCP6 solves the problem. Apparently my router does not support DHCP6. -- 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=704666 https://bugzilla.novell.com/show_bug.cgi?id=704666#c18 --- Comment #18 from Freek de Kruijf 2011-08-15 13:10:43 UTC --- My view is that in openSUSE the default configuration in YaST, when leaving or requesting a dynamic address, should be that only DHCP4 should be made active and DHCP6 should not be made active. Now the default is that both DHCP version 4 and 6 are requested. -- 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.