[opensuse] local NTP server?
Is there something on http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n... that explains how I can configure a system to be an NTP server for other systems on a LAN? If it's there, I'm not recognizing it, and it's not obvious to me looking at time config in YaST2 or elsewhere in YaST2, or in /etc/ntp.conf. Also, what exactly does running as daemon in context of NTP mean or imply? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Is there something on
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n...
that explains how I can configure a system to be an NTP server for other systems on a LAN?
It always is. Just point your other systems to it. -- Per Jessen, Zürich (-3.1°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 07:58 (GMT+0100) Per Jessen composed:
Felix Miata wrote:
Is there something on
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n...
that explains how I can configure a system to be an NTP server for other systems on a LAN?
It always is. Just point your other systems to it.
How do I find out why it doesn't work? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
On 2013-03-15 07:58 (GMT+0100) Per Jessen composed:
Felix Miata wrote:
Is there something on
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n...
that explains how I can configure a system to be an NTP server for other systems on a LAN?
It always is. Just point your other systems to it.
How do I find out why it doesn't work?
You look at the traffic going back and forth - the client should query the server, you should see a response. Run "tcpdump -n -i <iface> port 123" on the server to see the ntp traffic. -- Per Jessen, Zürich (-3.0°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/15/2013 03:58 AM, Per Jessen wrote:
Felix Miata wrote:
Is there something on
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n...
that explains how I can configure a system to be an NTP server for other systems on a LAN?
It always is. Just point your other systems to it.
Yep, however what he really needs is just to use a server from the public ntp pool. ;) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
On 03/15/2013 03:58 AM, Per Jessen wrote:
Felix Miata wrote:
Is there something on
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n...
that explains how I can configure a system to be an NTP server for other systems on a LAN?
It always is. Just point your other systems to it.
Yep, however what he really needs is just to use a server from the public ntp pool. ;)
Yeah, although it's not such a bad idea to have one system sync'ed to the pool, and the rest sync'ed to that system. -- Per Jessen, Zürich (-3.1°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 08:29 (GMT+0100) Per Jessen composed:
Cristian RodrÃguez wrote:
On 03/15/2013 03:58 AM, Per Jessen wrote:
Felix Miata wrote:
Is there something on
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n...
that explains how I can configure a system to be an NTP server for other systems on a LAN?
It always is. Just point your other systems to it.
Yep, however what he really needs is just to use a server from the public ntp pool. ;)
Yeah, although it's not such a bad idea to have one system sync'ed to the pool, and the rest sync'ed to that system.
Exactly what I'm trying to do because I have a STB running Linux that when configured to use a public pool always fails to sync. When setting it up to a specific public server like time.nist.gov or time.mit.edu it randomly works or not. It seems to work no more than about once or twice a day, but typically needs rebooting multiple times a day to avoid catching video output corruption while attempting to record from it. When it fails on reboot it gets a 1999 date and 00:00 UTC time setting. I was hoping a local server would somehow be more reliable. When I set the STB to sync to the local hostname or IP of my local NTP, it always fails, and the output of 'tcpdump -n -i etho port 123' never sees anything incoming from the STB, while it is showing 140.99.51.114.123, which I would think my router should be blocking. Or could that be an IP via us.pool.ntp.org? I have no idea how the STB actually gets the date from the internet. It has no ntp command, no ntpd command, no tcpdump command, and no /etc/ntp.conf. A ntp server URL is fed into the GUI UI if auto sync from internet is selected. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
On 2013-03-15 08:29 (GMT+0100) Per Jessen composed:
Yeah, although it's not such a bad idea to have one system sync'ed to the pool, and the rest sync'ed to that system.
Exactly what I'm trying to do
because
I have a STB running Linux
What is an STB?
that when configured to use a public pool always fails to sync. When setting it up to a specific public server like time.nist.gov or time.mit.edu it randomly works or not. It seems to work no more than about once or twice a day,
That sounds like a dodgy network. Fails to sync is either a) fails to connect to time-server or b) the STB is too far out-of-sync.
but typically needs rebooting multiple times a day to avoid catching video output corruption while attempting to record from it. When it fails on reboot it gets a 1999 date and 00:00 UTC time setting. I was hoping a local server would somehow be more reliable.
Do you know how it sets the date on startup? With that kind of difference, it would need to start ntp with '-g' to override the safety check. Maybe it uses sntp?
When I set the STB to sync to the local hostname or IP of my local NTP, it always fails, and the output of 'tcpdump -n -i etho port 123' never sees anything incoming from the STB,
Firewall issue?
while it is showing 140.99.51.114.123, which I would think my router should be blocking. Or could that be an IP via us.pool.ntp.org?
It could be, yes. 140.99.51.114 = tuppy.intrepidhosting.net.
I have no idea how the STB actually gets the date from the internet. It has no ntp command, no ntpd command, no tcpdump command, and no /etc/ntp.conf.
sntp?
A ntp server URL is fed into the GUI UI if auto sync from internet is selected.
What does that look like? ntp://server/etc ??? -- Per Jessen, Zürich (0.4°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-03-15 12:33, Per Jessen wrote:
Felix Miata wrote:
that when configured to use a public pool always fails to sync. When setting it up to a specific public server like time.nist.gov or time.mit.edu it randomly works or not. It seems to work no more than about once or twice a day,
That sounds like a dodgy network. Fails to sync is either a) fails to connect to time-server or b) the STB is too far out-of-sync.
I would look at the firewall on the server, first thing. Also, there is another method of time sync, used by Windows. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFDG5gACgkQIvFNjefEBxocwACgmVsJtGtEudRO/ZNCHAFZehS6 vwcAniLetENMvJDM3vtYhCJh990P+7YR =7VAA -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
Also, there is another method of time sync, used by Windows.
Windows also uses NTP, but it's not as accurate as in Linux, if you use the default client. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-03-15 14:56, James Knott wrote:
Carlos E. R. wrote:
Also, there is another method of time sync, used by Windows.
Windows also uses NTP, but it's not as accurate as in Linux, if you use the default client.
No, they also have their own method. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFDM1oACgkQIvFNjefEBxoq6QCeIABc+GBJ3LmiThd6dNtUrl+M cksAnjguMGGudJWvHtYNAzYzl2+xjOg9 =kifT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
Windows also uses NTP, but it's not as accurate as in Linux, if you
use the default client. No, they also have their own method.
What would that method be? When you configure "Internet time settings" in Windows 7, you have to enter a NTP server. I have never seen anything else on Windows. However, if a Windows computer is connected to a domain server, it will obtain time from the domain server. Regardless, the included NTP client in Windows is not as accurate as in Linux. There have been other methods in the past for time sync, but they're no longer commonly used and I don't ever recall them being included with Windows. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-03-15 15:59, James Knott wrote:
Carlos E. R. wrote:
Windows also uses NTP, but it's not as accurate as in Linux, if you
use the default client. No, they also have their own method.
What would that method be? When you configure "Internet time settings" in Windows 7, you have to enter a NTP server. I have never seen anything else on Windows. However, if a Windows computer is connected to a domain server, it will obtain time from the domain server.
Yes, that's one method, an AD server.
Regardless, the included NTP client in Windows is not as accurate as in Linux.
I think that on a standalone machine it simply sets the time once, it does not trim the clock speed. I have no proof of this, so just a feeling. On an AD domain it has to keep sync somehow.
There have been other methods in the past for time sync, but they're no longer commonly used and I don't ever recall them being included with Windows.
Those other methods you mention is one possibility; actually, that's what I was thinking of. Time ago I tried to sync a Windows machine against my local NTP server and it failed for that reason precisely. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFDPS8ACgkQIvFNjefEBxod6ACfbNJcme9zkJtkDH3ZngY9GQFv +usAmwSmk1shWgSh9/aTcU2AqjQxfx/k =obSu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
В Fri, 15 Mar 2013 15:42:34 +0100
"Carlos E. R."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-03-15 14:56, James Knott wrote:
Carlos E. R. wrote:
Also, there is another method of time sync, used by Windows.
Windows also uses NTP, but it's not as accurate as in Linux, if you use the default client.
No, they also have their own method.
Thank you for letting me know. So my several dozens systems including Linux ones syncing off Windows servers exist just in my imagination :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlFDSFIACgkQR6LMutpd94zYGwCfco2RD2FCeJkAdtAE1+dAvsMk OOEAnjvu/0tOOGWP8L0gIpCiDzheD9HJ =q2L5 -----END PGP SIGNATURE-----
Andrey Borzenkov wrote:
No, they also have their own method.
Thank you for letting me know. So my several dozens systems including Linux ones syncing off Windows servers exist just in my imagination:)
If you're using a domain login, then that's how you're getting clock sync. Of course, the domain controller should be using NTP, but if you want accurate time, you may be better of using Linux for the domain controller. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Mar 15, 2013 at 12:24:35PM -0400, James Knott wrote:
Andrey Borzenkov wrote:
No, they also have their own method.
Thank you for letting me know. So my several dozens systems including Linux ones syncing off Windows servers exist just in my imagination:)
If you're using a domain login, then that's how you're getting clock sync. Of course, the domain controller should be using NTP, but if you want accurate time, you may be better of using Linux for the domain controller.
Or you have to use third-party applications. See http://support.microsoft.com/kb/939322/en-us Even if you use Linux or a different server operating system you still need some client software piece for your Microsoft clients in such an environment. In particular if your time needs to be more accurate than 'the range of 1 to 2 seconds'. That's from the knowledge base article quoted above. With a quick search I've not been able to find an Open Source Software which operates as a NTP client. Microsoft made in the Microsoft Windows 2k days only use of sntp. But even by this they had been able to fulfill the the main goal to provide a reliale and precise (enough) time source to operate a Kerberized environment. The short argumentation is: Kerberos, a key component of Microsoft's Active Directory (AD), relies on the correct time. See http://support.microsoft.com/kb/224799/en-us That's an older article and very basic. Nowadays mainly of historical use. http://technet.microsoft.com/en-us/library/cc773013%28v=ws.10%29.aspx is a bit more detailed and more up to date too. Thanks James to make me drive this little refreshed Microsoft time tour. :) Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 2013-03-15 14:01 (GMT+0100) Carlos E. R. composed:
Also, there is another method of time sync, used by Windows.
For purposes of the thread topic as relates to OP, there is no such thing as Windows. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-03-15 16:15, Felix Miata wrote:
On 2013-03-15 14:01 (GMT+0100) Carlos E. R. composed:
Also, there is another method of time sync, used by Windows.
For purposes of the thread topic as relates to OP, there is no such thing as Windows.
There may be, because the unknown machine used by the OP may be using that protocol >:-) - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFDPlgACgkQIvFNjefEBxpR+QCeJ79AeQvZLcnyBsOPgXm9BEMI vFMAoIrm8F+ZPjl1214uLVKLM6ymoyQb =b4IA -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 16:29 (GMT+0100) Carlos E. R. composed:
On 2013-03-15 16:15, Felix Miata wrote:
On 2013-03-15 14:01 (GMT+0100) Carlos E. R. composed:
Also, there is another method of time sync, used by Windows.
For purposes of the thread topic as relates to OP, there is no such thing as Windows.
There may be, because the unknown machine used by the OP may be using that protocol >:-)
As I am the OP, that would be a herculean surprise. Datapoints: $ uname -a Linux AZBox 2.6.15-sigma #138 PREEMPT Thu Jan 22 21:35:07 KST 2009 mips unknown $ ls -l /etc/*lease* ls: /etc/*lease*: No such file or directory $ cat /proc/sys/kernel/osrelease 2.6.15-sigma $ cat /proc/cpuinfo system type : Sigma Designs TangoX processor : 0 cpu model : MIPS 4KEc V6.9 Initial BogoMIPS : 296.96 wait instruction : yes microsecond timers : yes tlb_entries : 32 extra interrupt vector : yes hardware watchpoint : yes ASEs implemented : mips16 VCED exceptions : not available VCEI exceptions : not available System bus frequency : 200250000 Hz CPU frequency : 300375000 Hz DSP frequency : 300375000 Hz $ mount /proc on /proc type proc (rw,nodiratime) /dev/mtdblock5 on /DISK1 type jffs2 (ro,noatime) devpts on /dev/pts type devpts (rw) tmpfs on /tmp type tmpfs (rw) sysfs on /sys type sysfs (rw) /dev/hda1 on /MMP type ext3 (ro,data=ordered) /dev/hda2 on /PLUGINS type ext3 (ro,data=ordered) /dev/hda3 on /DISK2 type ext3 (rw,data=ordered) /dev/hda4 on /Download type ext3 (rw,data=ordered) /dev/hdb1 on /DATA/hdb1 type ext2 (rw,nogrpid) $ whoami root $ sntp -sh: sntp: command not found $ ntp -sh: ntp: command not found $ ntpd -sh: ntpd: command not found $ tcpdump -sh: tcpdump: command not found Searching with MC for *ntp* confirms their absence. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Searching with MC for *ntp* confirms their absence.
Run NTP on a Linux box. It will now operate as a server. Configure that STB to use that Linux box as a server. Fire up Wireshark on the server to see what's coming from/going to that STB. Without data, we're only guessing. You can configure Wireshark to watch for IP, MAC address, protocol etc. Try filtering on port 123 first. If that fails, try the IP address for the STB. If that fails, try it's MAC address. Let us know what you see. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 12:22 (GMT-0400) James Knott composed:
Felix Miata wrote:
Searching with MC for *ntp* confirms their absence.
Run NTP on a Linux box. It will now operate as a server. Configure that STB to use that Linux box as a server. Fire up Wireshark on the server to see what's coming from/going to that STB. Without data, we're only guessing. You can configure Wireshark to watch for IP, MAC address, protocol etc. Try filtering on port 123 first. If that fails, try the IP address for the STB. If that fails, try it's MAC address. Let us know what you see.
Filtering on port 123, only the pool server address, server address, and IP of another PC booted and configured only for server instead of us.pool.ntp.org in /etc/ntp.conf show up. Filtering on the STB IP, I see its IP (and server IP, since from it I telnet to the STB to run its shell) when I use it to ping Google. I also see Wireshark traffic to/from the STB using MC's FTPFS to manage its files. With time.nist.gov I tried in its GUI to make the STB sync after boot failed to sync automatically, and it failed twice, each time producing no additional Wireshark output. In its GUI I changed it to time.mit.edu and tried again. It succeeded in syncing but without producing any additional Wireshark output. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Fri, 15 Mar 2013 13:41:45 -0400
Felix Miata
On 2013-03-15 12:22 (GMT-0400) James Knott composed:
Felix Miata wrote:
Searching with MC for *ntp* confirms their absence.
Run NTP on a Linux box. It will now operate as a server. Configure that STB to use that Linux box as a server. Fire up Wireshark on the server to see what's coming from/going to that STB. Without data, we're only guessing. You can configure Wireshark to watch for IP, MAC address, protocol etc. Try filtering on port 123 first. If that fails, try the IP address for the STB. If that fails, try it's MAC address. Let us know what you see.
Filtering on port 123, only the pool server address, server address, and IP of another PC booted and configured only for server instead of us.pool.ntp.org in /etc/ntp.conf show up.
Filtering on the STB IP, I see its IP (and server IP, since from it I telnet to the STB to run its shell) when I use it to ping Google. I also see Wireshark traffic to/from the STB using MC's FTPFS to manage its files. With time.nist.gov I tried in its GUI to make the STB sync after boot failed to sync automatically, and it failed twice, each time producing no additional Wireshark output. In its GUI I changed it to time.mit.edu and tried again. It succeeded in syncing but without producing any additional Wireshark output.
Is your server (default) gateway for STB? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 21:53 (GMT+0400) Andrey Borzenkov composed:
Fri, 15 Mar 2013 13:41:45 -0400 Felix Miata composed:
Filtering on port 123, only the pool server address, server address, and IP of another PC booted and configured only for server instead of us.pool.ntp.org in /etc/ntp.conf show up.
Filtering on the STB IP, I see its IP (and server IP, since from it I telnet to the STB to run its shell) when I use it to ping Google. I also see Wireshark traffic to/from the STB using MC's FTPFS to manage its files. With time.nist.gov I tried in its GUI to make the STB sync after boot failed to sync automatically, and it failed twice, each time producing no additional Wireshark output. In its GUI I changed it to time.mit.edu and tried again. It succeeded in syncing but without producing any additional Wireshark output.
Is your server (default) gateway for STB?
No. Only gateway here I know of is the router. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Is your server (default) gateway for STB?
No. Only gateway here I know of is the router.
How are you watching the traffic when connecting to the MIT NTP server? If you're using a switch, you won't see anything between the STB and the NTP server. To watch that traffic you'll need to use a hub or a managed switch with a mirror port, unless you have an Ethernet tap handy. I keep an old 10 Mb hub handy, just for such monitoring. It's supposedly possible to make a passive tap, but I've never tried it. On my home network, my router/firewall is an old computer running Linux. It has Wireshark installed, so I can ssh to it and run Wireshark to monitor the traffic passing through it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 14:14 (GMT-0400) James Knott composed:
Felix Miata wrote:
Is your server (default) gateway for STB?
No. Only gateway here I know of is the router.
How are you watching the traffic when connecting to the MIT NTP server? If you're using a switch, you won't see anything between the STB and the NTP server. To watch that traffic you'll need to use a hub or a managed switch with a mirror port, unless you have an Ethernet tap handy.
The router connected to the modem is a DIR-615. Normally only the modem, a printer and a DGS-2208 switch are plugged into its ethernet ports. The server is plugged into the DGS-2208. The STB is plugged into a TEG-S80g switch, which is also plugged into the DGS-2208. Moving the STB and the server straight to the router didn't change anything except slowing I/O to/from the server down from gigabit to 10/100, and shutting off internet access to equipment plugged into the TEG-S80g. I don't see anything about mirror port or managing on the feature lists on the switches' boxes.
I keep an old 10 Mb hub handy, just for such monitoring. It's supposedly possible to make a passive tap, but I've never tried it.
I looked. All I have are switches; no hubs, no tap, and no puters with more than one installed NIC.
On my home network, my router/firewall is an old computer running Linux. It has Wireshark installed, so I can ssh to it and run Wireshark to monitor the traffic passing through it.
AFAIK, an old puter functioning only as firewall/router consumes a whole lot more dead dinosaurs than the dedicated internet router I use. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
On 2013-03-15 14:14 (GMT-0400) James Knott composed:
Felix Miata wrote:
Is your server (default) gateway for STB?
No. Only gateway here I know of is the router.
How are you watching the traffic when connecting to the MIT NTP server? If you're using a switch, you won't see anything between the STB and the NTP server. To watch that traffic you'll need to use a hub or a managed switch with a mirror port, unless you have an Ethernet tap handy.
The router connected to the modem is a DIR-615. Normally only the modem, a printer and a DGS-2208 switch are plugged into its ethernet ports. The server is plugged into the DGS-2208. The STB is plugged into a TEG-S80g switch, which is also plugged into the DGS-2208. Moving the STB and the server straight to the router didn't change anything except slowing I/O to/from the server down from gigabit to 10/100, and shutting off internet access to equipment plugged into the TEG-S80g.
I don't see anything about mirror port or managing on the feature lists on the switches' boxes.
Consumer level switches generally don't have mirror ports, so unless you have a hub or tap, you have no way to see what's happening.
I keep an old 10 Mb hub handy, just for such monitoring. It's supposedly possible to make a passive tap, but I've never tried it.
I looked. All I have are switches; no hubs, no tap, and no puters with more than one installed NIC.
On my home network, my router/firewall is an old computer running Linux. It has Wireshark installed, so I can ssh to it and run Wireshark to monitor the traffic passing through it.
AFAIK, an old puter functioning only as firewall/router consumes a whole lot more dead dinosaurs than the dedicated internet router I use.
No reason why you couldn't set one up for testing purposes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Filtering on port 123, only the pool server address, server address, and IP of another PC booted and configured only for server instead of us.pool.ntp.org in /etc/ntp.conf show up.
Do you see the NTP request from the STB? And the response from the server? You need both for NTP to work. For example here I see: 187 17:41:47.670596 172.16.1.10 132.246.11.228 NTP NTP Version 4, client 188 17:41:47.704311 132.246.11.228 172.16.1.10 NTP NTP Version 4, server This shows my client making the request followed by the server response. Do you see similar?
Filtering on the STB IP, I see its IP (and server IP, since from it I telnet to the STB to run its shell) when I use it to ping Google. I also see Wireshark traffic to/from the STB using MC's FTPFS to manage its files. With time.nist.gov I tried in its GUI to make the STB sync after boot failed to sync automatically, and it failed twice, each time producing no additional Wireshark output. In its GUI I changed it to time.mit.edu and tried again. It succeeded in syncing but without producing any additional Wireshark output.
What filter were you using at that time? If NTP, then some other means is used to obtain the time. If filtering on IP address, then you must have seen something going to the time server address. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 13:53 (GMT-0400) James Knott composed:
Felix Miata wrote:
Filtering on port 123, only the pool server address, server address, and IP of another PC booted and configured only for server instead of us.pool.ntp.org in /etc/ntp.conf show up.
Do you see the NTP request from the STB? And the response from the server? You need both for NTP to work. For example here I see:
187 17:41:47.670596 172.16.1.10 132.246.11.228 NTP NTP Version 4, client 188 17:41:47.704311 132.246.11.228 172.16.1.10 NTP NTP Version 4, server
This shows my client making the request followed by the server response. Do you see similar?
Only from the other PC, nothing whatsoever from STB filtering port 123.
Filtering on the STB IP, I see its IP (and server IP, since from it I telnet to the STB to run its shell) when I use it to ping Google. I also see Wireshark traffic to/from the STB using MC's FTPFS to manage its files. With time.nist.gov I tried in its GUI to make the STB sync after boot failed to sync automatically, and it failed twice, each time producing no additional Wireshark output. In its GUI I changed it to time.mit.edu and tried again. It succeeded in syncing but without producing any additional Wireshark output.
What filter were you using at that time? If NTP, then some other means is used to obtain the time. If filtering on IP address, then you must have seen something going to the time server address.
The whole paragraph was on the same IP filter ip.addr == 192.168.#.###. Not seeing anything whatsoever when having STB sync puzzled me too. I suppose there may be NTP broadcasting coming in on the satellite data stream that it might get it from, except if that were the case, providing a server URL wouldn't make any sense. Just now I did a capture restart with the same filter, then asked the STB to time sync again even though current appeared correct. It reported success, but nothing showed up in Wireshark. On rebooting STB, what first showed up in Wireshark was the Telnet session being closed, then stuff I don't recognize that could be Samba-related: http://fm.no-ip.com/SS/Tmp/azbhd-wires1421.png This boot succeeded to auto sync while NTP server config'd to time.mit.edu. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2013-03-15 19:26, Felix Miata wrote:
On rebooting STB, what first showed up in Wireshark was the Telnet session being closed, then stuff I don't recognize that could be Samba-related: http://fm.no-ip.com/SS/Tmp/azbhd-wires1421.png This boot succeeded to auto sync while NTP server config'd to time.mit.edu.
I would investigate those samba things. - -- Cheers / Saludos, Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlFDaWwACgkQja8UbcUWM1wQTgD+JMKqE7NZqYbz3q89a88NrUH0 +OqHfVBkwuaj8xiEUgEA/2jw7xB29BL0yBEBPXRSE2B3fKpxkqR7lhoUrUzaywjW =rJ7b -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-03-15 17:06, Felix Miata wrote:
On 2013-03-15 16:29 (GMT+0100) Carlos E. R. composed:
There may be, because the unknown machine used by the OP may be using that protocol >:-)
As I am the OP, that would be a herculean surprise. Datapoints:
I know :-) But you see, you can not find ntp on it... so what is it using!? I'm just saying that there is another time protocol and that _perhaps_ that's what it uses - because I know it does not work against our Linux NTP servers. Now that I think... I have a multimedia box (Linux inside). Once I tried to make it sync against my NTP server and also had problems. I do not remember what I concluded. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFDS8AACgkQIvFNjefEBxrL2gCbB8MlpccLIMTfL0P9jmr+yKs3 AZkAn0zux5L+m/zh9Enzmt86FaP22tHk =D+7M -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 12:33 (GMT+0100) Per Jessen composed:
Felix Miata wrote:
On 2013-03-15 08:29 (GMT+0100) Per Jessen composed:
Yeah, although it's not such a bad idea to have one system sync'ed to the pool, and the rest sync'ed to that system.
Exactly what I'm trying to do
because
I have a STB running Linux
What is an STB?
Generically: http://en.wikipedia.org/wiki/Set-top_box Specifically: http://www.azbox.ca/cfm/azbox/product_details.cfm?ID=154
that when configured to use a public pool always fails to sync. When setting it up to a specific public server like time.nist.gov or time.mit.edu it randomly works or not. It seems to work no more than about once or twice a day,
That sounds like a dodgy network. Fails to sync is either a) fails to connect to time-server or b) the STB is too far out-of-sync.
Fails to connect seems like the problem, but there are no network problems apparent. Too far out of sync would be no surprise, as my previous comment below suggests. The onboard 2032 battery is showing 3.15 volts.
but typically needs rebooting multiple times a day to avoid catching video output corruption while attempting to record from it. When it fails on reboot it gets a 1999 date and 00:00 UTC time setting. I was hoping a local server would somehow be more reliable.
Do you know how it sets the date on startup? With that kind of
No idea.
difference, it would need to start ntp with '-g' to override the safety check. Maybe it uses sntp?
Both ntp and sntp produce command not found.
When I set the STB to sync to the local hostname or IP of my local NTP, it always fails, and the output of 'tcpdump -n -i etho port 123' never sees anything incoming from the STB,
Firewall issue?
Firewall off while troubleshooting networking problems.
while it is showing 140.99.51.114.123, which I would think my router should be blocking. Or could that be an IP via us.pool.ntp.org?
It could be, yes. 140.99.51.114 = tuppy.intrepidhosting.net.
I have no idea how the STB actually gets the date from the internet. It has no ntp command, no ntpd command, no tcpdump command, and no /etc/ntp.conf.
sntp?
0
A ntp server URL is fed into the GUI UI if auto sync from internet is selected.
What does that look like? ntp://server/etc ???
I've been switching it back and forth on occasion between time.nist.gov and time.mit.edu, the only two that I've ever tried that worked. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
I've been switching it back and forth on occasion between time.nist.gov and time.mit.edu, the only two that I've ever tried that worked.
What does the manual for that STB say? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 12:37 (GMT-0400) James Knott composed:
Felix Miata wrote:
I've been switching it back and forth on occasion between time.nist.gov and time.mit.edu, the only two that I've ever tried that worked.
What does the manual for that STB say?
The manual skips a lot of things, one of which is any mention at all of the Edit URL field for auto sync from internet. I'm fairly sure one of time.nist.gov or time.mit.edu was there when I got it originally, but the dealer did some preconfiguring, as the now deceased manufacturer was Portugese. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Yeah, although it's not such a bad idea to have one system sync'ed to the pool, and the rest sync'ed to that system.
Exactly what I'm trying to do
because
I have a STB running Linux that when configured to use a public pool always fails to sync. When setting it up to a specific public server like time.nist.gov or time.mit.edu it randomly works or not. It seems to work no more than about once or twice a day, but typically needs rebooting multiple times a day to avoid catching video output corruption while attempting to record from it. When it fails on reboot it gets a 1999 date and 00:00 UTC time setting. I was hoping a local server would somehow be more reliable.
When I set the STB to sync to the local hostname or IP of my local NTP, it always fails, and the output of 'tcpdump -n -i etho port 123' never sees anything incoming from the STB, while it is showing 140.99.51.114.123, which I would think my router should be blocking. Or could that be an IP via us.pool.ntp.org?
I have no idea how the STB actually gets the date from the internet. It has no ntp command, no ntpd command, no tcpdump command, and no /etc/ntp.conf. A ntp server URL is fed into the GUI UI if auto sync from internet is selected.
It would appear the problem is with the STB. Point another computer at your local server to verify it's working. I expect it is. With NTP, there are two ways it can operate. Either a computer can request the time or the server can multicast. If using the first method, you should see the requests and responses on UDP port 123. I use Wireshark to monitor the network and it works quite well. It's curious that the STB is missing the ntp stuff. Who built it? What distro? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 08:13 (GMT-0400) James Knott composed:
It's curious that the STB is missing the ntp stuff.
Heard that.
Who built it?
Defunct Portugese manufacturer Opensat, designed it, but Koreans built it.
What distro?
Can't tell. It deviates so heavily from FHS and common distro conventions that it's hard to tell how anything works. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen said the following on 03/15/2013 03:29 AM:
Cristian Rodríguez wrote:
On 03/15/2013 03:58 AM, Per Jessen wrote:
Felix Miata wrote:
Is there something on
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n...
that explains how I can configure a system to be an NTP server for other systems on a LAN?
It always is. Just point your other systems to it.
Yep, however what he really needs is just to use a server from the public ntp pool. ;)
Yeah, although it's not such a bad idea to have one system sync'ed to the pool, and the rest sync'ed to that system.
<devils advocate mode="ON"> Other than * reduced bandwidth though the gateway * simpler filewall rules * potentially smaller attack surface Why would it be a better idea? -- Clear the battlefield and let me see All the profit from our victory. You talk of freedom, starving children poor. Are you deaf when you hear the season's call? Were you there to watch the earth be scorched? Did you stand beside the spectral torch? Know the leaves of sorrow turned their face, Scattered on the ashes of disgrace. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
Other than * reduced bandwidth though the gateway * simpler filewall rules * potentially smaller attack surface
Why would it be a better idea?
The big one is to reduce the load on the remote server. It's not considered "polite" to have several devices hitting a public server. You might also want to use multicast to distribute time, instead of having every device ask for it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
Anton Aylward wrote:
Other than * reduced bandwidth though the gateway * simpler filewall rules * potentially smaller attack surface
Why would it be a better idea?
The big one is to reduce the load on the remote server.
Yep, that's the only reason I had in mind. -- Per Jessen, Zürich (1.0°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 15/03/13 09:27, James Knott escribió:
The big one is to reduce the load on the remote server. It's not considered "polite" to have several devices hitting a public server.
Well, you dont use just one server, if you use a server pool you might get dozens of servers to query. I express my skepticism that behaving NTP clients would pose a major load on resources or bandwidth to public NTP servers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 15/03/13 09:27, James Knott escribió:
The big one is to reduce the load on the remote server. It's not considered "polite" to have several devices hitting a public server.
Well, you dont use just one server, if you use a server pool you might get dozens of servers to query.
I express my skepticism that behaving NTP clients would pose a major load on resources or bandwidth to public NTP servers.
I agree with that - the whole reason the pool concept was set up was to be able to shoulder hundreds of thousands of clients, e.g. SOHO routers. I still think it's nicer to use a local server if one is available. -- Per Jessen, Zürich (-2.1°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Cristian Rodríguez wrote:
El 15/03/13 09:27, James Knott escribió:
The big one is to reduce the load on the remote server. It's not considered "polite" to have several devices hitting a public server. Well, you dont use just one server, if you use a server pool you might get dozens of servers to query.
I express my skepticism that behaving NTP clients would pose a major load on resources or bandwidth to public NTP servers.
I agree with that - the whole reason the pool concept was set up was to be able to shoulder hundreds of thousands of clients, e.g. SOHO routers. I still think it's nicer to use a local server if one is available.
All I can suggest to you both is RTFM then. http://www.pool.ntp.org/en/use.html ... "If you have a static IP address and a reasonable Internet connection (bandwidth is not so important, but it should be stable and not too highly loaded), please consider donating your server to the server pool." ... "If your Internet provider has a timeserver, or if you know of a good timeserver near you, you should use that and not this list - you'll probably get better time and you'll use fewer network resources." ... "Be friendly. Many servers are provided by volunteers, and almost all time servers are really file or mail or webservers which just happen to also run ntp. So don't use more than four time servers in your configuration, and don't play tricks with burst or minpoll" ... *"If you are synchronising a network to pool.ntp.org, please set up one of your computers as a time server and synchronize the other computers to that one."* -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
Per Jessen wrote:
Cristian Rodríguez wrote:
El 15/03/13 09:27, James Knott escribió:
The big one is to reduce the load on the remote server. It's not considered "polite" to have several devices hitting a public server. Well, you dont use just one server, if you use a server pool you might get dozens of servers to query.
I express my skepticism that behaving NTP clients would pose a major load on resources or bandwidth to public NTP servers.
I agree with that - the whole reason the pool concept was set up was to be able to shoulder hundreds of thousands of clients, e.g. SOHO routers. I still think it's nicer to use a local server if one is available.
All I can suggest to you both is RTFM then.
[snip - irelevant in this context]
... *"If you are synchronising a network to pool.ntp.org, please set up one of your computers as a time server and synchronize the other computers to that one."*
That is exactly what Felix is trying to achieve and what I have recommended in least two postings. -- Per Jessen, Zürich (5.4°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Dave Howorth wrote:
Per Jessen wrote:
Cristian Rodríguez wrote:
I express my skepticism that behaving NTP clients would pose a major load on resources or bandwidth to public NTP servers.
I agree with that
[snip - irelevant in this context]
... *"If you are synchronising a network to pool.ntp.org, please set up one of your computers as a time server and synchronize the other computers to that one."*
That is exactly what Felix is trying to achieve and what I have recommended in least two postings.
I was simply responding to Cristian's statement above and your support of it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2013-03-18 at 12:03 +0000, Dave Howorth wrote:
Per Jessen wrote:
Cristian Rodríguez wrote:
El 15/03/13 09:27, James Knott escribió:
The big one is to reduce the load on the remote server. It's not considered "polite" to have several devices hitting a public server. Well, you dont use just one server, if you use a server pool you might get dozens of servers to query.
I express my skepticism that behaving NTP clients would pose a major load on resources or bandwidth to public NTP servers.
I agree with that - the whole reason the pool concept was set up was to be able to shoulder hundreds of thousands of clients, e.g. SOHO routers. I still think it's nicer to use a local server if one is available.
All I can suggest to you both is RTFM then.
http://www.pool.ntp.org/en/use.html
... "If you have a static IP address and a reasonable Internet connection (bandwidth is not so important, but it should be stable and not too highly loaded), please consider donating your server to the server pool."
... "If your Internet provider has a timeserver, or if you know of a good timeserver near you, you should use that and not this list - you'll probably get better time and you'll use fewer network resources."
... "Be friendly. Many servers are provided by volunteers, and almost all time servers are really file or mail or webservers which just happen to also run ntp. So don't use more than four time servers in your configuration, and don't play tricks with burst or minpoll"
... *"If you are synchronising a network to pool.ntp.org, please set up one of your computers as a time server and synchronize the other computers to that one."*
Not wanting to hijack the thread, but what kind of load does running an ntp server put on a machine? Say it is on a local network and serving < 4 clients? I ask because I am (very slowly) setting up a remote system that has no internet (only local), but does have a high-end GPS (with a PPS signal). The machine I hope to use for this will have other tasks that would like a reasonable response time. Just curious. Not even sure how to quantify this. -- Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
Not wanting to hijack the thread, but what kind of load does running an ntp server put on a machine? Say it is on a local network and serving < 4 clients?
No measurable or noticeable load. You could have it use broadcast too, means less network traffic. -- Per Jessen, Zürich (4.4°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 18/03/13 17:09, Roger Oberholtzer escribió:
Not wanting to hijack the thread, but what kind of load does running an ntp server put on a machine? Say it is on a local network and serving < 4 clients?
Very little, in a LAN however, you probably do not want NTP but IEEE 1588-2008 Precision Time Protocol (PTP). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Mon, 18 Mar 2013 16:56:45 -0300
Cristian Rodríguez
El 18/03/13 17:09, Roger Oberholtzer escribió:
Not wanting to hijack the thread, but what kind of load does running an ntp server put on a machine? Say it is on a local network and serving < 4 clients?
Very little, in a LAN however, you probably do not want NTP but IEEE 1588-2008 Precision Time Protocol (PTP).
Why? PTP was designed for cases when full NTP implementation is not possible (like embedded systems). So why exactly is it better when you do have full NTP implementation already? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2013-03-18 at 16:56 -0300, Cristian Rodríguez wrote:
El 18/03/13 17:09, Roger Oberholtzer escribió:
Not wanting to hijack the thread, but what kind of load does running an ntp server put on a machine? Say it is on a local network and serving < 4 clients?
Very little, in a LAN however, you probably do not want NTP but IEEE 1588-2008 Precision Time Protocol (PTP).
We have things like GigE Vision cameras that will get time via NTP, and then timestamp images based on that. So it is not fully up to us to decide to use something other than NTP. But I have seen other embedded devices that like PTP. Our first step will be NTP. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 15 March 2013, Cristian Rodríguez wrote:
On 03/15/2013 03:58 AM, Per Jessen wrote:
Felix Miata wrote:
Is there something on
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-refere nce/cha.netz.xntp.html
that explains how I can configure a system to be an NTP server for other systems on a LAN?
It always is. Just point your other systems to it.
Yep, however what he really needs is just to use a server from the public ntp pool. ;)
Probably not ... If you rely on public NTP servers only for anything else than single user desktops than you do it wrong. http://serverfault.com/questions/221834/local-or-public-ntp-servers cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----Original Message-----
From: Cristian Rodríguez
Felix Miata wrote:
Is there something on
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n...
that explains how I can configure a system to be an NTP server for other systems on a LAN?
It always is. Just point your other systems to it.
Yep, however what he really needs is just to use a server from the public ntp pool. ;) -----Original Message----- perhaps not >-; Some people have networks that are isolated from Internet... When using something like kerberos, it's rather important that all machines use the same time, even if it is stratum-256 ;-8 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Is there something on http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n... that explains how I can configure a system to be an NTP server for other systems on a LAN? If it's there, I'm not recognizing it, and it's not obvious to me looking at time config in YaST2 or elsewhere in YaST2, or in /etc/ntp.conf.
Just use NTP and a computer will also become a server for other computers.
Also, what exactly does running as daemon in context of NTP mean or imply?
Like any other daemon, it just runs in the background. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-03-15 07:30 (GMT-0400) James Knott composed:
Felix Miata wrote:
Also, what exactly does running as daemon in context of NTP mean or imply?
Like any other daemon, it just runs in the background.
I still don't understand how running as daemon in background differs operationally from how it works using the non-daemon YaST2 option. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
On 2013-03-15 07:30 (GMT-0400) James Knott composed:
Felix Miata wrote:
Also, what exactly does running as daemon in context of NTP mean or imply?
Like any other daemon, it just runs in the background.
I still don't understand how running as daemon in background differs operationally from how it works using the non-daemon YaST2 option.
Servers, including NTP normally run in that background. That is the user doesn't have to do anything to start the server etc. You can also manually start, stop or restart the servers running in the backround with the "rc" commands, such as rcntp start? With some servers, you can manually start them without using rc in front of the server name. You can also start them in the background by adding a "&" after the command. When you configure it in Yast, you are telling it to start as a dameon. Even changing a server configuration in Yast will generally cause a restart. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 15/03/13 14:51, Felix Miata escribió:
I still don't understand how running as daemon in background differs operationally from how it works using the non-daemon YaST2 option.
Traditionally it runs as a daemon because in order to obtain the most accurate time resolution, ntp needs some time to settle down, unfortunately it sometimes take hours... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 15/03/2013 03:13, Felix Miata ha scritto:
Is there something on http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n... that explains how I can configure a system to be an NTP server for other systems on a LAN? If it's there, I'm not recognizing it, and it's not obvious to me looking at time config in YaST2 or elsewhere in YaST2, or in /etc/ntp.conf.
Also, what exactly does running as daemon in context of NTP mean or imply?
This howto is Ubuntu specific http://ubuntuforums.org/showthread.php?t=862620 but if you need to learn something about NTP. I think is a good startpoint. Rergards, -- Marco Calistri (amdturion) opensuse 12.2 (Mantis) 64 bit - Kernel 3.4.28-2.20-desktop Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (13)
-
Andrey Borzenkov -
Anton Aylward -
Carlos E. R. -
Cristian Rodríguez -
Dave Howorth -
Felix Miata -
Hans Witvliet -
James Knott -
Lars Müller -
Marco Calistri -
Per Jessen -
Roger Oberholtzer -
Ruediger Meier