Date: Sun, 13 Jan 2002 23:44:37 -0500 From: "Joe & Fhe Barbish" <barbish@a1poweruser.com> To: "Drew Tomlinson" <drew@mykitchentable.net> Cc: "FBSD Questions" <questions@FreeBSD.ORG> Subject: RE: ntpd as time server? Message-ID: <LPBBIGIAAKKEOEJOLEGOIEHDCMAA.barbish@a1poweruser.com> In-Reply-To: <002801c19c66$b25e0d30$0301a8c0@bigdaddy>
next in thread | previous in thread | raw e-mail | index | archive | help
Drew I created the /etc/ntp.conf with server statements and a drift statements. In rc.conf, I first have ntpdate do a brute force time adjust followed by xntpd. When booting I see ntpdate and ntp started and when user ppp gets connected I can see in the firewall accounting counts that ntpdate goes out over tcp and then ntp starts using udp to talk to the servers I defined in ntp.conf. I thought I would see 3 or 5 packets pass through udp to port 123 as the remote time servers are accessed to build the data ntp needs to average the clock time. What I see are a continuous exchange of packets to those remote time services. Like 250 in a half hour and still going. I look at the drift file and it's blank. I get on a winbox and change the socketwatch to point to the IP address of the FBSD Nic card that winbox goes through and the win socketwatch program returns a message can not find host. I checked the socketwatch help and it says it uses SNTP to talk to the time server. Is this why it can not find the FBSD ntpd server? In a prevoius response you said you have a Win ntp client program called "Automochron" that runs on the Win2K machine. Please tell me the detailes about this pgm. Can I download it from the internet? Thanks Joe -----Original Message----- From: Drew Tomlinson [mailto:drew@mykitchentable.net] Sent: Sunday, January 13, 2002 2:16 PM To: Joe & Fhe Barbish Cc: questions@freebsd.org Subject: Re: ntpd as time server? ----- Original Message ----- From: Joe & Fhe Barbish To: Drew Tomlinson Cc: FBSD Questions Sent: Sunday, January 13, 2002 10:12 AM Subject: RE: ntpd as time server? Joe wrote > The final option is ntpd. This function does get the time from a > internet ntp server to update the requesting FBSD box, and keeps > the clock accurate by making very small adjustment over long periods > of time. It can be configurated to broadcast time packets to all > machines on the private net it is connected to. > It is not a ntp time server with a unique IP address. Drew wrote I don't think this is correct. ntpd *IS* a time server and the IP address is the address of the machine you run it on. On my private network, I have a FBSD box on 192.168.20.4. I have a Win2K machine on 192.168.20.3. I have a ntp client program called "Automochron" that runs on the Win2K machine. In the client, I have the time server listed as 192.168.20.4 (the FBSD machine). The Win2K client gets time updates. Joe writes back. When you say "I have a FBSD box on 192.168.20.4." Is this the IP address of the Nic card on the FBSD box that's talking to the machines down line, or is it the public IP address your private network is known by? 127.0.0.0 is the only IP address that I know of that is this FBSD box. I have 3 Nics, How would I get all the Winboxs on all the Nics to point to one single IP address for the ntp time server? Drew answers: It's my internal interface (downline). If all your Winboxes can connect to your FBSD box then just use whatever address that is that your Winboxes use to connect. For example, let's say NIC1 serves Win subnet A and NIC2 serves Win subnet B. Then you would set Winboxes on subnet A to get ntp updates from the ip address of NIC1 and Winboxes on subnet B to get ntp updates from the ip address of NIC2. Or if you have the appropriate routers (this may be your FBSD box alone or other routers) such that all 3 of your subnets can communicate with the others (i.e. Winbox on NIC2 can talk to Winbox on NIC1) then it shouldn't matter which IP address you tell the Winboxes to use as all NICs are reachable. HTH, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?LPBBIGIAAKKEOEJOLEGOIEHDCMAA.barbish>