Jason Lixfeld wrote:
> The main issue here is that the NAT box ahead of my
> internal NTP server changes the source port of the
> output NTP request to some low port < 123,
> which ntpd seems to reject.
> Modifying the configuration on my NAT box may be an option as well.
If you believe in RFCs
On Sun, Apr 15, 2012 at 13:08, Jason Lixfeld wrote:
> Hi,
>
> Per
> http://groups.google.com/group/comp.protocols.time.ntp/msg/5a0f45eaecc06578
> I checked ntp_proto.c and found that in the latest 4.2.7, the same issue
> seems to persist as what David was suggesting was the underlying issue.
>
>
Jason Lixfeld wrote:
> To circle back around, the main issue here is that the NAT box ahead of my
> internal NTP server changes the source port of the output NTP request to some
> low port < 123, which ntpd seems to reject. Modifying the configuration on
> my NAT box may be an option as well.
Hi,
Per http://groups.google.com/group/comp.protocols.time.ntp/msg/5a0f45eaecc06578
I checked ntp_proto.c and found that in the latest 4.2.7, the same issue seems
to persist as what David was suggesting was the underlying issue.
/*
* Monitor the packet and get restrictions. Not
