Hi. Does anybody run recent 10-stable with working 6to4 connectivity? A week ago I upgraded two systems where stf(4) is used. They were running 10-stable from beginning of September, with stf working fine. After upgrade, the address on stf0 stays "tentative" indefinitely. So far, I've not found any way to force it online. Tried ifconfig down/up, ifdisabled, no_dad, and sysctl -w net.inet6.ip6.dad_count=0. The latter just makes "tentative" flag flapping. Looking at commits, I suspect that r287734 (MFC of r287094) and/or r290348 (MFC of r288600) may be responsible for this. It changed the code that handles DAD, and AFAICT at least in6if_do_dad() now returns different value for stf interfaces than before. -- Dan
On Wed, 16 Dec 2015 17:04:18 +0100 Daniel Bilik <ddb at neosystem.org> wrote:> A week ago I upgraded two systems where stf(4) is used. They were running > 10-stable from beginning of September, with stf working fine. After > upgrade, the address on stf0 stays "tentative" indefinitely.I've finally got some time to analyze this more thoroughly. And indeed, the problem was introduced with both r287734 (changes to in6if_do_dad() in sys/netinet6/in6.c) and r290348 (changes to nd6_timer() in sys/netinet6/nd6.c), specifically in combination with stf(4) interfaces not being marked "running". Attached patch fixes that. Should I create PR for this? -- Dan -------------- next part -------------- A non-text attachment was scrubbed... Name: dad-on-stf.diff Type: text/x-diff Size: 672 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20160113/71e9a50a/attachment.diff>