Configuration (Ubuntu) - Revision history

Sstrutt: /* Setup (Post v12 Ubunutu) */ Updated restart command

2020-07-26T19:30:07Z

Setup (Post v12 Ubunutu): Updated restart command

← Older revision		Revision as of 19:30, 26 July 2020
Line 153:		Line 153:
	#* <code>SNMPDOPTS='-LS0-5d -Lf /dev/null </code>		#* <code>SNMPDOPTS='-LS0-5d -Lf /dev/null </code>
	# Restart SNMP		# Restart SNMP
	#* <code> ~~/etc/init.d/~~snmpd ~~restart~~ </code>		#* <code> systemctl restart snmpd </code>
	# Test with the following, replacing <hostname> with server's hostname (must be run from a machine with snmp installed, not just snmpd)		# Test with the following, replacing <hostname> with server's hostname (must be run from a machine with snmp installed, not just snmpd)
	#* <code> snmpwalk -v 1 -c public <hostname> system <hostname> </code>		#* <code> snmpwalk -v 1 -c public <hostname> system <hostname> </code>

Sstrutt: /* Deny a Specific Host */ Updated with insert rule

2020-06-11T09:02:49Z

Deny a Specific Host: Updated with insert rule

← Older revision		Revision as of 09:02, 11 June 2020
Line 71:		Line 71:

	=== Deny a Specific Host ===		=== Deny a Specific Host ===
	If you want to deny a specific host (because its spamming or hacking you for example) you need to ensure that the deny rule is one of the first processed. Otherwise the host might still be able to access on port 80 (if you're running a web server and have a general allow rule for http traffic). ~~It's easiest~~ to ~~edit~~ the ~~config files directly.~~		If you want to deny a specific host (because its spamming or hacking you for example) you need to ensure that the deny rule is one of the first processed. Otherwise the host might still be able to access on port 80 (if you're running a web server and have a general allow rule for http traffic). To do so you need to insert a deny rule at the top of your rule-set,

	To deny all traffic from 46.118.117.13...		To deny all traffic from 46.118.117.13...
			<pre> ufw insert 1 deny from 46.118.117.13 to any </pre>

			Alternatively you can edit the UFW config file direct, but the denied hosts will ''not'' appear when showing the firewall status, which will cause you problems later down the line...
	# Edit <code>/etc/ufw/before.rules</code>		# Edit <code>/etc/ufw/before.rules</code>
	# Create a new section under the <code> # drop INVALID packets </code> section (near the top of the file)		# Create a new section under the <code> # drop INVALID packets </code> section (near the top of the file)
Line 82:		Line 85:
	# Reload the firewall to apply the new config		# Reload the firewall to apply the new config
	#* <code> ufw reload </code>		#* <code> ufw reload </code>

	~~Note that the denied hosts will ''not'' appear when showing the firewall status, which is an irritation.~~

	= SNMP =		= SNMP =

Sstrutt: /* Setup (Post v12) */ Updated with snmpd option to reduce how verbose logging level is

2018-02-07T15:53:49Z

Setup (Post v12): Updated with snmpd option to reduce how verbose logging level is

← Older revision		Revision as of 15:53, 7 February 2018
Line 140:		Line 140:
	syscontact info@sandfordit.com		syscontact info@sandfordit.com

	=== Setup (Post v12) ===		== Setup (Post v12 Ubunutu) ==
	# Run the following command to update the package database		# Run the following command to update the package database
	#* <code> apt-get update </code>		#* <code> apt-get update </code>
Line 147:		Line 147:
	# Replace existing config file with contents as shown below the procedure		# Replace existing config file with contents as shown below the procedure
	#* <code> vi /etc/snmp/snmpd.conf </code>		#* <code> vi /etc/snmp/snmpd.conf </code>
			# Throttle down logging verbosity (otherwise log is spammed with <code>Connection from UDP</code> messages
			#* <code> vi /etc/default/snmpd </code>
			#* Set the option <code>-LS0-5d</code> so the config line starts...
			#* <code>SNMPDOPTS='-LS0-5d -Lf /dev/null </code>
	# Restart SNMP		# Restart SNMP
	#* <code> /etc/init.d/snmpd restart </code>		#* <code> /etc/init.d/snmpd restart </code>

Sstrutt: /* SNMP */ Added Setup (Post v12)

2016-08-23T15:26:56Z

SNMP: Added Setup (Post v12)

← Older revision		Revision as of 15:26, 23 August 2016
Line 86:		Line 86:

	= SNMP =		= SNMP =
			Note that the way in which the SNMP daemon/agent needs to be configured varies between OS version.

	== Setup (Pre v10 Ubuntu) ==		== Setup (Pre v10 Ubuntu) ==
	# Run the following command to update the package database		# Run the following command to update the package database
Line 107:		Line 109:
	syscontact info@sandfordit.com		syscontact info@sandfordit.com

	== Setup (v10 Ubuntu ~~onwards~~) ==		== Setup (v10/v12 Ubuntu) ==
	# Run the following command to update the package database		# Run the following command to update the package database
	#* <code> apt-get update </code>		#* <code> apt-get update </code>
Line 137:		Line 139:
	syslocation "CR DC"		syslocation "CR DC"
	syscontact info@sandfordit.com		syscontact info@sandfordit.com

			=== Setup (Post v12) ===
			# Run the following command to update the package database
			#* <code> apt-get update </code>
			# Run the following command to install SNMP
			#* <code> apt-get install snmpd </code>
			# Replace existing config file with contents as shown below the procedure
			#* <code> vi /etc/snmp/snmpd.conf </code>
			# Restart SNMP
			#* <code> /etc/init.d/snmpd restart </code>
			# Test with the following, replacing <hostname> with server's hostname (must be run from a machine with snmp installed, not just snmpd)
			#* <code> snmpwalk -v 1 -c public <hostname> system <hostname> </code>

			# Allows SNMP Get's from IP
			rocommunity dont-leave-as-public 192.168.123.10
			sysLocation CR DC
			sysContact info@sandfordit.com

	= Hostname Change =		= Hostname Change =

Sstrutt: /* = To MySQL Database */ Title fix

2014-01-03T15:19:50Z

= To MySQL Database: Title fix

← Older revision		Revision as of 15:19, 3 January 2014
Line 213:		Line 213:
	service rsyslog restart		service rsyslog restart

	== To MySQL Database =		== To MySQL Database ==
	This procedure achieves three things...		This procedure achieves three things...
	# Allows remote hosts to use the local server as a syslog destination		# Allows remote hosts to use the local server as a syslog destination

Sstrutt: /* Server */ Config fix

2014-01-03T15:19:26Z

Server: Config fix

← Older revision		Revision as of 15:19, 3 January 2014
Line 207:		Line 207:

	Add the following section so that received syslog messages get put into a folder for each host its received from...		Add the following section so that received syslog messages get put into a folder for each host its received from...
	$template PerHostLog,"/var/log/~~system-~~%HOSTNAME%~~.log~~"		$template PerHostLog,"/var/log/%HOSTNAME%/messages"
	. -?PerHostLog		. -?PerHostLog

Sstrutt: /* Syslog to MySQL Database */ Added Syslog server setup

2014-01-03T15:18:48Z

Syslog to MySQL Database: Added Syslog server setup

@@ Line 195: / Line 195: @@
 </source>
-= Syslog to MySQL Database =
+= Syslog =
 This procedure achieves three things...
 # Allows remote hosts to use the local server as a syslog destination

Sstrutt: /* Firewall */ Added link to Troubleshooting

2012-10-11T21:09:23Z

Firewall: Added link to Troubleshooting

← Older revision		Revision as of 21:09, 11 October 2012
Line 34:		Line 34:

	= Firewall =		= Firewall =
			'''See also [[Troubleshooting_(Ubuntu)#Firewall\|Troubleshooting > Firewall]]'''

	Ubuntu comes with UFW (Uncomplicated Firewall), which is a config tool used to modify the standard inbuilt Netfilter. If preferred, <code>iptables</code> can still be used, both <code>ufw</code> and <code>iptables</code> are essentially config tools for Netfilter.		Ubuntu comes with UFW (Uncomplicated Firewall), which is a config tool used to modify the standard inbuilt Netfilter. If preferred, <code>iptables</code> can still be used, both <code>ufw</code> and <code>iptables</code> are essentially config tools for Netfilter.

Sstrutt: /* Firewall */ Added NTP example

2012-10-10T15:44:11Z

Firewall: Added NTP example

← Older revision		Revision as of 15:44, 10 October 2012
Line 53:		Line 53:
	\|-		\|-
	\| <code> ufw allow proto tcp from 192.168.1.10 to any port 22 </code> \|\| Allow TCP 22 (SSH) from 192.168.1.10		\| <code> ufw allow proto tcp from 192.168.1.10 to any port 22 </code> \|\| Allow TCP 22 (SSH) from 192.168.1.10
			\|-
			\| <code> ufw allow proto udp from any to any port 123 </code> \|\| Allow UDP 123 (NTP) from any host
	\|-		\|-
	\| <code> ufw delete 2 </code> \|\| Delete rule 2		\| <code> ufw delete 2 </code> \|\| Delete rule 2
Line 63:		Line 65:

	Be aware that '''rules are processed in order''', despite the fact that there is no easy way to alter the order of your rules using <code>ufw</code> or insert rules above existing ones. Therefore you need to think about the order of your rules carefully.		Be aware that '''rules are processed in order''', despite the fact that there is no easy way to alter the order of your rules using <code>ufw</code> or insert rules above existing ones. Therefore you need to think about the order of your rules carefully.

			See [[TCP UDP Ports]] for further info on common ports.

	=== Deny a Specific Host ===		=== Deny a Specific Host ===

Sstrutt: /* Firewall */ Added "Deny a Specific Host"

2012-10-05T08:31:54Z

Firewall: Added "Deny a Specific Host"

@@ Line 34: / Line 34: @@
 = Firewall =
-Ubuntu comes with UFW (Uncomplicated Firewall), which is a config tool used to modify the standard inbuilt Netfilter.  If preferred, iptables can still be used.
+Ubuntu comes with UFW (Uncomplicated Firewall), which is a config tool used to modify the standard inbuilt Netfilter.  If preferred, <code>iptables</code> can still be used, both <code>ufw</code> and <code>iptables</code> are essentially config tools for Netfilter.
 Changes are applied immediately. Once you've added your first rule there's an implied deny all.
@@ Line 62: / Line 62: @@
   ufw enable
 = SNMP =