Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ted Kaczmarek <tedkaz@optonline.net>
To: firewalldude@newkirk.us
Cc: netfilter@lists.netfilter.org
Subject: Re: udp/tcp port range rules for forward/input chains
Date: Thu, 16 Oct 2003 17:34:03 -0400	[thread overview]
Message-ID: <1066340042.6368.21.camel@tarkus> (raw)
In-Reply-To: <1066199232.20310.4.camel@alpha.newkirk.us>

As it turned out their was a hidden character in one of my logging rules
which was totally messing with my head :-)



Thanks,
Ted
On Wed, 2003-10-15 at 02:27, Joel Newkirk wrote:
> On Tue, 2003-10-14 at 23:10, Ted Kaczmarek wrote:
> > Digging around the only thing I found was a patch-o-matic that allowed
> > for doing a range of 15 ports.
> > 
> > I see many references with dnat and snat, but nothing besides the patch
> > for input or forward chains.
> > 
> > If anyone has a link that or info that can steer me in the right
> > direction the beers are on me at the Javits Center Linux show.
> > 
> > Thanks,
> > Ted
> 
> Do you mean something like specifying tpc port 135 through 139 in a
> single rule?
> 
> iptables -A INPUT -i $EXTIF -p tcp --dport 135:139 -j DROP
> 
> If you mean non-contiguous ports, you're looking at multiport:
> 
> iptables -A INPUT -p tcp -m mulitport --dport 21,25,80,110,143,443 -j
> ACCEPT
> 
> Multiport is limited to 15 ports per rule.
> 
> j



  reply	other threads:[~2003-10-16 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15  3:10 udp/tcp port range rules for forward/input chains Ted Kaczmarek
2003-10-15  6:27 ` Joel Newkirk
2003-10-16 21:34   ` Ted Kaczmarek [this message]
2003-10-16 21:49     ` Joel Newkirk

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=1066340042.6368.21.camel@tarkus \
    --to=tedkaz@optonline.net \
    --cc=firewalldude@newkirk.us \
    --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