All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Jean <sj-netfilter@cookinglinux.org>
To: "R. DuFresne" <dufresne@sysinfo.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: --dport/--sport clarification
Date: Mon, 31 Jan 2005 17:00:14 -0500	[thread overview]
Message-ID: <41FEAA6E.1040202@cookinglinux.org> (raw)
In-Reply-To: <Pine.LNX.4.05.10501311643430.18954-100000@darkstar.sysinfo.com>

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.

No, it still stands in iptables.

--sport 80:5000 is allowed.

However, --sports (which is an option to multiport or mport matches) does take
list of port.

--sports 22,80,25,110,...

> 
> Thanks,
> 
> 
> Ron DuFresne

Did I misunderstand your question ?

Samuel


      parent reply	other threads:[~2005-01-31 22:00 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
2005-01-31 22:00 ` Samuel Jean [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=41FEAA6E.1040202@cookinglinux.org \
    --to=sj-netfilter@cookinglinux.org \
    --cc=dufresne@sysinfo.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.