All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Dropping network "noise"
Date: Tue, 15 Feb 2005 11:15:20 -0500	[thread overview]
Message-ID: <20050215161520.GA19496@bender.817west.com> (raw)
In-Reply-To: <200502130928.41225.e-boogie@yandex.ru>

On Sun, Feb 13, 2005 at 09:28:41AM +0300, Mikhail Zotov wrote:
> Hello everybody,
> 
> I have a Linux machine (with a static routable IP address)
> connected to a windoops LAN.  As is known, there is certain
> "noise" in windoops networks, which can be silently dropped
> by a rule like this:
> 
> iptables -A INPUT -p udp --dport 135:139 -j DROP
> 
> I have found that this "noise" can also be effectively blocked
> by the following rule:
> 
> iptables -A INPUT -d ! $IP.ADDRESS.OF.MY_BOX -j DROP
> 
> I haven't noticed anything going wrong yet, still I'd like to
> know: Does this rule have a (potential) drawback?  Can it break
> anything in case I have NFS or obtain IP address via DHCP or
> in any other situation?
> 
> A similar question goes for the case of a Linux router/gateway
> protecting a LAN (with machines with routable IP addresses).
> Can the following rules do any harm?
> 
> iptables -A FORWARD -i $EXTERIOR_INTERFACE -d $LAN.BROADCAST -j DROP
> iptables -A FORWARD -i $EXTERIOR_INTERFACE -d ! $LAN.IP.ADDRESSES.RANGE -j DROP

you can also use the pkttype match to drop broadcast/multicast traffic,
without having to calculate the broadcast address for every interface,
and having another rule for the all-ones broadcast:

  -m pkttype --pkt-type broadcast -j DROP
  -m pkttype --pkt-type multicast -j DROP

-j

--
"Boy, if you want anything in this life, you have to work for it. Now
 be quiet while I listen for these lottery numbers."
        --The Simpsons


  parent reply	other threads:[~2005-02-15 16:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-13  6:28 Dropping network "noise" Mikhail Zotov
2005-02-13 12:03 ` Jose Maria Lopez Hernandez
2005-02-13 13:09   ` Georgi Alexandrov
2005-02-13 13:30     ` Mikhail Zotov
2005-02-13 13:56     ` Jose Maria Lopez Hernandez
2005-02-13 20:54       ` R. DuFresne
2005-02-13 21:35         ` Jose Maria Lopez Hernandez
2005-02-13 13:30   ` Mikhail Zotov
2005-02-15 16:15 ` Jason Opperisano [this message]
2005-02-16  7:34   ` Mikhail Zotov
2005-02-16 13:28     ` Jason Opperisano
2005-02-16 13:51       ` Mikhail Zotov

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=20050215161520.GA19496@bender.817west.com \
    --to=opie@817west.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.