[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 00411) Re: anormal route
- To: "'usagi-users@xxxxxxxxxxxxxx'" <usagi-users@xxxxxxxxxxxxxx>, "'(Lista) users@xxxxxxxx'" <users@xxxxxxxx>
- Subject: (usagi-users 00411) Re: anormal route
- From: "Venning, Roger" <Roger.Venning@xxxxxxxxxxxxxxxx>
- Date: Fri, 20 Apr 2001 09:20:19 +1000
- List-subscribe: <mailto:usagi-users-ctl@linux-ipv6.org?body=subscribe>
- Reply-to: usagi-users@xxxxxxxxxxxxxx
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.
Roger.
--
Roger Venning - Technologist - Telstra Research Laboratories
For a successful technology, reality must take
precendence over public relations, for Nature
cannot be fooled. Richard Feynman
> -----Original Message-----
> From: jrh@xxxxxxxxxxxxxxxxxx
> [mailto:jrh@xxxxxxxxxxxxxxxxxx]On Behalf Of
> Juan Fco Rodriguez Hervella
> Sent: Thursday, 19 April 2001 9:24 PM
> To: (Lista) usagi-users@xxxxxxxxxxxxxx; (Lista) users@xxxxxxxx
> Subject: (usagi-users 00408) anormal route
>
>
> Hi:
>
> 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.
>
> The packets are received by the 6to4 router, and the 6to4 router
> sends them through the sit0 interface:
>
> 2002:a375:8b2c:1f:2c0:26ff:fea0:c15c >
> 3ffe:501:4819:2000:280:adff:fe71:81fc icmpv6: echo request
> 3ffe:501:4819:2000:280:adff:fe71:81fc >
> 2002:a375:8b2c:1f:2c0:26ff:fea0:c15c icmpv6: echo reply
> 3ffe:501:4819:2000:280:adff:fe71:81fc >
> 2002:a375:8b2c:1f:2c0:26ff:fea0:c15c icmpv6: echo reply
> 2002:a375:8b2c:1f:2c0:26ff:fea0:c15c >
> 3ffe:501:4819:2000:280:adff:fe71:81fc icmpv6: echo request
>
> If I examined the routing table of 6to4 box, I realize that
> when the ping6 is running, a new route appears:
>
> 2002:a375:8b2c:1f:2c0:26ff:fea0:c15c/128
> 2002:a375:8b2c:1f:2c0:26ff:fea0:c15c UAC 0 3
> 0 sit0
>
> This is wrong, because the route that should by applied should be:
>
> 2002:a375:8b2c:1f::/64
> :: UA 256 0
> 0 eth0
>
> If I stop the ping6, the route disapears a few time later.
>
> I am using zebra-ripngd, that announces a default route for the link,
> but I have killed the daemons and it is still happening.
> Why is this occurss ??
> Why does it appear that route, which blocks the reply ??
>
> If it is of interest, I attach my interfaces and routing
> table (of 6to4
> router):
> Thanks for your time...
>
> eth0 Link encap:Ethernet HWaddr 00:C0:26:A3:5D:F6
> inet addr:163.117.139.44 Bcast:163.117.139.255
> Mask:255.255.255.0
> inet6 addr: 3ffe:3328:1:1f::a375:8b2c/64 Scope:Global
> inet6 addr: fe80::2c0:26ff:fea3:5df6/10 Scope:Link
> inet6 addr: 2002:a375:8b2c:1f::a375:8b2c/64 Scope:Global
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:23809 errors:0 dropped:0 overruns:0 frame:0
> TX packets:36521 errors:0 dropped:0 overruns:0 carrier:0
> collisions:1278 txqueuelen:100
> Interrupt:10
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16144 Metric:1
> RX packets:133 errors:0 dropped:0 overruns:0 frame:0
> TX packets:133 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
>
> sit0 Link encap:IPv6-in-IPv4
> inet6 addr: ::163.117.139.44/96 Scope:Compat
> inet6 addr: 2002:a375:8b2c::1/64 Scope:Global
> inet6 addr: ::127.0.0.1/96 Scope:Unknown
> UP RUNNING NOARP MTU:1480 Metric:1
> RX packets:251 errors:0 dropped:0 overruns:0 frame:0
> TX packets:345 errors:236 dropped:0 overruns:0 carrier:236
> collisions:0 txqueuelen:0
>
>
>
> root@alacran:~# netstat -rn -A inet6
> Kernel IPv6 routing table
> Destination Next
> Hop Flags Metric Ref Use Iface
> ::1/128
> :: U 0 3 0 lo
> ::127.0.0.1/128
> :: U 0 0 0 lo
> ::163.117.139.44/128
> :: U 0 0 0 lo
> 2002:a375:8b2c::1/128
> :: U 0 6 0 lo
> 2002:a375:8b2c::/64
> :: UA 256 0 0 sit0
> 2002:a375:8b2c:1f::a375:8b2c/128
> :: U 0 0 0 lo
> 2002:a375:8b2c:1f::a375:8ba6/128
> 2002:a375:8b2c:1f::a375:8ba6 UAC 0 17 1 eth0
> 2002:a375:8b2c:1f::/64
> :: UA 256 3 0 eth0
> 2002:a375:8b2c:1f::/64
> :: UA 256 0 0 sit0
> 3ffe:3328:1:1f::a375:8b2c/128
> :: U 0 20 0 lo
> 3ffe:3328:1:1f::/64
> :: UA 256 0 0 eth0
> 3ffe::/16
> ::131.107.152.32 UG 1024 852 0 sit0
> 2000::/3
> ::131.107.152.32 UG 1024 204 0 sit0
> fe80::2c0:26ff:fea3:5df6/128
> :: U 0 24 0 lo
> fe80::/10
> :: UA 256 0 0 eth0
> fe80::/10
> :: UA 256 0 0 sit0
> ff02::1/128
> ff02::1 UAC 0 1 1 eth0
> ff00::/8
> :: UA 256 0 0 eth0
> ff00::/8
>
>
> --
> *********************************
> Juan F. Rodriguez Hervella
> Universidad Carlos III de Madrid
> ********************************
>