Home

 


Issues with "non-ntpport" and "ntpport" Posted on: Tue, 24 Jun 2003 17:30:16 -0400

I am having some problems getting my ntp server to accept ntpdate
requests.

I have several clients behind a gateway/router that need to have their
time updated. I am using NAT to translate their source addresses to just
one address. This is causing some of the clients to make attempts at
communicating with my ntp server via a non-standard port (something other
than 123) as their source port.

Basically, I see that the connection is in fact being made from the
client's side (with a --sport = 46 and a --dport = 123) but my ntp server
is evidently dropping the packets.

I have tried using this as my restrict rule:

restrict a.b.c.d notrust nomodify notrap non-ntpport

this:

restrict a.b.c.d notrust nomodify notrap non-ntpport ntpport

and this:

restrict a.b.c.d notrust nomodify notrap ntpport

with no luck whatsoever...

How can I get my ntp server to allow such non-standard communication?

Regards,

Wendell Smith
26130. Issues with "non-ntpport" and "ntpport"
26134. Issues with "non-ntpport" and "ntpport"
26136. Issues with "non-ntpport" and "ntpport"
26137. Issues with "non-ntpport" and "ntpport"
26140. Issues with "non-ntpport" and "ntpport"
26143. Issues with "non-ntpport" and "ntpport"
26144. Issues with "non-ntpport" and "ntpport"
26145. Issues with "non-ntpport" and "ntpport"
26147. Issues with "non-ntpport" and "ntpport"
26148. Issues with "non-ntpport" and "ntpport"
26149. Issues with "non-ntpport" and "ntpport"
26150. Issues with "non-ntpport" and "ntpport"
26151. Issues with "non-ntpport" and "ntpport"
26152. Issues with "non-ntpport" and "ntpport"
26153. Issues with "non-ntpport" and "ntpport"
26155. Issues with "non-ntpport" and "ntpport"
26156. Issues with "non-ntpport" and "ntpport"
26158. Issues with "non-ntpport" and "ntpport"
26159. Issues with "non-ntpport" and "ntpport"
26161. Issues with "non-ntpport" and "ntpport"