linux-kernel - Re: [IPv6] PROBLEM? Network unreachable despite correct route

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070117081420.GA1613@ff.dom.local>
Date:	Wed, 17 Jan 2007 09:14:20 +0100
From:	Jarek Poplawski <jarkao2@...pl>
To:	Bernhard Schmidt <berni@...kenwald.de>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [IPv6] PROBLEM? Network unreachable despite correct route

On Thu, Jan 11, 2007 at 02:08:16PM +0100, Bernhard Schmidt wrote:
> Jarek Poplawski wrote:
> 
> >>ip -6 route:
> >>2001:4ca0:0:f000::/64 dev eth0  proto kernel  metric 256  expires 
> >>86322sec mtu 1500 advmss 1440 fragtimeout 4294967295
> >>fe80::/64 dev eth0  metric 256  expires 21225804sec mtu 1500 advmss 1440 
> >>fragtimeout 4294967295
> >>ff00::/8 dev eth0  metric 256  expires 21225804sec mtu 1500 advmss 1440 
> >>fragtimeout 4294967295
> >>default via fe80::2d0:4ff:fe12:2400 dev eth0  proto kernel  metric 1024  
> >>expires 1717sec mtu 1500 advmss 1440 fragtimeout 64
> >>unreachable default dev lo  proto none  metric -1  error -101 fragtimeout 
> >>255

I've a look at this once more and have one more doubt:
probably it's some other ip6 trick again, but why this
default router doesn't have "normal" address in the
same segment (2001:4ca0:.../64)? 

Regards,
Jarek P.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/