v6 trouble
Dancer
dancer@zeor.simegen.com
Mon, 16 Oct 2000 19:02:19 -0700
Chris Kennedy wrote:
> On Mon, Oct 16, 2000 at 09:36:04AM -0700, Jason Martin wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > > > Hi!
> > > > I'm having some trouble setting up and v6 tunnel against freenet6,
> > > > I'm running Linux (debian)... If anyone have some ideas/hints, let me hear
> > > > it =)
> > >
> > > Hmmm...when "forwarding" is on, Linux ignore default route(::/0)
> > > It means Linux using as a router must have full route!! ;-(
> > > So, you'll need to input following commands...
> > This isn't really true, is it? At least, for ipv4 I can use a default
> > route w/o having a 'full' route table. Has this changed for v6?
> >
> > Thanks,
> > - -Jason Martin
> >
>
> I had to setup the routes for a tunnel server this way, for
> routing ipv6 out to the 6bone through the tunnel server from the
> tunnel endpoints. they were able to have local ipv6 network access
> fine but out past the main ipv6 gateway to the 6bone they would not
> be able to access anything. I just discovered that adding specific
> routes for a prefix would allow the endpoints to access the 6bone.
> I think it is a bug in the Linux kernel, but didn't have the time
> to dig into the problem anymore than geting it to work for that server.
> It seemed like the server forwarding the ipv6 packets would treat those
> forwarded packets with another routing table that didn't include the
> default as an option like the locally generated packets have, so you
> had to add those specific prefixes to give those packets the route.
>
Alexey's take on this is that the default route does not exist when _forwarding_
ipv6 packets. It's only checked when originating them. I felt it was a bug, and
queried him. He told me it was intentionally that way.
D