From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: Connection tracking and vlan Date: Mon, 02 Nov 2009 09:02:29 -0800 Message-ID: References: <20091030152054.GA7936@gondor.apana.org.au> <4AEB06E6.6020206@gmail.com> <4AEB75DD.8050204@candelatech.com> <4AEF09E7.2010004@trash.net> <4AEF0BAA.7050800@gmail.com> <4AEF0D69.7070205@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Eric Dumazet , Adayadil Thomas , Ben Greear , Herbert Xu , Linux Netdev List , Netfilter Development Mailinglist To: Patrick McHardy Return-path: In-Reply-To: <4AEF0D69.7070205@trash.net> (Patrick McHardy's message of "Mon\, 02 Nov 2009 17\:48\:41 +0100") Sender: netfilter-devel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Patrick McHardy writes: > Eric Dumazet wrote: >> Patrick McHardy a =C3=A9crit : >>> But it would be preferrable if we could do this using network >>> namespaces somehow. >>=20 >> eg eth0.100 and eth0.101 on namespace 1, eth0.200 and eth0.201 on n= amespace 2 ? >>=20 >> Can we do that with current kernel ? (different vlans on an unique p= hysical device) > > By default the underlying device needs to exist in the same namespace > in which the VLAN device is created. I believe it should be possible > to move the VLAN device to a different namespace after creating it, > but I'm not sure about that. There should be no problem moving the vlan device after it is created. Eric -- To unsubscribe from this list: send the line "unsubscribe netfilter-dev= el" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html