public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: IPv6 fails when IPv4 not configured
Date: Wed, 19 Jun 2013 16:38:00 -0000	[thread overview]
Message-ID: <kpsmq7$i6m$1@ger.gmane.org> (raw)
In-Reply-To: <kpq98p$fqh$1@ger.gmane.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

  parent reply	other threads:[~2013-06-19 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 18:35 [ECOS] " Grant Edwards
2013-06-18 18:40 ` [ECOS] " Grant Edwards
2013-06-19 16:38 ` Grant Edwards [this message]
2013-06-20 18:19   ` Grant Edwards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='kpsmq7$i6m$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).