[ntp:questions] Trace ntp sanity checks?
Hello, we are having problems to synchronize linux aix ntp-clients to a ntp-broadcastserver. ntp-broadcast-packets are received by the clients, but all servers are rejected by the clients after a few minutes. we found out, that the ntp-servers do not pass the sanity-checks on the clients and get probably rejected because of that. How can we further track down which of the sanity-checks fails and why... Thanks in advance Frank ___ This E-Mail is confidential. If you are not the intended recipient, you must not copy, disclose or use its contents. If you have received it in error, please inform us immediately by return E-Mail and delete the document. Diese E-Mail ist vertraulich. Wenn Sie nicht der rechtmäßige Empfänger sind, dürfen Sie den Inhalt weder kopieren, verbreiten noch benutzen. Sollten Sie diese E-Mail versehentlich erhalten haben, senden Sie sie bitte an uns zurück und löschen sie anschließend. Cet e-mail est confidentiel. Si vous n'etes pas le destinataire de ce message, vous ne devez pas copier, divulguer ou utiliser le contenu. Si vous avez recu cet e-mail par erreur, veuillez nous informer en retournant ce message a l'expediteur et detruisez-le. Esta mensagem, e qualquer de seus anexos, eh confidencial e privilegiada. Caso voce nao seja o destinatario, nao esta autorizado a reproduzir ou divulgar a terceiros o conteudo desta mensagem e de qualquer anexo da mesma e deve apagar com os seus respectivos anexos. ___ ANDREAS STIHL AG Co. KG Kommanditgesellschaft mit Sitz in Waiblingen, HRA 260269, Amtsgericht Stuttgart Persönlich haftende Gesellschafter: Hans Peter Stihl und STIHL Aktiengesellschaft mit Sitz in Waiblingen, HRB 263722, Amtsgericht Stuttgart Vorstand der STIHL AG: Dr. Bertram Kandziora (Vorstandsvorsitzender), Dr. Peter Dürolf, Jürgen Steinhauser, Wolfgang Zahn Vorsitzender des Aufsichtsrats der STIHL AG: Hans Peter Stihl ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
[ntp:questions] NTP stratum-1 architecture
Folks, For a large organisation, I am reviewing the current NTP-infrastructure. Because high-availability is a major concern, I am considering the following architecture (improvement): * Three stratum-1 NTP-servers, geographically dispersed * Each stratum-1 NTP-server has a peering relation with each other stratum-1 NTP-server * Two stratum-1 NTP servers use GPS as stratum-0. * Two stratum-1 NTP servers use Rubidium as stratum-0. * (So consequently, one stratum-1 server uses both). The formal requirement states that when one location fails completely, it must still be possible to apply maintance on the other NTP-infrastructure without discontinuing the service. Intuitively, I would say 3 servers are required, also because of the algorithms (which I dont understand in detail) used for identifying false-tickers(??). One option is to have each stratum-1 server implemented with GPS and Rubidium timesources, but especially for GPS there are cost considerations. Another consideration is that the stratum-2 implementation is outside the scope of the department offering the NTP-service. So we do not control this implementation, but we could define guidelines for a proper implementation. But if controlling the stratum-2 layer is an essential requirement for high availability, this probably could be implemented. Any comments on this architecture proposal and consequences for the implementation are highly appreciated. For instance, what are considered best practices for NTP-architecture? Thanks a lot! Raymond This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
[ntp:questions] New Windows Installer available (4.2.4p4)
Hi there! I just released a new version of the NTP Installer for Windows, which is including the current stable ntp version 4.2.4p4 and OpenSSL 0.9.8e . As usual it fixes a number of old bugs in the installer code (... and introduces new ones) and is nicknamed modena in memory of Mr. Pavarotti. You can download it for free from our NTP download page: http://www.meinberg.de/english/sw/ntp.htm Any comments, feedback, feature requests and bug reports are welcome, please contact us at [EMAIL PROTECTED] or post to this newsgroup. The performance of this build on Vista machines is poor when compared to XP, we are investigating how this can be improved in the ntpd codebase and will keep you posted when we have more data. Best Regards, Heiko ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Using mode byte for Accord GPS Clock (venu gopal)
Hi all, I need comments from folks who have been maintining reference clk drivers reg. using extra bits of the mode field to accomodate support for Accord GPS Clock. Please see the pervious posting on the same topic. As Dave Sir has suggested we need to have some agreement reg. this so that I can proceed to sumbit the modified NMEA driver for approval. Venu On 12/5/07, venu gopal [EMAIL PROTECTED] wrote: Hi all, After going through the NMEA ref.clock driver, it seems that the original author has choosen values 0(GPXXX), 1(GPRMC), 2(GPGGA) and 4(GPGLL) for mode field so that multiple sentences can be selected. As posted earlier reg. using the mode byte/field to support Accord GPS Clock, fourth bit cannot be used to denote the baudrate. Fourth bit can denote GPZDG(8) (custom NMEA format) while the fifth bit can be used for baudrate 0(4800) and 1(9600). But in this case multiple sentences may be allowed only if the value of last four bits is less than 8, because GPZDG gives GPS time and not UTC like rest of them. So if GPZDG is selected, others sentences should not be selected. Venu ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Dual-core systems - AMD - Windows Vista
Hi Ulrich, Ulrich Windl wrote: Martin Burnicki [EMAIL PROTECTED] writes: [...] The test machine is a Intel Pentium D 3 GHz (dual core) with Windows Vista x64. Data of the time synchronization performance was collected by the time adjustment service which comes with the Meinberg driver package for Windows. That service computes the difference between the Windows system time and a built-in GPS170PCI card and normally disiplines the system time. However, in order to test the accuracy of NTP the Meinberg time service was configured just to collect data and not to apply any correnctions to the system time. [...] What you probably need in addition is a random burst of CPU load (These new cores change voltage and clock rate depending on the load). I don't know a script for that, but manipulating a larger image in some image processor usually does the job... You're right. That's an additional constraint which has to be taken into account. The bad thing is that those tests are pretty time-consuming ... Regards, Martin -- Martin Burnicki Meinberg Funkuhren Bad Pyrmont Germany ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Using mode byte for Accord GPS Clock (venu gopal)
Venu, venu gopal wrote: Hi all, I need comments from folks who have been maintining reference clk drivers reg. using extra bits of the mode field to accomodate support for Accord GPS Clock. Please see the pervious posting on the same topic. As Dave Sir has suggested we need to have some agreement reg. this so that I can proceed to sumbit the modified NMEA driver for approval. I think Frank Kardel ([EMAIL PROTECTED]) would be a good starting point. Frank is pretty familiar with the NTP driver concept, and NTP in general. Unfortunately he is still on holidays until mid December, but I think it's worth waiting for his comments ... Martin -- Martin Burnicki Meinberg Funkuhren Bad Pyrmont Germany ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Linux as clients not synching with Win/Tardis Time server
suj wrote: [] How can I make these linux servers to sync up with the tardis time servers on the windows boxes? Thanking in advance. Suj Why not run NTP on the Windows PCs? Cheers, David ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
[ntp:questions] Linux as clients not synching with Win/Tardis Time server
3 Windows NTP server = Win 2003 Std Ed, Win 2000, Win 2003 Std Ed SP2 64 bit Linux= Suse SLES 2.6.16.21-0.8 NTP version [EMAIL PROTECTED] The 3 windows NTP time servers are pointing to the external public time server pool. I looked up your archives and I see references to modifying W32time / Windows registry and ofcourse advice to make Linux the time servers. Our setup has 3 windows servers with Tardis2000 running as the time server to our windows clients. We are deploying linux servers and want to maintain status quo on the time servers till we reach a critical mass where eventually we will have linux as NTP servers. So for the time being we have to sync up Linux clients with Win Time Servers. I have setup the ntp.conf as per the standard my ntp.conf: -- server 127.127.1.0 fudge 127.127.1.0 stratum 10 server Win NTp Server-1 IP burst iburst server Win NTp Server-2 IP burst iburst server Win NTp Server-3 IP burst iburst peer linux-server2-ip peer linux-server2-ip driftfile /var/lib/ntp/drift/ntp.drift logfile /var/log/ntp -- austinpower:/home/austin # ntpdc -c peers remote localstpoll reach delay offsetdisp === *LOCAL(0)127.0.0.1 10 64 377 0.0 0.00 0.03033 =10.248.0.22 10.248.3.23114 1024 377 0.00017 -69.55465 0.06303 =gargoyle1.abc 10.248.3.23114 1024 377 0.00015 -70.18628 0.06310 =gargoyle2.abc 10.248.3.23114 1024 377 0.00017 -69.14703 0.06311 The 3 Win time servers have a stratum of 14 and the Linux time is synched to its LCL clock. Also the ntpd does not like the time servers as seen from the x against their entries austinpower:/home/austin # ntpq -p remote refid st t when poll reach delay offset jitter == *LOCAL(0) LOCAL(0) 10 l 23 64 3770.000 0.0000.001 xgargoyle1.abc 216.bb.68.yyy 14 u 232 1024 377 0.153 -70186. 1.645 xgargoyle2.abc 216.bb.68.xxx 14 u 348 1024 377 0.179 -69147. 5.233 x10.222.0.55 71.bb.xx.xx14 u 726 1024 377 0.170 -69554. 2.765 giving the time server IP in the ntpq command; # ntpq -p 10.248.0.xxx 10.248.0.xxx: timed out, nothing received ***Request timed out I have Linux bonding/network teaming, should that make a difference to the ntp syncing? I don't think so, but just explaining the setup. austinpower:/home/austin # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.248.3.0 0.0.0.0 255.255.255.0 U 0 00 bond0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 10.222.3.2540.0.0.0 UG 0 00 bond0 ntpdate command exits as if the time servers were not available. But I can ping those Win servers from my linux servers, basically not a network connectivity issue. I can also do a nslookup WinNTPserverIP from the linux m/c's and it resolves the names correctly. ntpdate cmd comes back with ; # ntpdate -u 5 Dec 10:39:05 ntpdate[10238]: no servers can be used, exiting # ntpdate -u gargoyle1.abcd.com 5 Dec 10:39:27 ntpdate[10239]: no server suitable for synchronization found #cat /var/lib/ntp/drift/ntp.drift -143.940 result on one linux server 460.786result on the other linux server # netstat -anu Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State udp0 0 255.255.255.255:427 0.0.0.0:* udp0 0 10.abc.yy.32:123 0.0.0.0:* Secondary bond IP udp0 0 10.abc.yy.31:123 0.0.0.0:*Secondary bond IP udp0 0 10.abc.yy.30:123 0.0.0.0:*Secondary bond IP udp0 0 10.abc.yy.130:1230.0.0.0:* Primary bond IP udp0 0 127.0.0.1:123 0.0.0.0:* udp0 0 0.0.0.0:123 0.0.0.0:* udp0 0 ::: 123 :::* How can I make these linux servers to sync up with the tardis time servers on the windoze boxes? Thanking in advance. Suj ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] syncing two machines, microsecond precision?
On 2007-12-04, Dan B. Phung [EMAIL PROTECTED] wrote: Hi, I'm trying to sync two machines, one as the server the other as the client, both sitting on a private switched network. After ntp settles in, the client has a 10-30 ms offset that continues to increase in offset, but what I'm doing requires the two machines to be off by no more than 500 us. I've gone through the NTP debug routine and my PPM error is pretty small (see below) also, what's the huffpuff filter, I didn't try playing with that yet, and can't find much info on the web about it. Below is some info to help assess my situation, please let me know if there's more info I can provide. server (larry) conf: ntp.conf driftfile /var/lib/ntp/ntp.drift statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable server 127.127.1.1 fudge 127.127.1.1 stratum 10 restrict 127.0.0.1 restrict ::1 /ntp.conf You have not provided your server with a stable timebase. So you don't really know if the server clock is drifting slowly in one direction or the other or swinging back and forth. This may, or may not, contribute to the problem you're experiencing. BTW: Your restrict lines are meaningless (and harmless) since you have not defined a default restriction. client (moe) conf: server larry As an enhancement you could append 'iburst' to that server line to speed up initial sync. debugging info on larry: [snip] remote refid st t when poll reach delay offset jitter *LOCAL(1) .LOCL. 10 l 29 64 3770.0000.000 0.001 That looks normal. debugging info on moe: [snip] remote refidst t when poll reach delay offset jitter *larry LOCAL(1) 11 u6 64 377 0.175 -15.448 5.771 Keep in mind that this is only a snap shot and conveys more information when compared with other peer status billboards over time. [snip] clockË004b8a.3864b86c Tue, Dec 4 2007 16:56:26.220, state=2, ntpd is not fully synchronised until the state equals 4. ntpd spends about 20 minutes training the clock at start up if no drift file is present. During this time you may observe the clock being slewed back and forth. You need to allow ntpd to run long enough (~ 1 hour) for a drift file to be created. Has a drift file been created on moe? The states are (taken from ./ntpd/ntp_loopfilter.c): #define S_NSET 0 /* clock never set */ #define S_FSET 1 /* frequency set from the drift file */ #define S_SPIK 2 /* spike detected */ #define S_FREQ 3 /* frequency mode */ #define S_SYNC 4 /* clock synchronized */ -- Steve Kostecke [EMAIL PROTECTED] NTP Public Services Project - http://support.ntp.org/ ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
[ntp:questions] NTP fails synchronization with server at startup
Dear All, I have NTP configured to synchronize with a server at startup, but it always fails that as reported by Fedora 8 during the booting. Notwithstanding: # /sbin/service ntpd restart Shutting down ntpd:[ OK ] ntpd: Synchronizing with time server: [ OK ] Starting ntpd: [ OK ] # Any ideas? Thanks in advance, Paul ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Any samples for NTP/SNTP client code?
(sender?), As for symmetry in request/response being uncommon, you may consder ICMP Echo/Echo Reply and even TCP as uncommon, and that is curious. The RFC describes formulas for computing the offset and delay. You consider this ***alone*** is the slowest way. You imply there are other ways to compute these values and all of them are faster. Please reveal some examples. You also hint that you want to collect samples as fast as possible. If you confine this to your own servers, be happy. If you do that with public servers, you may get a very rude Kiss-o'-Death packet and a complaint to the Internet Police. In addition, at least with my servers, you will be permanantly blacklisted. Dave [EMAIL PROTECTED] wrote: On Dec 1, 3:07 pm, Joseph Gwinn [EMAIL PROTECTED] wrote: In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: Does anybody know of any *practical* samples on how to implement NTP/SNTP client?. The goal is to provide accurate time for a program/client running on Windows Vista. Specifically, what values to include in the the request message, how to process the reply message, etc. I am NOT asking how to send/receive UDP datagrams, or where to find comprehensive descriptions like RFC documents, or how to build or design user interfaces. Only a narrow description focused on NTP/SNTP request/reply datagrams for a simple PC client, preferably in C/C++ source code. I've done this in an embedded realtime system. (No, the source code is not available.) In Appendix A of RFC-1305 you will find the format of the NTPv3 request/response packet. Send this packet to port 123 of the NTP server, and read the reply packet. It's pretty easy. I saw this format. From data comm point of view it is very unusual to have the same format for request and reply. Sending/receiving the packet to port 123 is the first thing I tried. This is not an issue. The issue is to use all the values in request and reply correctly and reliably. And the quickest way is to get as many ***samples*** as possible, the RFC doc ***alone*** is the slowest way. ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Linux as clients not synching with Win/Tardis Time server
suj wrote: We are planning on eventually getting Linux to be the NTP servers, but since the existing clients are all pointing to the Win server with Tardis on it, we want to maintain it that way till we migrate to linux completely. The concern is to get the linux servers to right now be able to point to the existing Win servers with Tardis. Suj Your choice, of course. You might save yourself time installing NTP via a good install. Cheers, David ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Linux as clients not synching with Win/Tardis Time server
We are planning on eventually getting Linux to be the NTP servers, but since the existing clients are all pointing to the Win server with Tardis on it, we want to maintain it that way till we migrate to linux completely. The concern is to get the linux servers to right now be able to point to the existing Win servers with Tardis. Suj On Dec 5, 12:30 pm, David J Taylor [EMAIL PROTECTED] bit.nor-this-bit.co.uk wrote: Why not run NTP on the Windows PCs? Cheers, David ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] NTP stratum-1 architecture
Groenewoud, Raymond wrote: * Three stratum-1 NTP-servers, geographically dispersed * Each stratum-1 NTP-server has a peering relation with each other stratum-1 NTP-server * Two stratum-1 NTP servers use GPS as stratum-0. * Two stratum-1 NTP servers use Rubidium as stratum-0. * (So consequently, one stratum-1 server uses both). If I read this correctly, you are exclusively relying on GPS as a time source (Rubidium is a frequency source). I would suggest that you use different *independent* time sources, and as many as practical. Radio signals from DCF77 and MSF both have very good signal quality in The Netherlands. N ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Dual-core systems - AMD - Windows Vista
David, Don't look in the NTP distribution for interpolation code; that's in the kernel, for the Alpha the nanokernel code. All the code there, by the way, is in C for portability. By the way, I see that code is no longer available via http, only anonymous ftp. Dave David J Taylor wrote: David L. Mills wrote: David, The multiple-CPU nanokernel code that left here and is in the Alpha kernel assumes each CPU has an individual cycle counter and the timer interupts are vectored to a designated CPU. There is a data structure associated with each CPU that holds the measured current cycle counter scaling and offset, which is updated once each second by interprocessor interrrupt. A call to read the system clock lands on a j-random CPU, which reads the global time maintained by timer interrupts and interpolates according to the current CPU values. I don't know if Vista attempts to provide granularity within the tick; but if it does, I would expect it to use a similar strategy. Dave Thanks for that, Dave. I haven't needed to touch assembler for a little wile now, so I'm not up to speed on whether the various Intel and AMD architectures (hyper-threading, dual/quad-core, and physical multi-processor etc.) provide access to every cycle counter from a single CPU or executing thread. The Windows implementation does try to provide granularity within the tick, but I have no idea how the Meinberg port I'm using handles multi-processors. Checking. I see the routine: nt_clockstuff.c mentions that how to handle multi-processors is not yet decided, but that seems very old code (year 2000). I can't find the RDTSC instruction anywhere in version ntp-4.2.4p4. So I'm a bit stuck right now! Cheers, David ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] NTP fails synchronization with server at startup
[EMAIL PROTECTED] wrote: Dear All, I have NTP configured to synchronize with a server at startup, but it always fails that as reported by Fedora 8 during the booting. Notwithstanding: # /sbin/service ntpd restart Shutting down ntpd:[ OK ] ntpd: Synchronizing with time server: [ OK ] Starting ntpd: [ OK ] # Any ideas? Thanks in advance, Paul Your message is VERY short on useful information. What version of ntpd are you using? I don't see any details of the alleged failure. What command line are you using to start ntpd? What does your ntp.conf file look like? Are there any relevant messages in syslog? ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Dual-core systems - AMD - Windows Vista
Martin Burnicki wrote: [] There's now a new graph recorded under 32 bit Vista: http://www.meinberg.de/download/ntp/graphs/ntp-dev-4.2.5p104-windows-vista-32.pdf The first section is with maxpoll 6, and in the second part maxpoll has been reduced to 4, which does not seem to eliminate the reason for the jitter, but the magnitude. I do appreciate your efforts with this. Thanks. We all want NTP to discipline even the Windows system time as good as possible. Martin Thanks, Martin. The graph looks a little more like mine now - almost like two frequencies beating together with periods of large swing followed by periods of stability. It surprises me that in the maxpoll = 6 part, the tick value doesn't swing more. I would have thought that once an offset near zero was reached, the tick value would start to swing between the two best values. Can you try with the interpolation removed, in case it shows anything? Cheers, David ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] NTP stratum-1 architecture
Groenewoud, Raymond wrote: Folks, For a large organisation, I am reviewing the current NTP-infrastructure. Because high-availability is a major concern, I am considering the following architecture (improvement): * Three stratum-1 NTP-servers, geographically dispersed * Each stratum-1 NTP-server has a peering relation with each other stratum-1 NTP-server * Two stratum-1 NTP servers use GPS as stratum-0. * Two stratum-1 NTP servers use Rubidium as stratum-0. * (So consequently, one stratum-1 server uses both). The formal requirement states that when one location fails completely, it must still be possible to apply maintance on the other NTP-infrastructure without discontinuing the service. Intuitively, I would say 3 servers are required, also because of the algorithms (which I dont understand in detail) used for identifying false-tickers(??). One option is to have each stratum-1 server implemented with GPS and Rubidium timesources, but especially for GPS there are cost considerations. Another consideration is that the stratum-2 implementation is outside the scope of the department offering the NTP-service. So we do not control this implementation, but we could define guidelines for a proper implementation. But if controlling the stratum-2 layer is an essential requirement for high availability, this probably could be implemented. Any comments on this architecture proposal and consequences for the implementation are highly appreciated. For instance, what are considered best practices for NTP-architecture? Thanks a lot! First, it is customary to use the carriage return key after approximately seventy characters have been typed. It makes your message MUCH easier to read and reply to. I had to reformat your text in order to reply! I think four servers are the minimum. With only three servers, if one fails, you have no way to determine which of the survivors is more nearly correct. Five servers allows the failure of any two and seven servers allow the loss or failure of three without ill effect. Second; Rubidium, in and of itself, is not a source of time. A Rubidium oscillator can provide an extremely precise and stable frequency reference and you can determine delta time simply by counting the ticks. Knowing what time it is requires something more than a simple Rubidium oscillator! Having the finest Rolex watch does not guarantee that you have the correct time; it's only as good as the time you use to set it! Third, if your servers are geographically remote, you introduce uncertainty in the time returned by those servers. The uncertainty is equal to one half the round trip delay. The actual error is usually far less than that but you cannot know it! A GPS disciplined quartz crystal oscillator such as the HP3816A, the Symmetricom BC637 or the similar product from Meinberg Funkuhren makes a very good reference clock. These all provide good holdover characteristics in case of temporary loss of GPS signals. ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] NTP fails synchronization with server at startup
On Dec 6, 12:37 am, Harlan Stenn [EMAIL PROTECTED] wrote: How about the output of 'ntpq -p' ? H --http://ntpforum.isc.org - be a member! # /usr/sbin/ntpq -p remote refid st t when poll reach delay offset jitter == *syrte8.obspm.fr 145.238.203.14 2 u7 64 377 61.055 55.208 6.901 +ns2.kamino.fr 193.52.184.106 2 u 30 64 377 49.493 48.255 8.133 +ntp2.belbone.be 195.13.23.6 2 u4 64 377 69.442 43.465 6.665 # Paul ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
[ntp:questions] Computer Security Information and What You Can Do To Keep Your System Safe!
.:: Unix and Linux Hacking and Security ::. 1. Unix - Vulnerabilities and Advisories -- Tutorials and Papers -- Specific Exploits and Vulnerabilities 2. Unix - Security Tools -- Unix Security and Audit Tools (Including IDS and Access Control Tools) -- Unix Log Analysis Tools -- Unix Proxies, Firewalls and Accessories -- Unix Miscellany 3. Unix - BSD, FreeBSD, etc... -- FreeBSD -- BSD and Misc. BSD variants -- BSD Security Tools -- BSD Micro-distributions 4. Unix - Solaris, SunOS etc... -- Solaris -- SunOS -- Cobalt Appliances -- SunOS and Solaris Security Tools 5. Unix - Other Flavors (Irix, HPUX, AIX, etc...) -- SGI/Irix -- HP-UX -- AIX -- SCO -- Miscellaneous 6. Linux - Vulnerabilities and Advisories -- Linux - General Hacking -- Linux Application Exploits -- Linux - Red Hat Specific -- Linux - Debian Specific 7. Linux - Security Tools -- Linux - Intrusion Detection -- Linux - Access Control -- Linux Log Analysis Tools -- Linux Rootkits -- Linux Proxies and Firewalls -- Linux - General Security and Audit Tools 8. Linux - Security-oriented mini- and micro-distributions -- DMZS-Biatchux -- NSA Security Enhanced Linux -- Linux Mini- and Micro-distributions -- Applications .:: Windows Hacking and Security ::. 1. Windows Vulnerabilities, Advisories, and even security flaws introduced by so-called security products!!! -- Microsoft IIS Vulnerabilities -- Microsoft FrontPage Vulnerabilities -- Microsoft Internet Explorer Vulnerabilities -- Windows Application Vulnerabilities -- Windows Internet/Networking Vulnerabilities -- Insecurities introduced by security programs! -- Netscape Browsers -- Windows Hacks - Miscellaneous 2. Windows Security and Auditing Tools -- Windows Registry Tools -- Windows and MSDOS Security and Auditing Tools -- Windows Local Security -- File/Disk/Log Shredders 3. Windows Miscellany -- Raw Sockets and Custom Packet Building -- A Few Little Extras for Microsoft Fans .:: Crypto, Virology, Cracking and Backdoors ::. 1. Cryptography, Cryptanalysis, Steganography -- Crypto: PGP and GPG -- Crypto: Cryptanalysis -- Crypto: Steganography -- Crypto: Miscellaneous -- Misc. File Encryptors 2. About Viruses and Worms -- Virus Info Files and Advisories -- Worms -- Virus/Worm Protection Utilities 3. Backdoors, Trojans and defenses -- Back Orifice and BO2K -- SubSeven and Addons -- Other Remote Administration Tools -- Trojan Detectors/Removers/Retaliators -- Information Files .:: Learn what Hackers know, how they do it, and what you can do to keep your system safe ::. 1. General Hacking Information -- General Security Concepts -- Antique Systems -- Oracle -- Tools, Advisories and Exploits affecting multiple platforms -- PC Software and BIOS Hacking -- Truly Miscellaneous Hacking Info 2. Password Security -- Password Hacking -- Password Generators -- Password Security Audit Programs -- Word Lists 3. Scanning, Fingerprinting and similar techniques -- Network Scanning -- Wargames Modem Carrier Scanning -- Fingerprinting -- Sniffing 4. How Hackers Attack Numerous Internet Services -- Denial of Service Attacks -- Email and News -- Proxies and IP Spoofing -- DNS and BIND -- SPAM -- FTP -- General Unsorted Information -- Indispensible Internet Utilities -- Cable and DSL Info and Hacking 5. How Hackers Attack Web Servers, CGIs, PHP, ASP, etc... -- Web Site Hacking - General and Miscellaneous -- Web Site Hacking - Specific Sites -- Web Site Hacking - Servers -- Web Site Hacking - CGI, Perl, ASP, PHP etc. -- Web BBSes -- Web Site Hacking - Audit Tools 6. How Hackers attack IRC, Instant Messaging, and Multiplayer Games -- ICQ Hacking -- IRC Hacking, Scripts and Bots -- AOL Instant Messenger (AIM) -- Miscellaneous Chat/gaming Systems 7. Vulnerabilities found in Platforms with Smaller Market Share -- Macintosh -- PalmOS -- Printers -- Dedicated Network Appliances, Hubs, Routers, etc... -- Cisco Equipment -- Miscellaneous 8. How Hackers Attack Novell and 802.11b Networks -- Novell Networks -- Wireless LANs -- X.25 Networks -- Miscellaneous Networking Information .:: Computer Security Information ::. -- Access Control -- Basics -- Chat Systems -- Cryptography -- Denial Of Service -- Hacking Security Groups -- Hardening Securing Papers -- ICQ -- Intrusion Detection Systems -- IRC -- Miscellaneous -- Network Auditing Secuirty Penetration -- Online Privacy -- Operating Systems -- Protocols .:: Phreaking - The black art of telephony ::. 1. GENERAL - General Information About the Phone Company -- Hacking Answering Machines and Voice Mail -- Phreaking Programs 2. Electronic Toll Fraud and Other Phone Devices -- The Fixer's Box Review - Read this before you read the rest of these files! -- Blue and Green Boxes -- Red Box -- Beige and Bridge Boxes -- Various new boxes -- Programs to generate phreak tones 3. All about Payphones, COCOTs, BOCOTs, etc... -- Payphones -- COCOTs -- Nortel/Quortech Millennium -- Smart Cards/Phone Cards 4. Cellular Telephones and the Hacking Thereof -- Cellular Phones by
Re: [ntp:questions] NTP fails synchronization with server at startup
[EMAIL PROTECTED] wrote: On Dec 5, 10:35 pm, Richard B. Gilbert [EMAIL PROTECTED] wrote: I have NTP configured to synchronize with a server at startup, but it always fails that as reported by Fedora 8 during the booting. Notwithstanding: # /sbin/service ntpd restart Shutting down ntpd:[ OK ] ntpd: Synchronizing with time server: [ OK ] Starting ntpd: [ OK ] # Any ideas? Thanks in advance, Paul Your message is VERY short on useful information. What version of ntpd are you using? I don't see any details of the alleged failure. What command line are you using to start ntpd? What does your ntp.conf file look like? Are there any relevant messages in syslog? Thanks, Richard. Let me add the requested details: Using: # rpm -qi ntp Name: ntp Relocations: (not relocatable) Version : 4.2.4p2 Vendor: Fedora Project Release : 6.fc8 Build Date: Mon 24 Sep 2007 03:40:21 PM WEST Install Date: Fri 02 Nov 2007 02:22:53 PM WET Build Host: xenbuilder4.fedora.phx.redhat.com Group : System Environment/DaemonsSource RPM: ntp-4.2.4p2-6.fc8.src.rpm Size: 2652615 License: (MIT and BSD and BSD with advertising) and GPLv2 Signature : DSA/SHA1, Thu 25 Oct 2007 05:41:19 AM WEST, Key ID b44269d04f2a6fd2 Packager: Fedora Project URL : http://www.ntp.org Summary : Synchronizes system time using the Network Time Protocol (NTP) Description : The Network Time Protocol (NTP) is used to synchronize a computer's time with another reference time source. The ntp package contains utilities and daemons that will synchronize your computer's time to Coordinated Universal Time (UTC) via the NTP protocol and NTP servers. The ntp package includes ntpdate (a program for retrieving the date and time from remote machines via a network) and ntpd (a daemon which continuously adjusts system time). Install the ntp package if you need tools for keeping your system's time synchronized via the NTP protocol. # - SYSLOG /var/log/messages:Dec 6 00:11:47 localhost ntpd[1863]: ntpd exiting on signal 15 /var/log/messages:Dec 6 00:13:22 localhost ntpdate[2187]: can't find host ntp.obspm.fr /var/log/messages:Dec 6 00:13:22 localhost ntpdate[2187]: can't find host ntp.kamino.fr /var/log/messages:Dec 6 00:13:22 localhost ntpdate[2187]: can't find host ntp2.belbone.be /var/log/messages:Dec 6 00:13:22 localhost ntpdate[2187]: no servers can be used, exiting The above appears to say that your system is having trouble resolving the IP addresses of your servers. Have you tried replacing ntp.obspm.fr with 145.238.203.10 etc? snip ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Any samples for NTP/SNTP client code?
[EMAIL PROTECTED] wrote: On Dec 3, 3:34 am, [EMAIL PROTECTED] (David Woolley) wrote: In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: QueryPerformanceCounter() directly off the hardware. Windows scheduling has no impact here, the drawbacks of tick counts do not Windows scheduling will cause uncertainty in the time you get from your SNTP requests which you use to calibrate the performance counters. (It will also cause uncertainties in the time of whatever real world event is associated with the times being recorded by your software.) Windows scheduling will NOT cause any bigger uncertainty than many other factors including network delays or scheduling on my Linksys router (probably Unix-like OS) that relays all my incoming/outgoing IP traffic. Then you have no idea. There is plenty of evidence to disprove this. I have plenty of suspicious pieces that may be the cause of the issues including interrupts and message pumping. The most important thing is that my code will be able to measure fairly consistently the time between sending a request and receiving a reply for ***all*** servers in microseconds. I will use at least five servers. It would not be possible with TICKS but it is possible with high frequency counters because they operate on different principle as stated. This is the key difference!!! Consequently, it will be possible to estimate the drift of the PC counter and come up with servers' polling frequencies that satisfy my reqs for accuracy. So do not make it more complicated than it is. The rest belongs to the algorithims I will use and you do not know them, and I am not ready to discusss them. That's okay, we don't need to know. If you can prove you get better results then I'm sure you will let us know. We would welcome something better but you need to show it really is better for most (if not all) cases that ntp deals with. Danny ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
