From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: BROUTING VLANS
Date: Mon, 15 Nov 2010 10:43:27 -0600 [thread overview]
Message-ID: <4CE1632F.1080104@riverviewtech.net> (raw)
In-Reply-To: <0619127E-C439-4A2D-A720-30C5B1FD25FA@gmail.com>
On 11/15/10 05:02, Asher Awelan wrote:
> QUESTION:
> Is there a way to broute the vlans to the eth1 interface and not have
> to create every interface and register every vlan... or perhaps strip
> the vlan id (after logging of course)...
It /might/ be possible to strip the VLAN tags and send the traffic on
it's way with out the need for all the vlan interfaces. But, I don't
know that it will be possible (at least as easily) to re-tag the
returning traffic.
Something you might consider doing is moving the (un)tagging / trunking
in to a user space application that can dynamically add and remove the
VLAN tags with out needing kernel support or vlan interfaces. - I'm
just typing raw theories out my (you know what) and would have to give
this quite a bit more thought.
Grant. . . .
next prev parent reply other threads:[~2010-11-15 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 11:02 BROUTING VLANS Asher Awelan
2010-11-15 16:43 ` Grant Taylor [this message]
2010-11-15 17:12 ` Oskar Berggren
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=4CE1632F.1080104@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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