Hi Wong, As far as i can see it looks fine, but there are a bit to many unreachables for my taste. but nevermind about that. I would rather see the output of ip route show . just the normal ipv4 route table.
Does the trace ever work, or does it always fail? does it always fail at the same point, with the same server? Kind regards, @ On Wednesday 06 April 2005 04:42, PM WONG wrote: > Hi > > > It looks like your internet conection is lost somehow. > > The lookup starts at root level, then finds a server in the GTLD domain > > and then nothing ..... strange. > > > > Are there any specific routes you defined? ( mail the ouput of ip route > > show please) > > No. > Here's the output of the command: > ip -f inet6 route show > > --------------------------------------------- > unreachable ::/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 > metric1 > 0 64 > unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 16436 > advmss 1 > 6376 metric10 64 > 2001:ce0:6:10::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss > 1440 metr > ic10 64 > unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss > 16376 > metric10 64 > unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 metric10 64 > 2001:ce0:6:10::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss > 1440 metr > ic10 64 > unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss > 16376 > metric10 64 > unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 > advmss 1637 > 6 metric10 64 > fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 metric10 64 > ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440 metric10 1 > default via fe80::209:e9ff:fe48:438 dev eth0 proto kernel metric 1024 > expires > 173sec mtu 1500 advmss 1440 metric10 64 > unreachable default dev lo proto none metric -1 error -101 metric10 255 > > -------------- > It seems to look okay for interface eth0, or does it? > > PM Wong, ITSC , Hongkong Baptist University > > --------------------------------------------------------------------- > The IPv6 Users Mailing List > Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED] --------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
