Re: IPv6 over gif(4) broken in 6.2-RELEASE?



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
anyways. Also, that's not the change I made to my local sources to get
my gif(4) tunnel working. Are you sure about this? :-)

I'm following -STABLE, and 1.48.2.16 is in there. Since it was
committed on 29 Nov, I suspected it would end up in -RELEASE, but
apparently not. :)

I explicitly tried reverting just this one commit, and for me it solved
the problem (i.e. the automagical addition of needed routing entries).

So for you, reverting the combination of 1.48.2.14 and .15 works? Maybe
there is something else involved too, for example the route command
itself?

I'll have to experiment a bit further, I guess.
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: IPv6 over gif(4) broken in 6.2-RELEASE?
    ... Bruce A. Mah wrote: ... This isn't consistent with what I'm finding. ... I explicitly tried reverting just this one commit, ...
    (freebsd-stable)
  • Re: .version keeps being updated
    ... 8993780a6e44fb4e7ed34e33458506a775356c6e is first bad commit ... Reverting this from 2.6.20-rc1 made the build behave again, ... this patch started all the mess: ... Fix linux banner utsname information ...
    (Linux-Kernel)
  • Re: .version keeps being updated
    ... 8993780a6e44fb4e7ed34e33458506a775356c6e is first bad commit ... depends on getting the kernel version from the kernel binary. ... This just restores "linux_banner" as a static string, ... Reverting this from 2.6.20-rc1 made the build behave again, ...
    (Linux-Kernel)
  • Re: .version keeps being updated
    ... 8993780a6e44fb4e7ed34e33458506a775356c6e is first bad commit ... Reverting this from 2.6.20-rc1 made the build behave again, ... this patch started all the mess: ... Fix linux banner utsname information ...
    (Linux-Kernel)
  • Re: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545b
    ... Bisection turned up commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd as the culprit: ... Reverting this commit helps. ... extern u64 e820_hole_size; ... extern void e820_reserve_resources; ...
    (Linux-Kernel)