From: "Mark E. Donaldson" <markee@bandwidthco.com>
To: netfilter@lists.netfilter.org
Subject: RE: NTP
Date: Fri, 2 Jul 2004 12:23:37 -0700 [thread overview]
Message-ID: <SERVER7IIZS2TRqf69a00000056@server7.bandwidthco.com> (raw)
In-Reply-To: <200407021906.41982.Antony@Soft-Solutions.co.uk>
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Antony Stone
Sent: Friday, July 02, 2004 11:07 AM
To: netfilter@lists.netfilter.org
Subject: Re: NTP
On Friday 02 July 2004 5:28 pm, Hudson Delbert J Contr 61 CS/SCBN wrote:
> do not i repeat...do not allow inbound ntp with a source port above
> the root ports.
Why not? What difference does the client's source port make?
Antony.
Yes - I'm quite curious about this too as the protocol "normally" acts as
follows:
Client > 1023 -> Server 123
Server 123 -> Client > 1023
Server 123 -> Server 123
next prev parent reply other threads:[~2004-07-02 19:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 16:28 NTP Hudson Delbert J Contr 61 CS/SCBN
2004-07-02 18:06 ` NTP Antony Stone
2004-07-02 19:23 ` Mark E. Donaldson [this message]
2004-07-02 19:40 ` NTP Gavin Hamill
2004-07-05 18:23 ` NTP Antony Stone
2004-07-05 19:27 ` NTP Rob Sterenborg
-- strict thread matches above, loose matches on Subject: below --
2016-06-17 6:33 NTP Anicic Damir (PSI)
2016-06-17 6:47 ` NTP piotr.lewicki
2016-06-17 6:55 ` NTP Anicic Damir (PSI)
2016-06-17 7:02 ` NTP piotr.lewicki
2016-06-17 7:03 ` NTP akuster
2016-06-17 10:26 ` NTP Jussi Kukkonen
2007-02-02 8:47 ntp zhangxiliang
2007-02-02 9:10 ` ntp Matti Aarnio
2007-02-05 2:06 ` ntp zhangxiliang
2007-02-05 8:22 ` ntp David Schwartz
2007-02-04 7:59 ` ntp David Schwartz
2004-07-02 10:57 NTP Steve Comfort
2004-07-02 11:06 ` NTP Gavin Hamill
2004-07-02 11:08 ` NTP Antony Stone
2004-02-26 8:08 ntp Luca Ferrari
2004-02-26 9:09 ` ntp Jeffrey Morse
2004-02-26 9:19 ` ntp Jeffrey Morse
2004-02-26 9:24 ` ntp terry white
2004-02-26 9:47 ` ntp Milan P. Stanic
2004-02-26 14:59 ` ntp Milan P. Stanic
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=SERVER7IIZS2TRqf69a00000056@server7.bandwidthco.com \
--to=markee@bandwidthco.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.