netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
	yoshfuji@linux-ipv6.org, netdev@oss.sgi.com,
	ikebe.takashi@lab.ntt.co.jp, akpm@osdl.org,
	ctindel@users.sourceforge.net,
	bonding-devel@lists.sourceforge.net
Subject: Re: [Bonding-devel] Re: [Bugme-new] [Bug 4189] New: IPv6 link local addresses are not assigned correctly on multiple-bonding enviromrnts
Date: Thu, 10 Feb 2005 13:26:24 -0800	[thread overview]
Message-ID: <420BD180.2040605@hp.com> (raw)
In-Reply-To: <20050210122745.16ca7cb3.davem@davemloft.net>

 >IPv6 should catch an event when MAC addresses change, to reassign
> to correct link local address.  I don't think the bonding driver
> needs to change at all.
> 
> IPv6 needs to fix this issue, regardless of bonding.  It is perfectly
> legal to change MAC addresses while a link is still up.

This may seem a silly question, but what happens to existing TCP connections 
when the IPv6 link local address changes?

rick jones

  reply	other threads:[~2005-02-10 21:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10  8:23 Fw: [Bugme-new] [Bug 4189] New: IPv6 link local addresses are not assigned correctly on multiple-bonding enviromrnts Andrew Morton
2005-02-10  9:22 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-10  9:25   ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-10 11:59     ` Takashi Ikebe
2005-02-10 18:17   ` [Bonding-devel] " Jay Vosburgh
2005-02-10 20:27     ` David S. Miller
2005-02-10 21:26       ` Rick Jones [this message]
2005-02-11  2:40       ` Jay Vosburgh
2005-02-11  3:44         ` David S. Miller
2005-02-10 20:25   ` David S. Miller
2005-02-11  0:29     ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-11  1:06       ` David S. Miller
2005-02-11  1:40       ` Rick Jones
2005-02-11  2:17         ` YOSHIFUJI Hideaki / 吉藤英明

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=420BD180.2040605@hp.com \
    --to=rick.jones2@hp.com \
    --cc=akpm@osdl.org \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=ctindel@users.sourceforge.net \
    --cc=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --cc=ikebe.takashi@lab.ntt.co.jp \
    --cc=netdev@oss.sgi.com \
    --cc=yoshfuji@linux-ipv6.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 NNTP newsgroup(s).