From: "Paul Albert" <palbert@rovingplanet.com>
To: Cedric Blancher <blancher@cartel-securite.fr>
Cc: netfilter@lists.netfilter.org
Subject: RE: iptables and 802.1q tagging
Date: Tue, 27 May 2003 11:41:38 -0600 [thread overview]
Message-ID: <661F9268BBA8CB4EB92CC12B8C42F06912EA7D@pluto.rovingplanet.com> (raw)
Cedric -
Thanks for the info. Now that you mention the layer 3 vs. layer 2
aspects, it makes sense. It appears that I have some reading to do ...
Paul
-----Original Message-----
From: Cedric Blancher [mailto:blancher@cartel-securite.fr]
Sent: Tuesday, May 27, 2003 11:38 AM
To: Paul Albert
Cc: netfilter@lists.netfilter.org
Subject: Re: iptables and 802.1q tagging
Le mar 27/05/2003 à 19:22, Paul Albert a écrit :
> I googled to determine whether an iptables bridge that is filtering on
> IP addresses would be smart enough to pick up on the fact that the
> packets have 802.1Q tags or not. No definitive answer was found. My
> question is just that - does iptables notice that the tag is present
> or will it not know what to do with such a packet?
iptables configures IP layer (OSI 3) and dot1q is layer 2 concept. Thus,
iptables cannot match dot1q extensions.
Nevertheless, you can use ebtables that provides layer 2 filtering on
birdged interfaces and has dot1q matching (vlan match). Using ebtables
you can filter dot1q frames from classicla ones, even match VLAN id,
prio and encapsulated proto.
See http://ebtables.sourceforge.net/
--
Cédric Blancher <blancher@cartel-securite.fr>
Consultant en sécurité des systèmes et réseaux - Cartel Sécurité
Tél: +33 (0)1 44 06 97 87 - Fax: +33 (0)1 44 06 97 99
PGP KeyID:157E98EE FingerPrint:FA62226DA9E72FA8AECAA240008B480E157E98EE
next reply other threads:[~2003-05-27 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 17:41 Paul Albert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-27 17:22 iptables and 802.1q tagging Paul Albert
2003-05-27 17:38 ` Cedric Blancher
2003-05-21 0:08 Paul Albert
2003-09-09 19:15 ` Cedric Blancher
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=661F9268BBA8CB4EB92CC12B8C42F06912EA7D@pluto.rovingplanet.com \
--to=palbert@rovingplanet.com \
--cc=blancher@cartel-securite.fr \
--cc=netfilter@lists.netfilter.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).