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]
Date:	Fri, 22 Jan 2010 16:11:53 +1300
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Ben Hutchings <bhutchings@...arflare.com>
Cc:	netdev@...r.kernel.org
Subject: Re: VLAN vs bridging receive precedence

Ben Hutchings <bhutchings@...arflare.com> wrote:
>
> It is not clear which behaviour is 'correct'.  However it appears that
> the XenCenter network management software currently depends on the
> accelerated behaviour.

My question would be why would you have both VLAN and bridging
on the same physical interface in the first place?

These two configurations are well-defined and work as expected:

1) Bridging after VLAN: The bridge only includes the VLAN device,
ethX.Y, not the physical ethX.
2) VLAN after bridging: The VLAN should be linked to the bridge
device, i.e., brX.Y, and not the physical ethX.

So what exactly is the admin trying to achieve here?

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