[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 00412) Re: anormal route
- To: usagi-users@xxxxxxxxxxxxxx, "'(Lista) users@xxxxxxxx'" <users@xxxxxxxx>
- Subject: (usagi-users 00412) Re: anormal route
- From: Peter Bieringer <pb@xxxxxxxxxxxx>
- Date: Fri, 20 Apr 2001 08:20:05 +0200
- In-reply-to: <73388857A695D31197EF00508B08F29801908CA4@ntmsg0131.corpmai l.telstra.com.au>
- Reply-to: usagi-users@xxxxxxxxxxxxxx
At 01:20 20.04.2001, Venning, Roger wrote:
Juan,
You must have a route to 2002::/16 via sit0. I recommend
looking at Peter Bieringer's scripts, and also you might
like to use the iproute2 package, (e.g. ip -6 route show)
rather than route. I also concur that the route
> 2002:a375:8b2c:1f::/64
> :: UA 256 0 0 sit0
looks very wrong, given the addresses assigned to the ethernet
and sit0 devices.
>
> I trying to ping6 www.kame.net through a 6to4 tunnel in linux.
> If I do the ping6 in the machine with the 6to4 tunnel, all is ok,
> but if I try to do the ping6 in another host directly connected
> with the 6to4 router, I receive no answer.
There is an existing issue regarding the generated routing entries. You
have to set /64 static routes for your LAN interfaces, too, if you want to
connect subnets to the 6bone
See here for solution:
http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/scripts/current/index.html#6to4subnetrouting
and set following option proper:
IPV6TO4_ROUTING="eth0-:f101::0/64 eth1-:f102::0/64"
Strange but working format:
eth0 : devicename
- : delimiter
:f101::0/64 : LAN suffix (example)
Peter