From: jamal <hadi@cyberus.ca>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: dshwatrz@gmail.com, davem@davemloft.net, netdev@vger.kernel.org,
kaber@trash.net
Subject: Re: [PATCH net-2.6][NEIGH] Updating affected neighbours when about MAC address change
Date: Mon, 24 Dec 2007 09:33:20 -0500 [thread overview]
Message-ID: <1198506800.9642.40.camel@localhost> (raw)
In-Reply-To: <1198415873.4423.96.camel@localhost>
On Sun, 2007-23-12 at 08:17 -0500, jamal wrote:
> On Sun, 2007-23-12 at 22:04 +0900, YOSHIFUJI Hideaki / 吉藤英明 wrote:
>
> > If the secondary MACs are used with ARP/NDP, we should take care of
> > that, but I think we use the primary MAC for ARP/NDP, no?
> > (In other words, we always use primary MAC for ARP reply / NA, no?)
>
> I think it maybe a policy decision;
Never mind, that was my body being in a different time zone.
I went back and looked at a little chat i had with Patrick when he
posted with the macvlan driver.
At the moment we are still maintaining the model that a NIC can _only_
appear to have a single MAC to the upper layers. IOW, you have to
instantiate a macvlan device for each of the 16 MAC addresses on the
e1000 if you need to expose them. This means that the ip layer - even
with multiple ip addresses will only ever see one MAC address.
Note also: The name macvlan is a little misleading since it allows for
the above without need for vlans.
cheers,
jamal
next prev parent reply other threads:[~2007-12-24 14:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-23 11:41 [PATCH net-2.6][NEIGH] Updating affected neighbours when about MAC address change David Shwatrz
2007-12-23 12:11 ` YOSHIFUJI Hideaki / 吉藤英明
2007-12-23 12:24 ` David Shwatrz
2007-12-23 12:38 ` YOSHIFUJI Hideaki / 吉藤英明
2007-12-23 12:46 ` jamal
2007-12-23 13:04 ` YOSHIFUJI Hideaki / 吉藤英明
2007-12-23 13:17 ` jamal
2007-12-24 14:33 ` jamal [this message]
2007-12-23 13:04 ` David Shwatrz
2007-12-23 13:13 ` YOSHIFUJI Hideaki / 吉藤英明
2007-12-23 13:21 ` David Shwatrz
2007-12-23 14:02 ` Herbert Xu
2007-12-24 13:38 ` David Shwatrz
2007-12-24 14:50 ` jamal
2007-12-25 0:53 ` Herbert Xu
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=1198506800.9642.40.camel@localhost \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=dshwatrz@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--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).