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] IPv6 fails when IPv4 not configured
Date: Tue, 18 Jun 2013 18:35:00 -0000	[thread overview]
Message-ID: <kpq98p$fqh$1@ger.gmane.org> (raw)

I've run into a problem when trying to use IPv6 without IPv4.

With an IPv4 address configured, I can use IPv6 with either a static
address or using DHPCv6 and everything works fine.

If I configure a static IPv6 address, everything is fine.  However, if
when I try to use DHCPv6 without IPv4, both my dhcp client and the
eCos radv6 daemon report "no route to host" failures trying to send.
I believe they're both trying to send link-local multicast packets and
failing because the interface doesn't have a link local address.

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?

-- 
Grant Edwards               grant.b.edwards        Yow! Is a tattoo real, like
                                  at               a curb or a battleship?
                              gmail.com            Or are we suffering in
                                                   Safeway?


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2013-06-18 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 18:35 Grant Edwards [this message]
2013-06-18 18:40 ` [ECOS] " Grant Edwards
2013-06-19 16:38 ` Grant Edwards
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='kpq98p$fqh$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).