All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: droping too many ports
Date: Thu, 23 Sep 2004 16:14:53 -0500	[thread overview]
Message-ID: <41533CCD.1060706@pbl.ca> (raw)
In-Reply-To: <a0f69e504092313454a9090b3@mail.gmail.com>

Askar wrote:
> hi all
> 
> what if I do (and im doing this from last two hours ;))
> 
> iptables -A FORWARD -p tcp --dport 31000:65500 -j DROP
> iptables -A FORWARD -p udp --dport 31000:65500 -j DROP

[snip]

> iptables -L -nvx  gives too many counts whenever I checked, especailly
> numbers are very high for UDP "udp --dport 31000:65500 -j DROP"

Depending on your other rules this might not be good idea.  Here's an 
example why.  If client connects to say your web server, it may look 
something like this:

  client sport 54321 to server dport 80     for incoming packets
  server sport 80    to client dport 54321  for outgoing packets

As you can guess by now, your rules are blocking outgoing packets of an 
perfectly legal connection.

BTW, you should really consider setting default policy to DROP, and 
allow only what you need.

-- 
Aleksandar Milivojevic <amilivojevic@pbl.ca>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7


      parent reply	other threads:[~2004-09-23 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 20:45 droping too many ports Askar
2004-09-23 20:51 ` Gavin Hamill
2004-09-23 21:01 ` Jason Opperisano
2004-09-23 21:14 ` Aleksandar Milivojevic [this message]

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=41533CCD.1060706@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --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.