From: "John W. Linville" <linville@tuxdriver.com>
To: Jeremy Jones <jjones@djc.state.id.us>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Bridging vlans...
Date: Thu, 25 Mar 2004 21:32:58 -0500 [thread overview]
Message-ID: <4063965A.103@tuxdriver.com> (raw)
In-Reply-To: 011a01c412d3$f141fe90$f80210ac@djc.state.id.us
Again, I'm no expert. I hope someone will correct me if I'm wrong, blah
blah blah...
To start, I think you should be using ebtables rather than iptables. As
I understand things, the ebtables stuff works at Layer-2.
I guess your purpose is to log untagged packets? Are packets belonging
to VLAN interfaces visible to the parent interface? (It seems intuitive
that they would not be, but I really don't know.) If not, then
something like what you propose below should work (given ebtables
instead of iptables). If the VLAN packets ARE visible on the parent
interface, then you will need to do some additional checking to make
sure that the frames are actually untagged. You may want to do this
anyway so as to differentiate between untagged frames and frames tagged
for an "unknown" VLAN.
Again, hth... :-)
John
Jeremy Jones wrote:
> Now, with iptables, under the first scenario (creating 2 vlan interfaces per
> physical interface, and bridging the vlan interfaces), can I safely DROP
> everything to, from, or through eth0 & eth1? That is, assuming I don't want
> to forward any untagged frames.
>
> So:
>
> iptables -N only_tagged
> iptables -A only_tagged -j LOG --log-prefix " untagged? "
> iptables -A only_tagged -j DROP
> iptables -A INPUT -i eth0 -j only_tagged
> iptables -A INPUT -i eth1 -j only_tagged
> iptables -A OUTPUT -i eth0 -j only_tagged
> iptables -A OUTPUT -i eth1 -j only_tagged
> iptables -A FORWARD -i eth0 -j only_tagged
> iptables -A FORWARD -i eth1 -j only_tagged
>
> Then do my more granular filtering on the vlan interfaces...
>
> (guess this would be something to ask the vlan mailing list people -- but
> what the heck, this list isn't terribly busy anyway)
>
> I imagine I'll have to come up with a fairly complex matrix of --physdev-in,
> --physdev-out, etc. combinations. Yikes.
>
> Jeremy
>
>
>>-----Original Message-----
>>From: bridge-bounces@lists.osdl.org
>>[mailto:bridge-bounces@lists.osdl.org] On Behalf Of John W. Linville
>>Sent: Thursday, March 25, 2004 5:56 AM
>>To: Jeremy Jones
>>Cc: bridge@lists.osdl.org
>>Subject: Re: [Bridge] Bridging vlans...
>>
>>
>>Jeremy,
>>
>>I have no specific experience with a situation like yours. But, that
>>won't stop me from rendering an opinion... :-)
>>
>>I, too, would lean toward the first at least partly for the
>>reason you
>>describe. But, you should also consider untagged frames and
>>frames with
>>other VLAN IDs. The second configuration should bridge all frames
>>(tagged or untagged), while the first will only be bridging
>>frames with
>>VLAN IDs of 4 or 51. I'm not sure which is your desired
>>behaviour, but
>>I suspect it is the first configuration which you should prefer.
>>
>>Hth...
>>
>>John
>>--
>
>
>
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> http://lists.osdl.org/mailman/listinfo/bridge
next prev parent reply other threads:[~2004-03-26 2:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 2:50 [Bridge] Bridging vlans Jeremy Jones
2004-03-25 12:56 ` John W. Linville
2004-03-26 1:44 ` Jeremy Jones
2004-03-26 2:32 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-29 1:01 [Bridge] Bridging VLANs Diego Woitasen
2005-09-23 7:00 Josef Brunner
2005-09-22 12:34 R Harper
2004-03-25 0:23 [Bridge] Bridging vlans Jeremy Jones
2004-03-29 17:39 ` Bart De Schuymer
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=4063965A.103@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bridge@lists.osdl.org \
--cc=jjones@djc.state.id.us \
/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