This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: IPV6 Testing
- From: bhanuprakash kandimalla <kbhanu at yahoo dot com>
- To: Andrew Lunn <andrew at lunn dot ch>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Thu, 26 Aug 2004 12:48:02 -0700 (PDT)
- Subject: Re: [ECOS] IPV6 Testing
--- Andrew Lunn <andrew@lunn.ch> wrote:
> On Wed, Aug 25, 2004 at 10:51:06AM -0700,
> bhanuprakash kandimalla wrote:
> >
> > --- Andrew Lunn <andrew@lunn.ch> wrote:
> >
> > > On Tue, Aug 24, 2004 at 07:07:44PM -0700,
> > > bhanuprakash kandimalla wrote:
> > > > Hello ECOS World:
> > > > I am testing ecos for i386pc(with net
> template). I
> > > am
> > > > using the test case as mentioned in the ecos
> > > document.
> > > > When I called the (ping_test.c file)
> net_test()
> > > > function ( I commented the ipv4 part) I am
> always
> > > > getting the following message: "No Router
> > > > advertisement received"
> > > > Which means that cyg_net_get_ipv6_advrouter()
> is
> > > > returning 0. Can someone suggest me what this
> > > > net_test() will test for IPV6. My intention is
> to
> > > > ping6 another IPV6 host. The ping from another
> > > ipv6
> > > > host to the target is working just fine.
> > >
> > > By default, eCos expects an IPv6 router
> advertisent
> > > server, such as
> > > radvd, on the network. This allows the IPv6 host
> to
> > > make its own IP
> > > address from the network portion advertised in
> the
> > > rputer advert and
> > > the MAC address for the lower part of the IP
> > > address.
> > >
> > > Either starically configure the IPv6 addresses
> or
> > > start a radvd
> > > daemon.
> > Statically...can this be done in the config tool?
> In
> > the config tool, I already selected
> > BasicNetworkingFramework-->INET support-->IPv6
> > Support. I disabled the option "Options
> controlling
> > IPv6 routing.
> > I am using all static IPv4 and Ipv6 addresses.
> Ping4
> > works fine.
> > For ping6, I provide the IPV6 address as
> following:
> > void ping6_start(void)
> > {
> > struct sockaddr_in6 ipv6router;
> > struct in6_addr in6addr={{{0xfe,0x80, 0, 0, 0, 0,
> 0,
> > 0, 0x2, 0x1, 0x02, 0xff,0xfe, 0x37, 0x2e, 0xa0}}};
> >
> >
> > ipv6router.sin6_len=sizeof(ipv6router);
> > ipv6router.sin6_family=AF_INET6;
> > ipv6router.sin6_port=0;
> > ipv6router.sin6_addr=in6addr;
> >
> > ping6_test(&ipv6router);
> > }
> >
> > Am i missing anything here? I am getting the
> following
> > message:
> > "PING6 server fe80::201:2ff:fe37:2ea0
> > sendto: No route to host". This message will be
> > repeated 16 times.
>
> So you don't have a valid route.
I am wondering how is this different from IPv4. With
the same functions for ipv4, ping(ipv4) works fine
from the target. I guess I am missing a basic concept
here. I don't have much knowledge about IPV6 stuff.
Can someone suggest me what is missing here. I
appreciate any help
> Add a call to show_network_tables(). That will print
> out all the
> addresses the interfaces have and the routing table.
>
For reference I am attaching a textfile for the
routing information.
Thanks,
Bhanu.
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 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
Interface statistics
eth0 IP: 10.21.1.246, Broadcast: 10.21.1.255, Netmask: 255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU: 1500, Metric: 0
Rx - Packets: 8, Bytes: 983, Tx - Packets: 0, Bytes: 0
eth0 IP: fe80:1::2d0:b7ff:fe7e:436f/64
UP BROADCAST RUNNING MULTICAST MTU: 1500, Metric: 0
Rx - Packets: 0, Bytes: 0, Tx - Packets: 3, Bytes: 216
eth0 IP: 3ffe:302:11:2::a15:1f6/128
UP BROADCAST RUNNING MULTICAST MTU: 1500, Metric: 0
Rx - Packets: 0, Bytes: 0, Tx - Packets: 0, Bytes: 0
lo0 IP: ::1/128 NoDAD
UP LOOPBACK RUNNING MULTICAST MTU: 16384, Metric: 0
Rx - Packets: 0, Bytes: 0, Tx - Packets: 0, Bytes: 0
lo0 IP: fe80:2::1/64 NoDAD
UP LOOPBACK RUNNING MULTICAST MTU: 16384, Metric: 0
Rx - Packets: 0, Bytes: 0, Tx - Packets: 0, Bytes: 0
lo0 IP: 127.0.0.1, Broadcast: 127.0.0.1, Netmask: 255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU: 16384, Metric: 0
Rx - Packets: 0, Bytes: 0, Tx - Packets: 0, Bytes: 0
socket :3
setsocketopt =0
PING6 server fe80::201:2ff:fe37:2ea0
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
resul
t: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
sendto: No route to host
result: -1
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss