https://bugzilla.novell.com/show_bug.cgi?id=697929
https://bugzilla.novell.com/show_bug.cgi?id=697929#c23
--- Comment #23 from Marius Tomaschewski
Hi, Ruediger Meier
I am testing the bug, but I knew a little about rcnetwork and ipv6. So how did you discovered the bug? and what steps to reproduce it?
Sorry, I forgot to attach a test description. Here some hints how to reproduce it quite easy: First, manual steps: ip link set dev eth0 down ip addr flush dev eth0 -- ip link set dev eth0 up ip addr add 2001:DB8:abba::1/64 dev eth0 ip addr show Every IPv6 is initially visible as "tentative", e.g.: inet6 2001:DB8:abba::1/64 scope global tentative after few seconds, when the kernel finished DAD, this flag will either disappear (success) or will get the "dadfailed" or the "flags 08" addition (depends on ip route version). Set up a NIC with static IPv6 address, e.g.: STARTMODE=auto BOOTPROTO='static' IPADDR='2001:DB8:abba::1/64' then execute the following commands: rcnetwork stop -o boot rcnetwork start -o boot ; ip addr show # sleep 10 ; ip addr show When you see tentative (without flags 08 or dadfailed), you run into this problem here. The second (commented out) "ip a s" after 10 secs should usually not show the tentative flag any more. Now you can configure a service that makes use of the IP address [bind() to this IP address, usually via "Listen 2001:DB8:abba::1"] and this service may fail trying to use the tentative address when it gets started just after network. The fixed rcnetwork version may show it as: eth0 is up, but has tentative ipv6 address but then wait until the DAD finished. -- 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.