Displaying 5 results from an estimated 5 matches for "filrewall".
Did you mean:
filewall
2016 Dec 27
2
chronyd configuration as a local ntp server
...AIK the only thing needed to make your host an NTP server using chrony
is to set the allow line to the network address in CIDR format of the
network you want to be served, and uncomment it. The restart chronyd.
You also need to ensure that port 123 (NTP) is open to your internal
network on your filrewall.
I have a CentOS 6 box that is an NTP server for my network. CentOS 7
works the same way.
On 12/27/2016 08:25 AM, Fred Smith wrote:
> On Mon, Dec 26, 2016 at 11:04:22PM -0500, Robert Moskowitz wrote:
>> This is for centos 7 that has chronyd 2.1.1
>>
>> I am looking into how...
2016 Dec 27
0
chronyd configuration as a local ntp server
...eeded to make your host an NTP server using
> chrony is to set the allow line to the network address in CIDR format
> of the network you want to be served, and uncomment it. The restart
> chronyd. You also need to ensure that port 123 (NTP) is open to your
> internal network on your filrewall.
>
> I have a CentOS 6 box that is an NTP server for my network. CentOS 7
> works the same way.
>
>
> On 12/27/2016 08:25 AM, Fred Smith wrote:
>> On Mon, Dec 26, 2016 at 11:04:22PM -0500, Robert Moskowitz wrote:
>>> This is for centos 7 that has chronyd 2.1.1
>...
2016 Dec 27
2
chronyd configuration as a local ntp server
This is for centos 7 that has chronyd 2.1.1
I am looking into how to use chronyd as my local ntp server.
On my old servers with ntpd I had local access control lines like:
restrict 192.168.128.0 mask 255.255.255.0 nomodify notrap
But in looking for documentation on chronyd I did not find anything on
this at:
https://chrony.tuxfamily.org/doc/2.1/manual.html
In the actual /etc/chronyd.conf
2013 Mar 16
23
Shorewall 4.5.15 Beta 1
Beta 1 is now availablew for testing.
Problems Corrected:
1) Previously, the Shorewall and Shorewall6 install.sh scripts did two
things wrong with respect to the /etc/shorewall[6]/routes file:
- The existing file was unconditionally removed.
- A skeleton file was not installed when SPARSE was not set in
the shorewallrc file.
Additionally, the installer would remove
2013 Mar 16
23
Shorewall 4.5.15 Beta 1
Beta 1 is now availablew for testing.
Problems Corrected:
1) Previously, the Shorewall and Shorewall6 install.sh scripts did two
things wrong with respect to the /etc/shorewall[6]/routes file:
- The existing file was unconditionally removed.
- A skeleton file was not installed when SPARSE was not set in
the shorewallrc file.
Additionally, the installer would remove