(Applogies for not maintaining thread id, I'm not subscribed.)
>> We don't have any clean interfaces by which to do this MAC
>> programming, and we do need something for it soon.
>Yep, that's been on my long term wish list for a while, as well.
>Overall I would like to see a more flexible way o
Prafulla Deuskar wrote:
On 6/19/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
David Miller wrote:
> This is actually a real issue for virtualization, and many
> if not all current generation ethernet chips support
> programming several unicast ethernet addresses in the MAC.
>
> Networking switches
On 6/19/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
David Miller wrote:
> This is actually a real issue for virtualization, and many
> if not all current generation ethernet chips support
> programming several unicast ethernet addresses in the MAC.
>
> Networking switches in domain0 on virtualizat
David Miller wrote:
This is actually a real issue for virtualization, and many
if not all current generation ethernet chips support
programming several unicast ethernet addresses in the MAC.
Networking switches in domain0 on virtualization hosts use
this feature to support seperate MACs per gues
David Miller wrote:
From: Patrick McHardy <[EMAIL PROTECTED]>
Date: Tue, 19 Jun 2007 23:14:21 +0200
Stephen Hemminger wrote:
Looks good. I have some changes to allow devices with multiple MAC addresses
(never finished). This device could use that.
How would the driver do that?
From: Patrick McHardy <[EMAIL PROTECTED]>
Date: Tue, 19 Jun 2007 23:14:21 +0200
> Stephen Hemminger wrote:
> > Looks good. I have some changes to allow devices with multiple MAC addresses
> > (never finished). This device could use that.
>
>
> How would the driver do that? I was thinking about
On Tue, 19 Jun 2007 23:14:21 +0200
Patrick McHardy <[EMAIL PROTECTED]> wrote:
> Stephen Hemminger wrote:
> > Looks good. I have some changes to allow devices with multiple MAC addresses
> > (never finished). This device could use that.
>
>
> How would the driver do that? I was thinking about us
Stephen Hemminger wrote:
> Looks good. I have some changes to allow devices with multiple MAC addresses
> (never finished). This device could use that.
How would the driver do that? I was thinking about using dev_add_mc,
but wasn't sure if that would work with all drivers for non-multicast
addre
On 6/19/07, Stephen Hemminger <[EMAIL PROTECTED]> wrote:
Looks good. I have some changes to allow devices with multiple MAC addresses
(never finished). This device could use that.
Stephen,
Is this patch available somewhere? I'd be interested in taking a look at it.
- Chris
-
To unsubscribe
On Tue, 19 Jun 2007 15:08:41 +0200 (MEST)
Patrick McHardy <[EMAIL PROTECTED]> wrote:
> These patches add a rewritten version of Ben's macvlan driver, which
> allows to create virtual ethernet devices. The underlying device is
> put in promiscous mode and packets are demuxed based on MAC address.
>
These patches add a rewritten version of Ben's macvlan driver, which
allows to create virtual ethernet devices. The underlying device is
put in promiscous mode and packets are demuxed based on MAC address.
It behaves similar to bridge devices in that packets are visible on
the real device before de
11 matches
Mail list logo
