[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <467B423C.80504@candelatech.com>
Date: Thu, 21 Jun 2007 20:30:04 -0700
From: Ben Greear <greearb@...delatech.com>
To: Patrick McHardy <kaber@...sh.net>
CC: "Eric W. Biederman" <ebiederm@...ssion.com>,
netdev@...r.kernel.org, shemminger@...ux-foundation.org,
davem@...emloft.net, jeff@...zik.org
Subject: Re: [RFC NET 00/02]: Secondary unicast address support
Patrick McHardy wrote:
> Eric W. Biederman wrote:
>> For the macvlan code do we need to do anything special if we transmit
>> to a mac we would normally receive? Another unicast mac of the same
>> nic for example.
>
> That doesn't happen under normal circumstances. I don't believe
> it would work.
Assuming you mean you want to send between two mac-vlans on the same physical
nic...
This can work if your mac-vlans are on different subnets and you are
routing between them (and if you have my send-to-self patch or have
another way to let a system send packets to itself).
A normal ethernet switch will NOT turn a packet around on the same
interface it was received, so that is why you must have them on different
subnets and have a router in between.
For sending directly to yourself, something like the 'veth' driver
is probably more useful.
>
>> For the macvlan hash you just use an upper byte. Is that just a
>> simple starting place, or do we not need a more complex hash.
>>
>
> It comes from the original code, I think it should be good enough.
Ahhh, I knew my hash was lame for some reason!
Ben
--
Ben Greear <greearb@...delatech.com>
Candela Technologies Inc http://www.candelatech.com
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists