From: "Pawel Staszewski" <pstaszewski@artcom.pl>
To: netfilter@lists.netfilter.org
Subject: Re: source-mac filtering
Date: Sun, 11 Jan 2004 01:34:34 +0100 [thread overview]
Message-ID: <005801c3d7da$afe66460$0d04460a@orion> (raw)
In-Reply-To: 200401110025.25675.Antony@Soft-Solutions.co.uk
----- Original Message -----
From: "Antony Stone" <Antony@Soft-Solutions.co.uk>
To: <netfilter@lists.netfilter.org>
Sent: Sunday, January 11, 2004 1:25 AM
Subject: Re: source-mac filtering
On Sunday 11 January 2004 12:13 am, Pawel Staszewski wrote:
> Hello
>
> Maybe try to block broadcast to the "blocked" client....
> "-m pkttype --pkttype broadcast ........."
>
> I use it and this work fine...
You can use a rule with this match in it to stop your DHCP server giving out
addresses?
I thought DHCPD caught the packets before they ever got to netfilter,
therefore you couldn't block the traffic with any sort of rule.
Antony.
--
Ramdisk is not an installation procedure.
Please reply to the
list;
please don't CC
me.
Hmm...
iptables -t raw ??
Maybe this helps...
Paol
next prev parent reply other threads:[~2004-01-11 0:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 23:20 source-mac filtering Håkan Engblom
2004-01-10 23:37 ` Antony Stone
2004-01-11 0:13 ` Pawel Staszewski
2004-01-11 0:25 ` Antony Stone
2004-01-11 0:34 ` Pawel Staszewski [this message]
2004-01-11 5:55 ` Unknown, Alistair Tonner
2004-01-11 16:37 ` Ramin Dousti
2004-01-11 19:05 ` Tarek W.
2004-01-12 6:10 ` Unknown, Alistair Tonner
[not found] ` <200401120110.08378.Alistair Tonner <>
2004-01-12 15:52 ` Ramin Dousti
-- strict thread matches above, loose matches on Subject: below --
2004-01-11 0:43 Håkan Engblom
2004-01-11 0:59 Håkan Engblom
2004-01-11 17:36 Håkan Engblom
2004-01-11 17:39 Håkan Engblom
2004-01-11 17:50 ` Antony Stone
2004-01-12 17:56 ` Ramin Dousti
2004-01-12 16:06 ` Ramin Dousti
2004-01-11 18:16 Håkan Engblom
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='005801c3d7da$afe66460$0d04460a@orion' \
--to=pstaszewski@artcom.pl \
--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