ok I discoverd after doing my own sniffing, ntpdate does behave how you
describe (123 <-> 123), but xntpd behaves in the way I thought it did goes
out to port 123 on the server from some high port, then the server comes
back on that same high port from 123, I think it was 1051 in my test.
This different behavior could cause problems in that the /etc/init.d/xntpd
start script calls, ntpdate to step the clock before it invokes the daemon.
I guess both behaviors have to be anticipated?
does NAAT use xntpd or just repeated calls to ntpdate or just set up the
rules for xntpd to operate?? I would assume it just sets up the rules. It
seems the behavior it sets up rules for the is the xntpd daemon.
-----Original Message-----
From: R.I.P. Deaddog [mailto:[EMAIL PROTECTED]]
Sent: March 22, 2001 3:39 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [Cooker-firewall] ftp and ntp problems
Did a tcpdump when running ntpdate....... it's communicating using port
123 to port 123.
On Thu, 22 Mar 2001, Gene Moreau wrote:
> I was under the assumption that it came back on some high port. ie
> 1024:65535
>
> -----Original Message-----
> From: R.I.P. Deaddog [mailto:[EMAIL PROTECTED]]
> Sent: March 22, 2001 3:30 PM
> To: Cooker-Firewall (E-mail)
> Subject: Re: [Cooker-firewall] ftp and ntp problems
>
>
>
> Hope I doesn't give false information...... isn't ntp protocol using
> port 123 <--> port 123 ?
>
> Abel Cheung
>
>
> On Thu, 22 Mar 2001, Gene Moreau wrote:
>
> > ntp won't work from the firewall box if I have the rules turned on. I
> even
> > put my ntp servers in the ntp server box. verified the rules are there
> with
> > ipchains -L -n and got this...
> >
> > ACCEPT udp ------ 128.100.100.128 0.0.0.0/0 123
->
> > 1024:65535
> > ACCEPT udp ------ 140.221.9.20 0.0.0.0/0 123
->
> > 1024:65535
>
>
>
