All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georgi Alexandrov <tehlists@hotpop.com>
To: netfilter@lists.netfilter.org
Subject: Re: Dropping network "noise"
Date: Sun, 13 Feb 2005 15:09:26 +0200	[thread overview]
Message-ID: <420F5186.5060703@hotpop.com> (raw)
In-Reply-To: <1108296226.10876.16.camel@nostromo.bgsecm.com>

Jose Maria Lopez Hernandez wrote:

>El dom, 13-02-2005 a las 09:28 +0300, Mikhail Zotov escribió:
>  
>
>>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
>>    
>>
>
>That's OK, but also DROP port 445 because there's also a great
>amount of traffic in that port.
>
>  
>
How exactly is that OK ? i guess you don't have anything listening on 
135-139/udp, right ?
So you won't "save" any traffic with a rule like that, that's how 
ethernet works.
The only point in a rule like that maybe is - if you are logging not 
matched packets at the end of the filter table/INPUT chain and don't 
want your logs flooded by that broadcast traffic.

>>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
>>    
>>
>
>Yes, it's a rule to prevent spoofing. It's OK *if* and *only if*
>the $IP.ADDRESS.OF.MY_BOX it's really the IP address of your
>box, and the *only* IP address of your box (you can have more
>than one for various reasons).
>
>  
>
>>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?
>>    
>>
>
>NFS doesn't have any problem, but if you receive your IP via
>DHCP you must change the IP in the rule with the one received.
>And also if you use Zeroconf you must have a rule to accept
>the traffic for the Zeroconf IP.
>
>  
>
>>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
>>    
>>
>
>If you are don't want to receive traffic your broadcast it's OK.
>  
>
same thing here ... you will receive that broadcast traffic no matter 
what. dropping it won't help.

>  
>
>>iptables -A FORWARD -i $EXTERIOR_INTERFACE -d ! $LAN.IP.ADDRESSES.RANGE -j DROP
>>    
>>
>
>And this it's another anti-spoofing rule. I'll tell you the same that
>for the previous rule. It's OK if the $LAN.IP.ADDRESSES.RANGE it's OK.
>
>  
>
>>Thanks in advance!
>>
>>--
>>Mikhail
>>    
>>
>
>Regards.
>
>  
>
regards,
Georgi Alexandrov


  reply	other threads:[~2005-02-13 13:09 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 [this message]
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
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=420F5186.5060703@hotpop.com \
    --to=tehlists@hotpop.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.