From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20872 invoked by alias); 26 Aug 2004 20:43:11 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 20845 invoked from network); 26 Aug 2004 20:43:09 -0000 Received: from unknown (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org with SMTP; 26 Aug 2004 20:43:09 -0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1C0R5K-0007QG-00; Thu, 26 Aug 2004 22:43:02 +0200 Date: Thu, 26 Aug 2004 21:45:00 -0000 To: bhanuprakash kandimalla Cc: Andrew Lunn , ecos-discuss@sources.redhat.com Message-ID: <20040826204302.GB4059@lunn.ch> Mail-Followup-To: bhanuprakash kandimalla , Andrew Lunn , ecos-discuss@sources.redhat.com References: <20040825182124.GA4059@lunn.ch> <20040826194803.79379.qmail@web40907.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040826194803.79379.qmail@web40907.mail.yahoo.com> User-Agent: Mutt/1.5.6+20040803i From: Andrew Lunn Subject: Re: [ECOS] IPV6 Testing X-SW-Source: 2004-08/txt/msg00397.txt.bz2 > Routing tables > Destination Gateway Mask Flags Interface > 0.0.0.0 10.21.1.1 0.0.0.0 UG eth0 > 10.21.1.0 10.21.1.0 255.255.255.0 U eth0 > 127.0.0.0 127.0.0.1 255.0.0.0 UG lo0 > 127.0.0.1 127.0.0.1 UH lo0 > ::1 ::1 UH lo0 > 3ffe:302:11:2::a15:1f6 3ffe:302:11:2::a15:1f6 UH lo0 > > fe80:1:: fe80:1:: /64 U eth0 > fe80:1::2d0:b7ff:fe7e:436f fe80:1::2d0:b7ff:fe7e:436f UH lo0 > fe80:2:: fe80:2::1 /64 U lo0 > fe80:2::1 fe80:2::1 UH lo0 > ff01:1:: ff01:1:: /32 U eth0 > ff01:2:: ::1 /32 U lo0 > ff02:1:: ff02:1:: /32 U eth0 > ff02:2:: ::1 /32 U lo0 > PING6 server fe80::201:2ff:fe37:2ea0 > sendto: No route to host IPv6 works just the same as IPv4 in terms of routing. fe80::201:2ff:fe37:2ea0 is not on any of the directly connected nets. So it has to be routed through a gateway. Unforutately, you don't have any routes to gateways configured and not default route. Hence it does not know where to send the packet and so it is printing the error message. You need to sort out your IP addresses and routers and make sure eCos knows this information. Probably the easiest way to do this is use radvd or some other router advertisement program. Andrew -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss