Initial Settings : Firewall2023/02/20

	Configure Firewall and SELinux.
[1]	It's possible to display FireWall Service Status like follows. (enabled by default)

[root@localhost ~]#

systemctl status firewalld

*  firewalld.service - firewalld - dynamic firewall daemon
     Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor>
     Active: active (running) since Mon 2023-02-20 09:41:13 JST; 3min 57s ago
       Docs: man:firewalld(1)
   Main PID: 772 (firewalld)
      Tasks: 2 (limit: 24744)
     Memory: 41.0M
        CPU: 259ms
     CGroup: /system.slice/firewalld.service
             +- 772 /usr/bin/python3 -s /usr/sbin/firewalld --nofork --nopid

# [Active: active (running) ***] means firewalld is running now

[2]	If you use FireWall service, it needs to modify FireWall settings manually because incoming requests for services are mostly not allowed by default. Refer to here for basic Firewall operation and settins. Configuration examples of AlmaLinux 9 on this site are based on the environment Firewalld service is always enabled.
[3]	If you don't need FireWall service because of some reasons like that some FireWall Machines are running in your Local Netowrk or others, it's possbile to stop and disable FireWall service on AlmaLinux server like follows.

# stop service

[root@localhost ~]#

systemctl stop firewalld

# disable service

[root@localhost ~]#

systemctl disable firewalld

Removed /etc/systemd/system/multi-user.target.wants/firewalld.service.
Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.

Initial Settings : SELinux

[4]	It's possible to display current SELinux (Security-Enhanced Linux) Status like follows. (enabled by default)

[root@localhost ~]#

getenforce

Enforcing     # SELinux is enabled

[5]	If you enable SELinux, there are cases to modify SELinux policies manually because sometimes SELinux stops applications. Refer to here for basic SELinux operation and settins. Configuration examples of AlmaLinux 9 on this site are based on the environment SELinux is always Enforcing.
[6]	If you don't need SELinux feature because of some reasons like that your server is running only in Local safety Network or others, it's possbile to disable SELinux like follows.

# disable SELinux

[root@localhost ~]#

grubby --update-kernel ALL --args selinux=0

# apply changes to restart computer

[root@localhost ~]#

reboot

# if falling back to enable, run like follows

[root@localhost ~]#

grubby --update-kernel ALL --remove-args selinux

Matched Content