All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Subject: Re: drop dhcp request from a particular mac address, after a dhcp relay
Date: Sat, 13 Mar 2010 09:10:08 +0100	[thread overview]
Message-ID: <4B9B4860.5010509@chello.at> (raw)
In-Reply-To: <937499.80494.qm@web31506.mail.mud.yahoo.com>

On 12.03.2010 03:27, netfilter-owner@vger.kernel.org wrote:
> --- On Wed, 3/10/10, Robert Nichols <rnicholsNOSPAM@comcast.net> wrote:
> 
>  :-
>>>
>>>     iptables ..... -m bootp --mac-source
>> 00:08:a1:ab:75:d1 -j DROP ?
>>>
>>> Well, if 'iptables' can't serve the purpose, how about
>> ebtables ?
>>
>> Wouldn't it be a lot easier to adjust the DHCP server's
>> configuration by
>> adding a "deny" statement in the pool's permit list?
>>
> 
> True but manually editing the configuration file will require the dhcp server to be restarted, whereas 'iptables' and/or 'ebtables' can be scripted at runtime.
> 
> Cheers. 
> 

most likely the dhcp server should have a 'reload' parameter?
actually adding/inserting/deleting iptables rules does just the same (as
a service restart). the whole ruleset inside the kernel gets reloaded
for every single 'runtime' command you place. that is why there is
iptables-restore, which loads all rules at once.

Best regards


Mart

  parent reply	other threads:[~2010-03-13  8:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12  2:27 drop dhcp request from a particular mac address, after a dhcp relay Ming-Ching Tiew
2010-03-12  9:06 ` John Haxby
2010-03-13  8:10 ` Mart Frauenlob [this message]
2010-03-13 16:03   ` Robert Nichols
2010-03-13 16:34     ` Mart Frauenlob
2010-03-13 19:29     ` Sven-Haegar Koch
2010-03-14 21:36       ` Robert Nichols
  -- strict thread matches above, loose matches on Subject: below --
2010-03-10 14:30 Ming-Ching Tiew
2010-03-10 15:30 ` Robert Nichols

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=4B9B4860.5010509@chello.at \
    --to=mart.frauenlob@chello.at \
    --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 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.