* NTP
@ 2004-07-02 10:57 Steve Comfort
2004-07-02 11:06 ` NTP Gavin Hamill
2004-07-02 11:08 ` NTP Antony Stone
0 siblings, 2 replies; 9+ messages in thread
From: Steve Comfort @ 2004-07-02 10:57 UTC (permalink / raw)
To: netfilter
Hi all,
Could someone tell me what rules I need in order to enable NTP?
Best regards
Steve
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: NTP
2004-07-02 10:57 NTP Steve Comfort
@ 2004-07-02 11:06 ` Gavin Hamill
2004-07-02 11:08 ` NTP Antony Stone
1 sibling, 0 replies; 9+ messages in thread
From: Gavin Hamill @ 2004-07-02 11:06 UTC (permalink / raw)
To: netfilter
On Friday 02 July 2004 11:57, Steve Comfort wrote:
> Hi all,
>
> Could someone tell me what rules I need in order to enable NTP?
Simply allow incoming UDP on port 123. The 'normal' way is for both the source
and destination ports to be 123, but it is common (esp. with debugging) for
the source port to be >1024.
Cheers,
Gavin.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: NTP
2004-07-02 10:57 NTP Steve Comfort
2004-07-02 11:06 ` NTP Gavin Hamill
@ 2004-07-02 11:08 ` Antony Stone
1 sibling, 0 replies; 9+ messages in thread
From: Antony Stone @ 2004-07-02 11:08 UTC (permalink / raw)
To: netfilter
On Friday 02 July 2004 11:57 am, Steve Comfort wrote:
> Hi all,
>
> Could someone tell me what rules I need in order to enable NTP?
NTP uses UDP port 123.
What rules you need depends on what you're trying to do - run an NTP server
(allow UDP 123 in the INPUT chain), access an NTP server (allow UDP 123 in
the OUTPUT chain), or allow clients and servers to talk to each other through
a router (allow UDP 123 through the FORWARD chain).
If in doubt, add a LOG rule, try using the protocol, and see what gets logged
- that will tell you what sort of packets you need to ACCEPT instead.
Regards,
Antony.
--
Software development can be quick, high quality, or low cost.
The customer gets to pick any two out of three.
Please reply to the list;
please don't CC me.
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: NTP
@ 2004-07-02 16:28 Hudson Delbert J Contr 61 CS/SCBN
2004-07-02 18:06 ` NTP Antony Stone
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Hudson Delbert J Contr 61 CS/SCBN @ 2004-07-02 16:28 UTC (permalink / raw)
To: 'Gavin Hamill', netfilter
do not i repeat...do not allow inbound ntp with a source port above the root
ports.
####################################
# delbert.hudson@losangeles.af.mil #
# 61cs/scbn, 3-0182 #
####################################
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Gavin Hamill
Sent: Friday, July 02, 2004 4:07 AM
To: netfilter@lists.netfilter.org
Subject: Re: NTP
On Friday 02 July 2004 11:57, Steve Comfort wrote:
> Hi all,
>
> Could someone tell me what rules I need in order to enable NTP?
Simply allow incoming UDP on port 123. The 'normal' way is for both the
source
and destination ports to be 123, but it is common (esp. with debugging) for
the source port to be >1024.
Cheers,
Gavin.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: NTP
2004-07-02 16:28 NTP Hudson Delbert J Contr 61 CS/SCBN
@ 2004-07-02 18:06 ` Antony Stone
2004-07-02 19:23 ` NTP Mark E. Donaldson
2004-07-02 19:40 ` NTP Gavin Hamill
2004-07-05 18:23 ` NTP Antony Stone
2 siblings, 1 reply; 9+ messages in thread
From: Antony Stone @ 2004-07-02 18:06 UTC (permalink / raw)
To: netfilter
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.
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Gavin Hamill
> Sent: Friday, July 02, 2004 4:07 AM
> To: netfilter@lists.netfilter.org
> Subject: Re: NTP
>
> On Friday 02 July 2004 11:57, Steve Comfort wrote:
> > Hi all,
> >
> > Could someone tell me what rules I need in order to enable NTP?
>
> Simply allow incoming UDP on port 123. The 'normal' way is for both the
> source
> and destination ports to be 123, but it is common (esp. with debugging) for
> the source port to be >1024.
>
> Cheers,
> Gavin.
--
There's no such thing as bad weather - only the wrong clothes.
- Billy Connolly
Please reply to the list;
please don't CC me.
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: NTP
2004-07-02 18:06 ` NTP Antony Stone
@ 2004-07-02 19:23 ` Mark E. Donaldson
0 siblings, 0 replies; 9+ messages in thread
From: Mark E. Donaldson @ 2004-07-02 19:23 UTC (permalink / raw)
To: netfilter
-----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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: NTP
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:40 ` Gavin Hamill
2004-07-05 18:23 ` NTP Antony Stone
2 siblings, 0 replies; 9+ messages in thread
From: Gavin Hamill @ 2004-07-02 19:40 UTC (permalink / raw)
To: netfilter
On Friday 02 July 2004 17:28, 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.
Hi Delbert - would you mind expanding on this to include the reasons why?
Cheers,
Gavin.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: NTP
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:40 ` NTP Gavin Hamill
@ 2004-07-05 18:23 ` Antony Stone
2004-07-05 19:27 ` NTP Rob Sterenborg
2 siblings, 1 reply; 9+ messages in thread
From: Antony Stone @ 2004-07-05 18:23 UTC (permalink / raw)
To: netfilter
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.
Was there ever a follow-up reply about this?
Several people asked for more details, a bit of explanation, or a reference to
find out more - I didn't see anything back again from Hudson Delbert J Contr?
I'd be very interested to know the reason for the recommendation.
Regards,
Antony.
--
Perfection in design is achieved not when there is nothing left to add, but
rather when there is nothing left to take away.
- Antoine de Saint-Exupery
Please reply to the list;
please don't CC me.
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: NTP
2004-07-05 18:23 ` NTP Antony Stone
@ 2004-07-05 19:27 ` Rob Sterenborg
0 siblings, 0 replies; 9+ messages in thread
From: Rob Sterenborg @ 2004-07-05 19:27 UTC (permalink / raw)
To: netfilter
> > do not i repeat...do not allow inbound ntp with a source port above
> > the root ports.
>
> Was there ever a follow-up reply about this?
Not according to my mail history.
Maybe he went on holliday and therefore cannot elaborate on this ..?
Gr,
Rob
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2004-07-05 19:27 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-02 10:57 NTP Steve Comfort
2004-07-02 11:06 ` NTP Gavin Hamill
2004-07-02 11:08 ` NTP Antony Stone
-- strict thread matches above, loose matches on Subject: below --
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 ` NTP Mark E. Donaldson
2004-07-02 19:40 ` NTP Gavin Hamill
2004-07-05 18:23 ` NTP Antony Stone
2004-07-05 19:27 ` NTP Rob Sterenborg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox