From: George Alexandru Dragoi <waruiinu@gmail.com>
To: Tobias DiPasquale <codeslinger@gmail.com>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: iptables mac destination filtering
Date: Sat, 30 Apr 2005 10:18:08 +0300 [thread overview]
Message-ID: <3063e5050430001857a1447b@mail.gmail.com> (raw)
In-Reply-To: <876ef97a0504280410210fc94e@mail.gmail.com>
Use arptables for that, like
arptables -A INPUT --src-mac <mac> --opcode 1 -j DROP
arptables -A OUTPUT --dst-mac <mac> --opcode 1 -j DROP
This way that mac won't know your mac address and won't be able to
comunicate with you. But, a "very" good enough firewall, it is not
necesary to filter destination mac, source mac is enough, arptables is
good to stop somebody DDOS you (if he is in same L2 with you).
On 4/28/05, Tobias DiPasquale <codeslinger@gmail.com> wrote:
> On 4/28/05, Michael Tautschnig <michael.tautschnig@zt-consulting.com> wrote:
> > Could you please explain, why one would do that? IMHO the only possible use is
> > an interface in promiscous mode.
>
> Not really. I know of a project that wanted this functionality in
> order to be able to determine if the next hop was terminal, and if so,
> do some IDS scanning on it. This was in the context of AODV-assembled
> wireless LANs.
>
> --
> [ Tobias DiPasquale ]
> 0x636f6465736c696e67657240676d61696c2e636f6d
>
>
--
Bla bla
next prev parent reply other threads:[~2005-04-30 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 9:39 iptables mac destination filtering Thomas Turquois
2005-04-28 9:55 ` Seferovic Edvin
2005-04-28 9:57 ` Michael Tautschnig
2005-04-28 11:10 ` Tobias DiPasquale
2005-04-30 7:18 ` George Alexandru Dragoi [this message]
2005-04-28 10:13 ` Filip Sneppe
[not found] <200504280955.j3S9tYSQ029850@sunny.fnst.com.cn>
2005-04-28 10:03 ` Yu Zhiguo
2005-04-28 10:14 ` Seferovic Edvin
[not found] <200504281014.j3SAEgpi030006@sunny.fnst.com.cn>
2005-04-28 10:27 ` Yu Zhiguo
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=3063e5050430001857a1447b@mail.gmail.com \
--to=waruiinu@gmail.com \
--cc=codeslinger@gmail.com \
--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 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.