In setting up my new CentOS 6 laptop, I replaced
/etc/sysconfig/iptables with my own, very restrictive
version. I then tried to restart the iptables daemon,
but it reported that my new iptables was unreadable.
On a guess, I disabled selinux, and my problem was
solved. Later, I re-enabled selinux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/30/2011 03:08 PM, Michael D. Berger wrote:
In setting up my new CentOS 6 laptop, I replaced
/etc/sysconfig/iptables with my own, very restrictive version. I
then tried to restart the iptables daemon, but it reported that my
new iptables
Michael D. Berger wrote:
In setting up my new CentOS 6 laptop, I replaced
/etc/sysconfig/iptables with my own, very restrictive
version. I then tried to restart the iptables daemon,
but it reported that my new iptables was unreadable.
On a guess, I disabled selinux, and my problem was
On 30/08/11 20:08, Michael D. Berger wrote:
In setting up my new CentOS 6 laptop, I replaced
/etc/sysconfig/iptables with my own, very restrictive
version. I then tried to restart the iptables daemon,
but it reported that my new iptables was unreadable.
On a guess, I disabled selinux, and my
On 08/30/2011 03:23 PM, Ned Slider wrote:
On 30/08/11 20:08, Michael D. Berger wrote:
In setting up my new CentOS 6 laptop, I replaced
/etc/sysconfig/iptables with my own, very restrictive
version. I then tried to restart the iptables daemon,
but it reported that my new iptables was
5 matches
Mail list logo