netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Patrick McHardy <kaber@trash.net>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	Adayadil Thomas <adayadil.thomas@gmail.com>,
	Ben Greear <greearb@candelatech.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Linux Netdev List <netdev@vger.kernel.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@vger.kernel.org>
Subject: Re: Connection tracking and vlan
Date: Mon, 02 Nov 2009 09:02:29 -0800	[thread overview]
Message-ID: <m14opcj1wa.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4AEF0D69.7070205@trash.net> (Patrick McHardy's message of "Mon\, 02 Nov 2009 17\:48\:41 +0100")

Patrick McHardy <kaber@trash.net> writes:

> Eric Dumazet wrote:
>> Patrick McHardy a écrit :
>>> But it would be preferrable if we could do this using network
>>> namespaces somehow.
>> 
>> eg eth0.100 and eth0.101 on namespace 1,  eth0.200 and eth0.201 on namespace 2 ?
>> 
>> Can we do that with current kernel ? (different vlans on an unique physical 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-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-11-02 17:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 15:43 Connection tracking and vlan Adayadil Thomas
2009-10-30 15:20 ` Herbert Xu
2009-10-30 15:31   ` Eric Dumazet
2009-10-30 15:46     ` Herbert Xu
2009-10-30 16:19       ` Eric Dumazet
2009-10-30 16:27         ` Patrick McHardy
2009-10-30 16:55         ` Herbert Xu
2009-10-30 16:26     ` Patrick McHardy
2009-10-30 19:20     ` Adayadil Thomas
2009-10-30 19:51       ` Caitlin Bestler
2009-10-30 20:40         ` Adayadil Thomas
2009-10-30 23:15       ` Eric W. Biederman
2009-10-30 23:25         ` Ben Greear
2009-11-02 16:14           ` Adayadil Thomas
2009-11-02 16:30             ` Adayadil Thomas
2009-11-02 16:33             ` Patrick McHardy
2009-11-02 16:41               ` Eric Dumazet
2009-11-02 16:48                 ` Patrick McHardy
2009-11-02 17:02                   ` Eric W. Biederman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m14opcj1wa.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=adayadil.thomas@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).