JINMEI Tatuya / 神明達哉 wrote:
>> Confirmed. I've updated the machine on which I originally had this
>> problem to -STABLE as of today, and the problem has disappeared.
>
> I thought it was also planned to be incorporated to RELENG_6_2, right?
I'm not sure if non-security related fixes are consider
Bruce A. Mah wrote:
> I've convinced myself that this problem needs to be tested in isolation
> (i.e. you have complete control over both ends of the tunnel) because
> incoming packets over the tunnel cause the host route to get added
> automatically if it wasn't there already.
>
> After reading t
Bruce A. Mah wrote:
Just to confirm, you're dealing with a gif(4) interface with an
explicitly-configured destination address and a 128-bit prefixlen, yes?
Yes. The specific line in my rc.conf is:
ipv6_ifconfig_gif0="2001:7b8:2ff:146::2 2001:7b8:2ff:146::1 prefixlen 128"
Maybe
there is som
Bruce A. Mah wrote:
>> and later I found out it was caused by commit 1.48.2.16:
>> http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031853.html
>
> This isn't consistent with what I'm finding. For one thing, rev.
> 1.48.2.16 of nd6.c isn't in 6.2-RELEASE but I saw the problem there
Bruce A. Mah wrote:
>> I remember Dimitry Andric reported the same problem on -stable on 30
>> Dec, and after he reverted rev.1.48.2.16 it worked fine again. Do
>> you have the symptom even on 6.2-RELEASE? Since RELENG_6_2_0_RELEASE
>> did not have the change, I thou
