Oh wow, solved it in 1 try 👍
[root@eset ~]# service iptables status
Redirecting to /bin/systemctl status iptables.service
● iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled; vendor preset: disabled)
Active: inactive (dead)
[root@eset ~]#
Starting the service fixed the problem immediately, but If i understand that right Disabled means it won't start on reboot. I enabled it but vendor preset stays disabled. I hope It stays up after reboot.
[root@eset ~]# systemctl enable iptables
Created symlink from /etc/systemd/system/basic.target.wants/iptables.service to /usr/lib/systemd/system/iptables.service.
[root@eset ~]# service iptables status
Redirecting to /bin/systemctl status iptables.service
● iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
Active: active (exited) since Thu 2019-06-27 20:38:05 CEST; 11min ago
Main PID: 49265 (code=exited, status=0/SUCCESS)
Jun 27 20:38:04 eset systemd[1]: Starting IPv4 firewall with iptables...
Jun 27 20:38:05 eset iptables.init[49265]: iptables: Applying firewall rules: [ OK ]
Jun 27 20:38:05 eset systemd[1]: Started IPv4 firewall with iptables.
Thanks !!!!