[Dorset] Setting up an NTP Server in a Closed Network

2017-08-21 Thread Terry Coles
Hi, We've been trying to set up a local NTP Server on our WMT network which consists of a Wireless AP (we're not connecting to the Internet), the 'Master' Pi and a 'Remote' Pi. The Wireless AP is only there for debugging and to act as a Switch and the Pi's are interconnected with Cat 5

Re: [Dorset] Setting up an NTP Server in a Closed Network

2017-08-21 Thread Bob Dunlop
Hi, On Mon, Aug 21 at 04:32, Terry Coles wrote: ... > However, it doesn't work. Everything is sitting at stratum 16 "no trusted clocks", the server won't offer a syncronisation service at this level. The server needs a clock it trusts before it will serve the time. Add the following two lines

Re: [Dorset] Exclude hidden folder in rsync

2017-08-21 Thread Tim
On 20/08/17 21:58, Ralph Corderoy wrote: Hi Tim, I want to compress my rsynced home folder, I want the video folder in the final compressed file but I don't want tar to try and compress it as it compresses the rest of the home folder, does that make sense? Yes, but it can't be done. tar(1)

Re: [Dorset] Setting up an NTP Server in a Closed Network

2017-08-21 Thread Terry Coles
On Monday, 21 August 2017 17:30:18 BST Terry Coles wrote: > > Add the following two lines to your servers config. > > > > server 127.127.1.0 > > fudge 127.127.1.0 stratum 12 > > Hmmm. I tried that and still nogo. Should that have been 127.0.0.1? (I > tried that and it still didn't

Re: [Dorset] Setting up an NTP Server in a Closed Network

2017-08-21 Thread Terry Coles
On Monday, 21 August 2017 16:56:50 BST Bob Dunlop wrote: > Everything is sitting at stratum 16 "no trusted clocks", the server won't > offer a syncronisation service at this level. > > The server needs a clock it trusts before it will serve the time. > > Add the following two lines to your

Re: [Dorset] Setting up an NTP Server in a Closed Network

2017-08-21 Thread Terry Coles
On Monday, 21 August 2017 16:32:12 BST Terry Coles wrote: > For the Client we've added: > > server 192.168.0.2 > > to the server pool. > > For the Server we've added: > > restrict 192.168.0.0 mask 255.255.255.0 > > and: > >broadcast 192.168.0.255 > > However, it doesn't work.