Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: --dport/--sport clarification
Date: Mon, 31 Jan 2005 16:53:42 -0500	[thread overview]
Message-ID: <20050131215342.GA26235@bender.817west.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10501311643430.18954-100000@darkstar.sysinfo.com>

On Mon, Jan 31, 2005 at 04:45:52PM -0500, R. DuFresne wrote:
> ipfwadm and I believe ipchains allowed port ranges, as in 135:139.  Does
> this worj te same with --dport/--sport?  My reading indicates the list or
> 'range' requires that the ports be a comma seperated list, rather then the
> ole 'range' option of old.

both --sport and --dport support the port[:port] syntax (this is in the
man page of iptables).  the comma-separated list syntax is a feature of
the multiport/mport matches.  multiport only supports a comma-separated
list of single ports, while mport supports a comma separated list of
single ports or ranges (where ranges eat up two values).  both multiport
and mport have a element max of 15.

i.e., all of the following are valid:

  Syntax				Ports
  ---------------------------------------------------------------------
  --dport 137:139			137 - 139
  --sport 1:1023			1 - 1024
  --sport 1024:				1024 - 65535

  -m multiport --dports 80,443		80 and 443
  -m mport --dports 21:23,80,443	21, 22, 23, 80 and 443

HTH...

-j

--
"Me lose brain? Uh, oh! Ha ha ha! Why I laugh?"
        --The Simpsons


  reply	other threads:[~2005-01-31 21:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31 21:45 --dport/--sport clarification R. DuFresne
2005-01-31 21:53 ` Jason Opperisano [this message]
2005-01-31 22:00 ` Samuel Jean

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=20050131215342.GA26235@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox