From: "David S. Miller" <davem@davemloft.net>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: 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 12:27:45 -0800 [thread overview]
Message-ID: <20050210122745.16ca7cb3.davem@davemloft.net> (raw)
In-Reply-To: <200502101817.j1AIH6p7000602@death.nxdomain.ibm.com>
On Thu, 10 Feb 2005 10:17:06 -0800
Jay Vosburgh <fubar@us.ibm.com> wrote:
> The model used by the bridge device is probably a better way to
> go, particularly given that IPv6 link local addresses are created at
> "ifconfig up" time.
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.
next prev parent reply other threads:[~2005-02-10 20:27 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 [this message]
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
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=20050210122745.16ca7cb3.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=bonding-devel@lists.sourceforge.net \
--cc=ctindel@users.sourceforge.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 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.