From: Stephen Hemminger <shemminger@vyatta.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Jiri Bohac <jbohac@suse.cz>,
netdev@vger.kernel.org, Herbert Xu <herbert@gondor.hengli.com.au>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: IPv6: autoconfiguration and suspend/resume or link down/up
Date: Thu, 21 Jul 2011 12:44:57 -0700 [thread overview]
Message-ID: <20110721124457.72cb45e4@nehalam.ftrdhcpuser.net> (raw)
In-Reply-To: <1311266139.3059.9.camel@dcbw.foobar.com>
On Thu, 21 Jul 2011 11:35:37 -0500
Dan Williams <dcbw@redhat.com> wrote:
> > For problem #2, shouldn't a new RS be sent whenever the interface
> > changes it's IFF_LOWER_UP bit? IFF_LOWER_UP indicates a carrier on/off
> > event and thus indicates possible disconnect/reconnect to a new network.
> > I don't specifically know how it works now, but if RS isn't triggered
> > from IFF_LOWER_UP, I'd imagine that either (a) something didn't get
> > updated when IFF_LOWER_UP became how carrier was indicated in 2.6.17
> > (commit b00055aacdb172c05067612278ba27265fcd05ce) or (b) there's a
> > reason IFF_LOWER_UP isn'
IFF_RUNING is used to indicate carrier, IFF_LOWER_UP is for layered
devices like vlan's but is rarely used.
next prev parent reply other threads:[~2011-07-21 19:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 18:02 IPv6: autoconfiguration and suspend/resume or link down/up Jiri Bohac
2011-07-20 16:15 ` Stephen Hemminger
2011-07-20 16:29 ` Jiri Bohac
2011-07-20 16:21 ` Dan Williams
2011-07-20 16:36 ` Jiri Bohac
2011-07-21 5:30 ` Dan Williams
2011-07-21 16:35 ` Dan Williams
2011-07-21 19:44 ` Stephen Hemminger [this message]
2011-07-22 8:06 ` David Miller
2011-07-22 9:21 ` Herbert Xu
2011-07-23 14:31 ` Nicolas de Pesloüan
2011-07-23 15:27 ` Herbert Xu
2011-07-23 16:37 ` Stephen Hemminger
2011-07-24 0:18 ` Herbert Xu
2011-07-24 8:35 ` Nicolas de Pesloüan
2011-07-25 3:26 ` Stephen Hemminger
2011-07-25 3:46 ` Herbert Xu
2011-07-27 19:48 ` Dan Williams
2011-07-19 19:42 Stephen Hemminger
2011-07-26 5:16 ` Anirban Chakraborty
2011-07-25 16:55 Stephen Hemminger
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=20110721124457.72cb45e4@nehalam.ftrdhcpuser.net \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=herbert@gondor.hengli.com.au \
--cc=jbohac@suse.cz \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.