All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erwin Van de Velde <erwin.vandevelde@gmail.com>
To: netfilter-devel@lists.netfilter.org
Cc: Martijn Lievaart <m@rtij.nl>
Subject: Re: MAC Filtering
Date: Wed, 5 Jan 2005 17:12:18 +0100	[thread overview]
Message-ID: <200501051712.18817.erwin.vandevelde@gmail.com> (raw)
In-Reply-To: <17648.213.236.112.75.1104937880.squirrel@213.236.112.75>

Hi,

I don't want to bridge, I only said I have to when using ebtables. I need MAC 
filtering without bridging... I'm fully aware of the fact that iptables works 
on layer 3 and that MAC is layer 2, however if it can filter on source MAC 
addresses, why can't it filter on destination MAC addresses?

Best regards,
Erwin


> If you bridge, you cannot use iptables. Ip tables operates on layer 3
> (routed) and the destination MAC is always the MAC of the firewall.
> Ebtables operates on layer 2 (switched) and can filter traffic based on
> source and destination MAC address.
>
> So I think ebtables is exactly what you need.
>
> HTH,
> Martijn Lievaart

  parent reply	other threads:[~2005-01-05 16:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 13:25 MAC Filtering Erwin Van de Velde
     [not found] ` <17648.213.236.112.75.1104937880.squirrel@213.236.112.75>
2005-01-05 16:12   ` Erwin Van de Velde [this message]
2005-01-05 16:22     ` Patrick Schaaf
2005-01-05 18:16     ` Bart De Schuymer
  -- strict thread matches above, loose matches on Subject: below --
2010-04-21  3:55 mac filtering ratheesh k
2010-04-21  5:54 ` Marek Kierdelewicz
2010-04-21  7:49 ` Lars Nooden
2005-06-29 11:56 MAC filtering varun_saa
2005-06-29 15:58 ` Gustavo Castro Puig
2005-06-29 20:30 ` /dev/rob0
2005-06-14 20:55 MAC Filtering Claude Biron
2005-06-16 16:22 ` Charlie Brady
2004-01-14 23:58 Gopal Chandavarapu
2004-01-14 23:52 Gopal Chandavarapu
2004-01-21 13:55 ` Harald Welte

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=200501051712.18817.erwin.vandevelde@gmail.com \
    --to=erwin.vandevelde@gmail.com \
    --cc=m@rtij.nl \
    --cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.