RE: -EXT-[chrony-users] New system ntp daemon on macOS 10.13

2017-07-25 Thread Parker, Michael D.
HmmmIf I recall timed protocol was used prior to NTP protocol becoming widely adapted. * * * Michael D. Parker General Atomics – ElectroMagnetics Systems Division (EMS) michael.d.par...@ga.com  < NOTE: Remember to include my middle initial >

[chrony-users] New system ntp daemon on macOS 10.13

2017-07-25 Thread Bryan Christianson
I was just looking through macOS 10.13, wondering why ntpd was not running. Apple seem to have got rid of it and are now using something called timed. I don't know anything at all about it, other than its running (I just enabled it after stopping chronyd) and I think is using the ntpd config

RE: -EXT-Re: [chrony-users] Using symbolic network names in /etc/chrony.conf file?

2017-07-25 Thread Parker, Michael D.
BTW, Several programs allow one to basically use (in IPV4) the form 10.10.10.10/16 to mean 10.10.0.0/16.I see no issue here as the Systems administrator should be aware of this. As for using the /etc/networksfor the symbolic name that might be fine, however, having an entry in that file

[chrony-users] chrony-3.2-pre1 released

2017-07-25 Thread Miroslav Lichvar
The first prerelease for chrony-3.2 is now available. The sources can be downloaded here: https://download.tuxfamily.org/chrony/chrony-3.2-pre1.tar.gz MD5 and SHA1 sums: 58f8b1b439f5d1a8084a2668b8284b25 chrony-3.2-pre1.tar.gz 7c58a02ae12bcb79c02317f21ba2b109c510d04b chrony-3.2-pre1.tar.gz

Re: [chrony-users] Using symbolic network names in /etc/chrony.conf file?

2017-07-25 Thread Bill Unruh
On Wed, 26 Jul 2017, Bryan Christianson wrote: My view on this is that host/prefix is a shorthand notation for (ip_address & mask) and that should work for both IPv6 and IPv4. i.e. there is an assumption that people understand how the network and mask are both calculated and used. I have no

Re: [chrony-users] Using symbolic network names in /etc/chrony.conf file?

2017-07-25 Thread Bryan Christianson
> On 26/07/2017, at 3:07 AM, Miroslav Lichvar wrote: > > Right. There may be also records. To which addresses it should > apply? The addresses may change over time. Should chronyd try to > follow the changes? That would be tricky. I generally don't recommend > using

Re: [chrony-users] Using symbolic network names in /etc/chrony.conf file?

2017-07-25 Thread Bryan Christianson
My view on this is that host/prefix is a shorthand notation for (ip_address & mask) and that should work for both IPv6 and IPv4. i.e. there is an assumption that people understand how the network and mask are both calculated and used. I have no problem with the ip part being either a name or an

Re: [chrony-users] Using symbolic network names in /etc/chrony.conf file?

2017-07-25 Thread Miroslav Lichvar
On Tue, Jul 25, 2017 at 10:28:09AM -0400, Chris Greenman wrote: > When you specify a hostname, that's it. It's a 32bit address (ipv4 of > course). Throwing a netmask on it does nothing except specify that your > network segment has 64,510 usable addresses. Now if you edit /etc/networks > and add

Re: [chrony-users] Using symbolic network names in /etc/chrony.conf file?

2017-07-25 Thread Chris Greenman
When you specify a hostname, that's it. It's a 32bit address (ipv4 of course). Throwing a netmask on it does nothing except specify that your network segment has 64,510 usable addresses. Now if you edit /etc/networks and add mynet 10.10.0.0 then you can use the mynet/16 notation in your

Re: [chrony-users] Using symbolic network names in /etc/chrony.conf file?

2017-07-25 Thread Miroslav Lichvar
On Tue, Jul 25, 2017 at 08:37:18AM +0200, Miroslav Lichvar wrote: > On Mon, Jul 24, 2017 at 08:24:57PM +, Parker, Michael D. wrote: > > The chrony allow directive allows the addition of a symbolic hostname in its > > specification. However, I took a leap in entering the following directive: >

Re: [chrony-users] Using symbolic network names in /etc/chrony.conf file?

2017-07-25 Thread Miroslav Lichvar
On Mon, Jul 24, 2017 at 08:24:57PM +, Parker, Michael D. wrote: > The chrony allow directive allows the addition of a symbolic hostname in its > specification. However, I took a leap in entering the following directive: > > allow hostname/16 > > which failed to do what I expected but no