Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Michail Zhilkin <myz@csu.ru>
To: netfilter@vger.kernel.org
Subject: ebtables without bridge
Date: Sat, 31 Jan 2009 03:32:58 +0500 (YEKT)	[thread overview]
Message-ID: <20090131024543.M20230@mail.csu.ru> (raw)

Hi ALL!

I have a box running Fedora 9 Linux with kernel 2.6.26.3 SMP x86_64.
All necessary Netfilter kernel modules are compiled and loaded.

I have no bridge interfaces at all, only one physical Ethernet card.

Is it possible to filter incoming and outgoing Layer2 traffic using 
ebtables in this case?

I tried to load simple rules to test ebtables firewall:

[root@space]# ebtables -P INPUT DROP
[root@space]# ebtables -P OUTPUT DROP
[root@space]# ebtables -P FORWARD DROP
[root@space]# ebtables -L --Ln
Bridge table: filter

Bridge chain: INPUT, entries: 0, policy: DROP

Bridge chain: FORWARD, entries: 0, policy: DROP

Bridge chain: OUTPUT, entries: 0, policy: DROP


All traffic should be blocked, but I can send and receive everything... 
f.e. can ping hosts in my LAN, make connections and so on.

I tried also to set up some rules like: ebtables -A INPUT -i eth0 -j DROP
but they have the same effect!

What is wrong? Are ebtables really designed for bridges only?
If so, what cat I do?

I would like to drop all Layer2 traffic except 
Ethernet frames with IPv4 and ARP protocols. In addition, i need only 
allow frames with my MAC-address (incoming and outgoing, i.e. locally 
generated).

The second is possible using iptables firewall (with -m mac), but only for 
INCOMING frames, not outgoing.

---
   Mike.

             reply	other threads:[~2009-01-30 22:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 22:32 Michail Zhilkin [this message]
2009-01-31 10:11 ` ebtables without bridge Pascal Hambourg

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=20090131024543.M20230@mail.csu.ru \
    --to=myz@csu.ru \
    --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