On 10/31/14 09:51, jd1008 wrote:
# systemctl status firewalld.service
firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
Active: inactive (dead) since Thu 2014-10-30 19:44:22 MDT; 4min 2s ago
Main PID: 659 (code=killed, signal=TERM)
CGroup: /system.slice/firewalld.service
Oct 30 19:44:21 localhost.localdomain systemd[1]: Started firewalld - dynamic firewall
daemon.
Oct 30 19:44:22 localhost.localdomain systemd[1]: Stopping firewalld - dynamic firewall
daemon...
Oct 30 19:44:22 localhost.localdomain systemd[1]: Stopped firewalld - dynamic firewall
daemon.
OK - I will disable it, but you stated earlier that it is not the culprit???
I made no statement about your environment. I made an observation about a working
environment on my test system in response to Tom's "god knows what it does"
statement.
# systemctl status iptables.service
iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled)
Active: active (exited) since Thu 2014-10-30 19:46:19 MDT; 3min 41s ago
Process: 2337 ExecStop=/usr/libexec/iptables/iptables.init stop (code=exited,
status=0/SUCCESS)
Process: 2446 ExecStart=/usr/libexec/iptables/iptables.init start (code=exited,
status=0/SUCCESS)
Main PID: 2446 (code=exited, status=0/SUCCESS)
Oct 30 19:46:19 localhost.localdomain iptables.init[2446]: iptables: Applying firewall
rules: [ OK ]
Oct 30 19:46:19 localhost.localdomain systemd[1]: Started IPv4 firewall with iptables.
You shouldn't have both of those services enabled.
--
If you can't laugh at yourself, others will gladly oblige.