At 20:54 10.02.2001, Slyoldfox wrote:
>oki tnx for the explenation of the 2000::/3 .. i added a route for that in
>the router ..
>
>Like you said I added its v6 IP to eth0
>Iridium:/# ifconfig eth0 add 3ffe:2a00:100:7ba2::3
>
>and added a route from the host to the router
>Iridium:/home/backup/iputils# route6 add 3ffe::/16 gw 3ffe:2a00:100:7ba2::2
>dev eth0
>router is ::2 here coz ::1 is the tunnel end point of *.uninett.no.
>
>routing table now looks like:
>Iridium:/home/backup/iputils# route6
>Kernel IPv6 routing table
>Destination Next Hop
>Flags Metric Ref Use Iface
>::1/128 ::
>U 0 3 0 lo
>3ffe:2a00:100:7ba2::3/128 ::
>U 0 0 0 lo
>3ffe:2a00:100:7ba2::/64 ::
>UA 256 3 0 eth0
>3ffe::/16 3ffe:2a00:100:7ba2::2
>UG 1 0 0 eth0
>fe80::5054:4cff:fe1a:554b/128 ::
>U 0 47 0 lo
>fe80::/10 ::
>UA 256 0 0 eth0
>ff00::/8 ::
>UA 256 0 0 eth0
>::/0 ::
>UDA 256 1 0 eth0
>
>which i thought was ok .. however:
>i can't ping6 3ffe:2a00:100:7ba2::2
>
>when i traceroute6 this i get:
>
>Iridium:/home/backup/iputils# traceroute6 3ffe:2a00:100:7ba2::2
>traceroute to 3ffe:2a00:100:7ba2::2 (3ffe:2a00:100:7ba2::2) from
>3ffe:2a00:100:7ba2::3, 30 hops max, 16 byte packets
> 1 ::1 (::1) 2996.19 ms !H 2996.45 ms !H 2999.39 ms !H
>
>which makes me think of a wrong route somewhere .. but i don't know why it
>would take a wrong route ?
>
>any suggestions ?
Run an IPv6 enabled "tcpdump -n" on each interface of each host and look,
what's going on.
Perhaps an ND-problem. Do you use the USAGI kernel patches?`
Also try "ping6 -n" first before traceroute
Peter
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
