Enabling IP routing - Revision history

Benrwong: /* on the nodes */

2018-12-05T02:19:14Z

on the nodes

← Older revision		Revision as of 02:19, 5 December 2018
Line 33:		Line 33:
	mkdir -pv /mnt/sali/diva2		mkdir -pv /mnt/sali/diva2
	route add 169.230.79.14 gw 10.0.1.157		route add 169.230.79.14 gw 10.0.1.157

			===For CentOS 7.5.1804===
			Temporary:
			# route add default gw <IP Address of machine that will route>

	===For Ubuntu 16.04===		===For Ubuntu 16.04===

Benrwong: added section for Ubuntu 16.04 client of IP routing

2018-11-02T19:50:35Z

added section for Ubuntu 16.04 client of IP routing

← Older revision		Revision as of 19:50, 2 November 2018
Line 34:		Line 34:
	route add 169.230.79.14 gw 10.0.1.157		route add 169.230.79.14 gw 10.0.1.157

			===For Ubuntu 16.04===
			Our Ubuntu 16.04 server had no public IP address but needed public network connectivity. This server got its network configuration from our DHCP server but the DHCP server config did not include routes. To have a permanent routing configuration even after network/system restarts for this DHCP client, we must edit the dhclient configurations to maintain a route through our other host, epsilon. To do this: <br />
			1. Edit /etc/dhcp/dhclient.conf <br />
			2. Add the following line to the bottom of the configuration file:
			supersede routers <ip address of routing machine>;

			Example: We use epsilon as our routing machine. The private IP address of epsilon is 10.20.1.5 so the resulting dhclient.conf for the client would look like:
			supersede routers 10.20.1.5;


	[[Category:Sysadmin]]		[[Category:Sysadmin]]

Benrwong: /* Alternative method: */ removed typo

2018-08-28T23:46:09Z

Alternative method:: removed typo

← Older revision		Revision as of 23:46, 28 August 2018
Line 22:		Line 22:
	:POSTROUTING ACCEPT [0:0]		:POSTROUTING ACCEPT [0:0]
	-A POSTROUTING -o <name of interface to route traffic out of> -j MASQUERADE		-A POSTROUTING -o <name of interface to route traffic out of> -j MASQUERADE
	COMMIT:		COMMIT

	4. # NAT forwarding		4. # NAT forwarding

Benrwong: /* Alternative method: */

2018-08-28T23:45:53Z

Alternative method:

← Older revision		Revision as of 23:45, 28 August 2018
Line 19:		Line 19:

	3. # enable post route		3. # enable post route
			*nat
			:POSTROUTING ACCEPT [0:0]
	-A POSTROUTING -o <name of interface to route traffic out of> -j MASQUERADE		-A POSTROUTING -o <name of interface to route traffic out of> -j MASQUERADE
			COMMIT:

	4. # NAT forwarding		4. # NAT forwarding

Benrwong: /* Alternative method: */

2018-08-28T23:22:43Z

Alternative method:

← Older revision		Revision as of 23:22, 28 August 2018
Line 16:		Line 16:

	==Alternative method:==		==Alternative method:==
	Same as steps 1 & 2 above. However, in step 3 & 4:		Ben: Same as steps 1 & 2 above. However, in step 3 & 4:

	3. # enable post route		3. # enable post route

	-A POSTROUTING -o <name of interface to route traffic out of> -j MASQUERADE		-A POSTROUTING -o <name of interface to route traffic out of> -j MASQUERADE

	4. # NAT forwarding		4. # NAT forwarding

Benrwong at 17:28, 20 April 2018

2018-04-20T17:28:17Z

← Older revision		Revision as of 17:28, 20 April 2018
Line 8:		Line 8:
	-A POSTROUTING -o bond0.100 -j MASQUERADE		-A POSTROUTING -o bond0.100 -j MASQUERADE
	COMMIT		COMMIT

	* 4. Add the following to the end of `/etc/sysconfig/iptables` (before `-A FORWARD -j REJECT --reject-with icmp-host-prohibited`)		* 4. Add the following to the end of `/etc/sysconfig/iptables` (before `-A FORWARD -j REJECT --reject-with icmp-host-prohibited`)

Line 16:		Line 15:
	5. Restart iptables: `service iptables restart`		5. Restart iptables: `service iptables restart`

	Alternative method:		==Alternative method:==
	Same as steps 1 & 2 above. However, in step 3 & 4:		Same as steps 1 & 2 above. However, in step 3 & 4:

	3. # enable post route		3. # enable post route

	-A POSTROUTING -o <name of interface to route traffic out of> -j MASQUERADE		-A POSTROUTING -o <name of interface to route traffic out of> -j MASQUERADE

	4. # NAT forwarding		4. # NAT forwarding
	-A FORWARD -i <input interface> -o <output interface> -j ACCEPT		-A FORWARD -i <input interface> -o <output interface> -j ACCEPT
	-A FORWARD -i <output interface> -o <input interface> -m state --state RELATED,ESTABLISHED -j ACCEPT		-A FORWARD -i <output interface> -o <input interface> -m state --state RELATED,ESTABLISHED -j ACCEPT
			5. Restart iptables with 'service iptables restart'

	= on the nodes =		= on the nodes =

Benrwong: added alternative NAT/postrouting method

2018-04-20T17:27:19Z

added alternative NAT/postrouting method

← Older revision		Revision as of 17:27, 20 April 2018
Line 15:		Line 15:

	5. Restart iptables: `service iptables restart`		5. Restart iptables: `service iptables restart`

			Alternative method:
			Same as steps 1 & 2 above. However, in step 3 & 4:

			3. # enable post route
			-A POSTROUTING -o <name of interface to route traffic out of> -j MASQUERADE

			4. # NAT forwarding
			-A FORWARD -i <input interface> -o <output interface> -j ACCEPT
			-A FORWARD -i <output interface> -o <input interface> -m state --state RELATED,ESTABLISHED -j ACCEPT

	= on the nodes =		= on the nodes =

Frodo at 21:28, 17 June 2014

2014-06-17T21:28:51Z

← Older revision		Revision as of 21:28, 17 June 2014
Line 16:		Line 16:
	5. Restart iptables: `service iptables restart`		5. Restart iptables: `service iptables restart`

			= on the nodes =
			echo "169.230.79.14:/diva2 /mnt/sali/diva2 nfs ro,noatime,tcp,intr 0 0" >> /etc/fstab
			mkdir -pv /mnt/sali/diva2
			route add 169.230.79.14 gw 10.0.1.157

	[[Category:Sysadmin]]		[[Category:Sysadmin]]

Frodo: Created page with "Say a cluster exports a disk to one machine, and you want to make that disk available to all machines in your cluster. Basically, you want to use that one machine as a router...."

2014-06-17T21:03:39Z

Created page with "Say a cluster exports a disk to one machine, and you want to make that disk available to all machines in your cluster. Basically, you want to use that one machine as a router...."

New page

Say a cluster exports a disk to one machine, and you want to make that disk available to all machines in your cluster. Basically, you want to use that one machine as a router. Here is how to do it:

* 1. Change `net.ipv4.ip_forward = 0` to `net.ipv4.ip_forward = 1` in `/etc/sysctl.conf
* 2. Also run `sysctl -w net.ipv4.ip_forward=1` to avoid restarting.
* 3. Add the following at the top of `/etc/sysconfig/iptables` (before `*filter`)
*nat
-A POSTROUTING -o bond0.100 -j MASQUERADE
COMMIT

* 4. Add the following to the end of `/etc/sysconfig/iptables` (before `-A FORWARD -j REJECT --reject-with icmp-host-prohibited`)

-A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
-A FORWARD -m state --state NEW -i bond0.101 -d 169.230.79.14 -j ACCEPT

5. Restart iptables: `service iptables restart`

[[Category:Sysadmin]]