On Tue, Jan 16, 2001 at 02:58:03AM -0300, [EMAIL PROTECTED] wrote:
> ¡Hola!
>
> > > I'm experimenting with ipv6 and i need some help. I've a gif
> > > tunnel between a FBSD 4.0 and a FBSD 4.2.
> > >
> > > In the 4.2 side i get lots of messages like:
> > >
> > > Jan 16 02:34:05 ipv6-gw /kernel: nd6_lookup: failed to add route for a
>neighbor(3ffe:2900:b00d:ff00::0002), errno=17
> > > Jan 16 02:34:05 ipv6-gw /kernel: nd6_lookup: failed to add route for a
>neighbor(3ffe:2900:000b:000d::0001), errno=17
> > >
> > > each time i use such tunnel
> > >
> > > I've looked at some search engines and know it's a common problem but no
> > > known solution (i'm tempted to recompile commenting out the log call)
> >
> > Your address prefix length is incorrect..can't remember what the
> > correct value should be off the top of my head, but it's come up
> > before so it should be in the archives upon closer examination.
>
> It looks like 128 is the "right" prefixlen. Problem is that my upstream
> provider (Sprint) wants to use 64 as prefixlen (IMHO FBSD is ok, but it
> seems to be the common practice to assign /64 to tunnels)
Hmm, not sure what can be done about that.
> > It's a common mistake - a FAQ question/answer would probably be in
> > order (could you write a doc PR once you've fixed it?).
>
> What's a PR?
Problem Report - it's the submission mechanism for changes and
patches, as well as bugs. You can submit one from the command-line
using send-pr with the doc patches if/when you write them (if you're
not familiar with docbook then ascii text is also fine), or using the
web interface at www.freebsd.org/send-pr.html
Kris
PGP signature
