From: MargoAndTodd <margoandtodd@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: what should I use for "unassigned" ports?
Date: Thu, 07 Jan 2010 11:03:54 -0800 [thread overview]
Message-ID: <4B46301A.5080207@gmail.com> (raw)
In-Reply-To: <56378e321001061233o121c12fgadc33b03639343c8@mail.gmail.com>
On 01/06/2010 12:33 PM, Richard Horton wrote:
> 2010/1/6 Anthony Ewell<amewell@verizon.net>:
>
>> 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?
>>
>
> Sadly these days nope - the assigned port numbers are now all over the place.
>
> However, alot of them are not likely to be in use on your system so
> you ought to define your unassigned port range by what you are
> actually running not by the contents of /etc/services (same goes for
> protocols).
So, pick the highest port I use and go somewhat above that.
That will work. Thank you!
-T
next prev parent reply other threads:[~2010-01-07 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 18:12 what should I use for "unassigned" ports? Anthony Ewell
2010-01-06 20:33 ` Richard Horton
2010-01-07 19:03 ` MargoAndTodd [this message]
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=4B46301A.5080207@gmail.com \
--to=margoandtodd@gmail.com \
--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