CentOS7 - Revision history

Leaky: /* Enable disk quota on ext4 */ added yum notes

2019-11-08T14:05:43Z

‎Enable disk quota on ext4: added yum notes

Leaky: /* Enable firewall */

2019-09-27T07:17:32Z

‎Enable firewall

Leaky: /* Enable firewall */

2018-08-14T18:17:17Z

‎Enable firewall

Leaky: /* Disable firewalld and use iptables */

2018-05-05T11:43:42Z

‎Disable firewalld and use iptables

Leaky: /* Change server hostname */

2017-08-06T19:29:13Z

‎Change server hostname

Leaky: /* Enable firewall */

2016-06-30T10:00:12Z

‎Enable firewall

Leaky: /* Enable firewall */

2016-06-03T07:38:27Z

‎Enable firewall

Leaky: /* Enable firewall */

2016-06-03T07:38:07Z

‎Enable firewall

Leaky: /* Enable firewall */

2016-05-24T22:30:46Z

‎Enable firewall

Leaky: /* Enable firewall */ How to use iptables instead of firewall-cmd

2016-03-03T09:21:36Z

‎Enable firewall: How to use iptables instead of firewall-cmd

← Older revision		Revision as of 14:05, 8 November 2019
Line 127:		Line 127:

	# repquota -auv		# repquota -auv
		+
		+	== Fix an interrupted yum upgrade ==
		+
		+	(notes copied from [https://www.thegeekdiary.com/centos-rhel-67-how-to-recover-an-interrupted-yum-package-installation/ www.thegeekdiary.com])
		+
		+	Normally if something interrupts a yum upgrade there will be duplicate package warnings or dependencies that haven't been filled. To resolve the problems, it's possible to retry the transaction.
		+
		+	# yum history
		+	Loaded plugins: fastestmirror
		+	ID \| Command line \| Date and time \| Action(s) \| Altered
		+	-------------------------------------------------------------------------------
		+	152 \| upgrade \| 2019-11-02 11:52 \| E, I, U \| 29 **
		+	151 \| upgrade -y \| 2019-10-20 12:44 \| O, U \| 10 EE
		+	150 \| upgrade \| 2019-10-11 08:21 \| Update \| 6
		+
		+	In this instance, the ** at the end of id 152 indicates that the transaction was interrupted.
		+
		+	> - The rpmdb was changed, outside yum, after the transaction.
		+	< - The rpmdb was changed, outside yum, before the transaction.
		+	* - The transaction aborted before completion.
		+	# - The transaction completed, but with a non-zero status.
		+	E - The transaction completed fine, but had warning/error output during the transaction.
		+	P - The transaction completed fine, but problems already existed in the rpmdb.
		+	s - The transaction completed fine, but --skip-broken was enabled and had to skip some packages.
		+
		+	To resolve this issue, I force-reinstalled all the packages in transaction 152 using the '''redo force-reinstall''' option with yum history.
		+
		+	# yum history redo force-reinstall 152
		+
		+	Always read what is going to be performed and don't blindly accept it otherwise the system may end up not working.

← Older revision		Revision as of 07:17, 27 September 2019
Line 77:		Line 77:

	[root@localhost ~]# firewall-cmd --reload		[root@localhost ~]# firewall-cmd --reload
		+
		+	Add port forwarding for port 22 to port 922 on the same machine
		+
		+	[root@localhost ~]# firewall-cmd --add-forward-port=port=22:proto=tcp:toport=922

	== Disable firewalld and use iptables ==		== Disable firewalld and use iptables ==

@@ Line 69: / Line 69: @@
       --add-rich-rule='rule family="ipv4" source address="1.2.3.0/24"
       port protocol="tcp" port="22222" accept'
 Reload the firewall rules

← Older revision		Revision as of 11:43, 5 May 2018
Line 103:		Line 103:

	$ journalctl -f -u iptables.service		$ journalctl -f -u iptables.service
		+
		+	== Enable disk quota on ext4 ==
		+
		+	Add to /etc/fstab the following options on the line with the ext4 fs (eg /home):
		+
		+	usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0
		+
		+	Then check quotas and enable them
		+
		+	# quotaoff -a
		+	# quotacheck -auvgm
		+	# quotaon -a
		+
		+	To check the quotas
		+
		+	# repquota -auv

@@ Line 4: / Line 4: @@
   [root@localhost ~]# hostnamectl status
-−
     Static hostname: localhost.localdomain
           Icon name: computer-vm
@@ Line 21: / Line 21: @@
 Check the host name again (Close the session and open new session using putty or console)
 == Enable firewall ==

@@ Line 42: / Line 42: @@
   [root@localhost ~]# firewall-cmd --permanent --zone=public --remove-service=ssh
-Add a rule for a service from a specific source port
+Add a rule for access to a service on a specific local port from a specific source IP
   [root@localhost ~]# firewall-cmd --permanent --zone=public \
-      --remove-rich-rule='rule family="ipv4" source address="1.2.3.0/24"
+      --add-rich-rule='rule family="ipv4" source address="1.2.3.0/24"
       port protocol="tcp" port="22222" accept'

← Older revision		Revision as of 07:38, 3 June 2016
Line 41:		Line 41:

	[root@localhost ~]# firewall-cmd --permanent --zone=public --remove-service=ssh		[root@localhost ~]# firewall-cmd --permanent --zone=public --remove-service=ssh
		+
		+	Add a rule for a service from a specific source port
		+
		+	[root@localhost ~]# firewall-cmd --permanent --zone=public \
		+	--remove-rich-rule='rule family="ipv4" source address="1.2.3.0/24"
		+	port protocol="tcp" port="10022" accept'

	Reload the firewall rules		Reload the firewall rules

@@ Line 37: / Line 37: @@
   [root@localhost ~]# firewall-cmd --permanent --zone=public --add-port=22222/tcp
 Reload the firewall rules
   [root@localhost ~]# firewall-cmd --reload
 == Disable firewalld and use iptables ==

← Older revision		Revision as of 09:21, 3 March 2016
Line 41:		Line 41:

	[root@localhost ~]# firewall-cmd --reload		[root@localhost ~]# firewall-cmd --reload
		+
		+
		+	== Disable firewalld and use iptables ==
		+
		+	(content taken from racktables.com in case it disappears)
		+
		+	The first step is to stop and mask the firewalld service (i.e., the service you do not want to use):
		+
		+	$ systemctl stop firewalld
		+	$ systemctl mask firewalld
		+
		+	Then, install the "iptables-services" package (if it is not already installed):
		+
		+	$ yum install iptables-services
		+
		+	Enable the service to start at boot-time:
		+
		+	$ systemctl enable iptables
		+
		+	If you are saving your rules in that /etc/sysconfig/iptables file, you will then need to run one of the following commands:
		+
		+	$ service iptables restart # OR:
		+	$ systemctl restart iptables
		+
		+	Next, check that the iptables service is "active" with:
		+
		+	$ systemctl status iptables
		+
		+	You can query the systemd journal for a "log" of the changes you made to the iptables service with:
		+
		+	$ journalctl -f -u iptables.service