From: Anthony Ewell <amewell@verizon.net>
To: netfilter@vger.kernel.org
Subject: what should I use for "unassigned" ports?
Date: Wed, 06 Jan 2010 10:12:07 -0800 [thread overview]
Message-ID: <4B44D277.3000801@verizon.net> (raw)
Hi All,
A long time ago, I used
unassgn=1024:65535
for my unassigned ports. As in
--sport $unassgn
Having taken a more recent look at "/etc/services", I
am finding zillions of service ports above 1024.
With that in mind, is there a better starting port
for my "unassigned" ports?
Many thanks,
-T
--
-------------------------
I Fish. Therefore, I am.
-------------------------
next reply other threads:[~2010-01-06 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 18:12 Anthony Ewell [this message]
2010-01-06 20:33 ` what should I use for "unassigned" ports? Richard Horton
2010-01-07 19:03 ` MargoAndTodd
2010-01-07 11:36 ` Pascal Hambourg
2010-01-07 11:56 ` Richard Horton
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=4B44D277.3000801@verizon.net \
--to=amewell@verizon.net \
--cc=netfilter@vger.kernel.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