From: Rick Jones <rick.jones2@hp.com>
To: netdev@oss.sgi.com
Cc: davem@davemloft.net, ikebe.takashi@lab.ntt.co.jp, akpm@osdl.org,
ctindel@users.sourceforge.net, fubar@us.ibm.com,
bonding-devel@lists.sourceforge.net
Subject: Re: [Bugme-new] [Bug 4189] New: IPv6 link local addresses are not assigned correctly on multiple-bonding enviromrnts
Date: Thu, 10 Feb 2005 17:40:21 -0800 [thread overview]
Message-ID: <420C0D05.6020408@hp.com> (raw)
In-Reply-To: <20050211.092916.50162307.yoshfuji@linux-ipv6.org>
>>I guess this causes problems for ipv6 local addresses, it
>>will need to catch some callback to handle these events and
>>thus adjust the local address properly.
>
>
> Okay, I'll try to solve it:
> 1) catch NETDEV_CHANGEADDR
> 2) (try to) add new link-local address and deprecate old one.
> 3) (when DAD finishes) RS will be sent.
At present, for IPv4 if someone changes the MAC address of an interface,
existing TCP connections don't really care right? The ARP caches will be
updated with a new IPv4 to MAC translation and happiness and joy ensues.
So, what would happen to TCP connections over IPv6 using link-local addresses?
If the old address is taken away (deprecated), and a new address generated,
doesn't that mean that TCP connections (using link-local addresses anyway) will
fail on a MAC change?
rick jones
next prev parent reply other threads:[~2005-02-11 1:40 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
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 [this message]
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=420C0D05.6020408@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 \
/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).