Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Anatoly Y." <snelius@tsu.ru>
Cc: netfilter@lists.netfilter.org
Subject: Re: Questions about DHCP firewall rules
Date: Sat, 12 May 2007 11:03:52 +0700	[thread overview]
Message-ID: <46453CA8.3010101@tsu.ru> (raw)
In-Reply-To: <729129.22320.qm@web83819.mail.sp1.yahoo.com>

Timestamp: Sat 12 May 2007, 11:03 +0700 (NOVT)
Nicholas Kline wrote:
> Greetings,
> 
> I am in the process of learning Netfilter/IPtables.  I
> plan on using Netfilter/IPtables to protect my Linux
> desktop computers and servers.  We're talking
> host-based firewalls, not one firewall protecting all
> of the desktops and servers.
> 
> I have a basic question I am hoping someone on this
> mailing list can answer.  I am a little confused about
> configuring Netfilter/IPtables on a Linux desktop
> computer.  Specifically, this situation:
> 
> a linux desktop computer that is configured to use
> DHCP
> and configured to use the following rule:
> 
> $IPTABLES -A INPUT -s $IP_LOCAL -j LOG --log-prefix
> "Spoofed source IP"
> $IPTABLES -A INPUT -s $IP_LOCAL -j DROP
> 
> I would like to include the previous rule as part of a
> standard rule set.
> 
>>From how I understand this situation, the firewall
> would have to be able to automatically detect when the
> computers IP address changes, right?  Manually
> inputting the computers IP address each time it
> changes would get really old.
> 
> I'm using several books as references for learning
> Netfilter/IPtables and they discuss implementing
> "dynamic firewall scripts".  In this case, a dynamic
> firewall script that recognizes when the computers IP
> address changes.
> 
> So, my questions are:
> 
> 1.) If I am using a computer that is configured to
> obtain its IP address through DHCP, what firewall
> rules do I need to setup?
> 
> 2.) Additionally, how do I configure the firewall to
> automatically detect changes in the computers network
> configuration (IP address change, etc.)?

Use full prefix of all fake networks (or your only).
-A INPUT -s 192.168.0.0/16 -j LOG .... for example.

-- 
Anatoly Y. aka Snelius | AY254-RIPE


  reply	other threads:[~2007-05-12  4:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12  1:55 Questions about DHCP firewall rules Nicholas Kline
2007-05-12  4:03 ` Anatoly Y. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-16 20:37 Nicholas Kline
2007-05-17  8:09 ` Elvir Kuric

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=46453CA8.3010101@tsu.ru \
    --to=snelius@tsu.ru \
    --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