lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1LD9nz-0007sR-OP@gondolin.me.apana.org.au>
Date:	Thu, 18 Dec 2008 14:44:07 +1100
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	kaber@...sh.net (Patrick McHardy)
Cc:	ipng@...06e6720323030352d30312d31340a.nosense.org,
	netdev@...r.kernel.org
Subject: Re: Is it valid to add a macvlan virtual interface to a bridge? If so, there seems to be a bug with it.

Patrick McHardy <kaber@...sh.net> wrote:
> 
>> I've had a look at the dev.c file in 2.6.27, and my very naive guess
>> is that as the handle_bridge() call is before the handle_macvlan() call,
>> because the incoming real physical interface is not part of the bridge,
>> the incoming unicast packet is being dropped, before the macvlan code
>> gets a look at it.
> 
> Yes, that seems correct.

Would it be possible to implement promiscuous mode for macvlans by
simply keeping a separate list of macvlan devices in promiscuous
mode and sending all inbound packets to them?

This should make bridging work, right?

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ