看板 FB_bugs 關於我們 聯絡資訊
--===============2225362800772039958== Content-Type: text/plain The following reply was made to PR kern/188032; it has been noted by GNATS. From: Darren Baginski <kickbsd@yandex.ru> To: Andrey V. Elsukov <bu7cher@yandex.ru>, "freebsd-gnats-submit@FreeBSD.org" <freebsd-gnats-submit@freebsd.org> Cc: Subject: Re: kern/188032: IPv6 on lo never leaves 'tentative' state if configured with prefixlen 128 Date: Thu, 03 Apr 2014 05:08:45 +0400 31.03.2014, 12:11, "Andrey V. Elsukov" <bu7cher@yandex.ru>: >> ⒐Pv6 on lo never leaves 'tentative' state if configured with prefixlen 128. >> >> ⒚teps to reproduce. >> >> 騣 ifconfig lo8 create >> 騣 ifconfig lo8 up >> 騣 ifconfig lo8 inet6 fc00::ff prefixlen 128 >> >> 騣 ifconfig lo8 >> 弎o8: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 >> 骚骚骚骚忂ptions=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> >> 骚骚骚骚幈net6 fc00::ff prefixlen 128 tentative >> 骚骚骚骚徱d6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> >> >> 弎o8 ipv6 stays 'tentative' stays forever and never become ping-able. >> >> 騢Workaround" is to apply any other prefixlen, e.g. /127 >>> ⒏ow-To-Repeat: >> 騣 ifconfig lo8 create >> 騣 ifconfig lo8 up >> 騣 ifconfig lo8 inet6 fc00::ff prefixlen 128 >> >> 騣 ifconfig lo8 >> 弎o8: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 >> 骚骚骚骚忂ptions=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> >> 骚骚骚骚幈net6 fc00::ff prefixlen 128 tentative >> 骚骚骚骚徱d6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> >> >> 騣 ping fc00::ff >>> ⒍ix: >> 騢Workaround" is to apply any other prefixlen, e.g. /127 > > Hello, > > Actually the problem is in your configuration. As you may see, you have > IFDISABLED flag set. When you are configuring /127 prefix, the system > does install route on that prefix and automatically clears IFDISABLED > flag. When you are configuring /128 prefix, the system won't install > route and thus IFDISABLED flag still here. With IFDISABLED flag the > system won't do DAD and 惗entative flag will never cleared. > > -- > WBR, Andrey V. Elsukov I'm not setting IFDISABLED flag as you see from output below. Moreover the same set of commands doesn't dot put interface into IFDISABLED sate on FreeBSD 7.x, 8.x, 9.x Again, if I set IPv4 /32 it works as well. Thus this /128 case is a clear regression. --===============2225362800772039958== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org" --===============2225362800772039958==--