This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: IPv6 fails when IPv4 not configured
- From: Grant Edwards <grant dot b dot edwards at gmail dot com>
- To: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 19 Jun 2013 16:38:31 +0000 (UTC)
- Subject: Re: IPv6 fails when IPv4 not configured
- References: <kpq98p$fqh$1 at ger dot gmane dot org>
On 2013-06-18, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> How do I get the network stack to create and configure an IPv6
> link-local address for the interface? It seems that configuring the
> interface with a static IPv6 address does that as a "side effect". How
> do I get that to happen without configuring a static IPv6 address?
No ideas on how to get the link local address initialized in IPv6?
Any ideas on how to add an IPv6 route so I can try adding the ff02::
multicast route manually?
Is there any documentation for the eCos IPv6 APIs?
It appears that even configuring an IPv4 static address is sufficient
to allow IPv6 multicast packets to be sent to ff02:: /16 addresses.
But IPv6 should not have to depend on IPv4 being configured.
--
Grant Edwards grant.b.edwards Yow! Vote for ME -- I'm
at well-tapered, half-cocked,
gmail.com ill-conceived and
TAX-DEFERRED!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss