Fault Tolerant Routing with Alpine Linux - Revision history

Sertonix: use relative symlinks

2023-11-17T10:23:46Z

use relative symlinks

← Older revision		Revision as of 10:23, 17 November 2023
Line 69:		Line 69:
	* Copy the scripts for each the interface:		* Copy the scripts for each the interface:
	{{Cmd\|apk add ucarp		{{Cmd\|apk add ucarp
	ln -s ~~/etc/init.d/~~ucarp /etc/init.d/ucarp.eth0		ln -s ucarp /etc/init.d/ucarp.eth0
	ln -s ~~/etc/init.d/~~ucarp /etc/init.d/ucarp.eth1		ln -s ucarp /etc/init.d/ucarp.eth1
	ln -s ~~/etc/init.d/~~ucarp /etc/init.d/ucarp.eth2.2		ln -s ucarp /etc/init.d/ucarp.eth2.2
	ln -s ~~/etc/init.d/~~ucarp /etc/init.d/ucarp.eth2.3		ln -s ucarp /etc/init.d/ucarp.eth2.3
	cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth0		cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth0
	cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth1		cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth1

Sertonix: replace /etc/init.d with rc-service

2023-11-17T10:23:25Z

replace /etc/init.d with rc-service

← Older revision		Revision as of 10:23, 17 November 2023
Line 118:		Line 118:
	rc-update add ucarp.eth2.2		rc-update add ucarp.eth2.2
	rc-update add ucarp.eth2.3		rc-update add ucarp.eth2.3
	~~/etc/init.d/~~ucarp.eth0 start		rc-service ucarp.eth0 start
	~~/etc/init.d/~~ucarp.eth1 start		rc-service ucarp.eth1 start
	~~/etc/init.d/~~ucarp.eth2.2 start		rc-service ucarp.eth2.2 start
	~~/etc/init.d/~~ucarp.eth2.3 start		rc-service ucarp.eth2.3 start
	lbu commit}}		lbu commit}}
	* Do the above steps for each router		* Do the above steps for each router

Zcrayfish: /* Start ip forwarding */ Fixed dead link.

2023-08-25T14:48:55Z

Start ip forwarding: Fixed dead link.

← Older revision		Revision as of 14:48, 25 August 2023
Line 57:		Line 57:
	{{Cmd\|echo 1 > /proc/sys/net/ipv4/ip_forward}}		{{Cmd\|echo 1 > /proc/sys/net/ipv4/ip_forward}}

	If you follow the ucarp section below, you'll also need to disable rp_filter (RFC3704 Ingress Filtering). Since this how-to is designed for an internal router this should (or might not) be acceptable. Available options for this setting can be viewed at ~~http~~://~~git~~.kernel.org/~~?p=linux~~/~~kernel/git/torvalds/linux-2.6.git;a=blob;f=~~Documentation/networking/ip-sysctl.txt~~;hb=HEAD#l855.~~		If you follow the ucarp section below, you'll also need to disable rp_filter (RFC3704 Ingress Filtering). Since this how-to is designed for an internal router this should (or might not) be acceptable. Available options for this setting can be viewed at https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt
	{{Cmd\|echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter		{{Cmd\|echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
	echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter		echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter

Bt129 at 10:06, 26 July 2021

2021-07-26T10:06:41Z

← Older revision		Revision as of 10:06, 26 July 2021
Line 1:		Line 1:
	This document ~~will explain~~ how to setup a fault-tolerant router using Alpine Linux. It has been tested ~~using~~ Alpine Linux 2.2.3.		This document explains how to setup a fault-tolerant router using Alpine Linux. It has been tested with Alpine Linux 2.2.3.
	== Hardware and Network Setup ==		== Hardware and Network Setup ==
	The network used in this example is as follows:		The network used in this example is as follows:
	* Will run (at least initially) IPv4		* Will run (at least initially) IPv4
	* Pre-existing border router that ~~NATs~~ from public IP(s) to the 10.0.0.0/8 network and has the address 10.0.0.1/24 on the transit network		* Pre-existing border router that performs NAT from public IP(s) to the 10.0.0.0/8 network and has the address 10.0.0.1/24 on the transit network
	* The border router will have a default route to the internal network via 10.0.0.2 (the virtual IP address of the routers being ~~setup~~ in this doc)		* The border router will have a default route to the internal network via 10.0.0.2 (the virtual IP address of the routers being set up in this doc)
	* A transit network between the border router and the fault-tolerant routers in this document will be on 10.0.0.0/24		* The transit network between the border router and the fault-tolerant routers described in this document, will be on 10.0.0.0/24
	* The routers will also connect several internal subnets on the network:		* The routers will also connect several internal subnets on the network:
	** 10.0.1.0/24		** 10.0.1.0/24
Line 11:		Line 11:
	** 10.0.3.0/24		** 10.0.3.0/24
	* It's assumed that 10.0.0.0/24 and 10.0.1.0/24 are connected via dedicated interfaces (eth0 and eth1, respectively), while 10.0.2.0/24 and 10.0.3.0/24 share an interface(eth2), but traffic is segregated using 802.1q vlan tagging, with 10.0.2.0/24 using vlan id 2, and 10.0.3.0/24 using vlan id 3.		* It's assumed that 10.0.0.0/24 and 10.0.1.0/24 are connected via dedicated interfaces (eth0 and eth1, respectively), while 10.0.2.0/24 and 10.0.3.0/24 share an interface(eth2), but traffic is segregated using 802.1q vlan tagging, with 10.0.2.0/24 using vlan id 2, and 10.0.3.0/24 using vlan id 3.
	* Finally, all computers in subnets 10.0.1.0/24, 10.0.2.0/24 and 10.0.3.0/24 are ~~setup~~ with a default gateway of 10.0.x.1		* Finally, all computers in subnets 10.0.1.0/24, 10.0.2.0/24 and 10.0.3.0/24 are set up with a default gateway of 10.0.x.1
	Two computers will be needed, with at three NICs in them (more if you are connecting more network segments together), ~~and they will~~ act as routers.		Two computers will be needed, with at least three NICs in them (more if you are connecting more network segments together), to act as routers.

	== Initial Setup ==		== Initial Setup ==
	First, [[Create a Bootable USB\|setup Alpine]] on a USB key or CF card on both computers. Connect both computers initially to 10.0.0.0/24 on eth0, and assign them ip addresses of 10.0.0.3/24 and 10.0.0.4/24 in the setup-alpine script(for router1 and router2, respectively). Do not configure other interfaces initially. Ensure that both machines are pingable.		First, [[Create a Bootable USB\|setup Alpine]] on a USB key or CF card on both computers. Connect both computers initially to 10.0.0.0/24 on eth0, and assign them ip addresses of 10.0.0.3/24 and 10.0.0.4/24 in the setup-alpine script(for router1 and router2, respectively). Do not configure other interfaces initially. Ensure that both machines are pingable.

	Next, connect them both to 10.0.1.0/24 on eth1, and assign them ip addresses of 10.0.1.2/24 and 10.0.1.3/24, respectively. Ensure that they can also ping each other. /etc/network/interfaces (for router1) ~~at this point~~ should look like:		Next, connect them both to 10.0.1.0/24 on eth1, and assign them ip addresses of 10.0.1.2/24 and 10.0.1.3/24, respectively. Ensure that they can also ping each other. At this point, /etc/network/interfaces (for router1) should look like this:
	auto eth0		auto eth0
	iface eth0 inet static		iface eth0 inet static
Line 28:		Line 28:
	netmask 255.255.255.0		netmask 255.255.255.0

	Finally, get the last two networks connected (the ip addresses given are for router1~~, and these~~ steps should be performed on router2 ~~as well~~):		Finally, get the last two networks connected (the ip addresses given are for router1. The following steps should be performed on router2):
	modprobe 8021q		modprobe 8021q
	echo "8021q" >> /etc/modules		echo "8021q" >> /etc/modules
Line 51:		Line 51:
	post-down vconfig rem $IFACE		post-down vconfig rem $IFACE
	EOF		EOF
	Test that you can also ping between ~~these~~ interfaces.		Test that you can also ping between the two interfaces.

	=== Start ip forwarding ===		=== Start ip forwarding ===
	Next, turn them into simple routers by enabling ip forwarding (do ~~this~~ on each box):		Next, turn them into simple routers by enabling ip forwarding (do that on each box):
	{{Cmd\|echo 1 > /proc/sys/net/ipv4/ip_forward}}		{{Cmd\|echo 1 > /proc/sys/net/ipv4/ip_forward}}

	If you follow the ucarp section below, you'll also need to disable rp_filter (RFC3704 Ingress Filtering). Since this ~~howto~~ is designed for an internal router this should (or might not) be acceptable. Available options for this setting can be viewed at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/networking/ip-sysctl.txt;hb=HEAD#l855.		If you follow the ucarp section below, you'll also need to disable rp_filter (RFC3704 Ingress Filtering). Since this how-to is designed for an internal router this should (or might not) be acceptable. Available options for this setting can be viewed at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/networking/ip-sysctl.txt;hb=HEAD#l855.
	{{Cmd\|echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter		{{Cmd\|echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
	echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter		echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter
Line 129:		Line 129:
	== Install and configure Shorewall iptables frontend ==		== Install and configure Shorewall iptables frontend ==

	We will ~~name our~~ Shorewall zones by letters to keep the config files simple~~, and they~~ will correspond to subnets and interfaces as follows:		We will refer to the Shorewall zones by letters to keep the config files simple. They will correspond to subnets and interfaces as follows:
	A = eth0 = 10.0.0.0/24		A = eth0 = 10.0.0.0/24
	B = eth1 = 10.0.1.0/24		B = eth1 = 10.0.1.0/24
Line 158:		Line 158:
	C_3 ipv4		C_3 ipv4
	#LAST LINE - ADD YOUR ENTRIES ABOVE THIS ONCE - DO NOT REMOVE		#LAST LINE - ADD YOUR ENTRIES ABOVE THIS ONCE - DO NOT REMOVE
	Edit /etc/shorewall/policy: (note: this allows all traffic between internal subnets and all traffic outbound ~~towards~~ the Internet, but blocks all traffic inbound by default, this policy might need to be adjusted in your case)		Edit /etc/shorewall/policy: (note: this allows all traffic between internal subnets and all traffic outbound to the Internet, but blocks all traffic inbound by default, this policy might need to be adjusted in your case)
	#FIRST LINE		#FIRST LINE
	A all REJECT INFO		A all REJECT INFO
Line 172:		Line 172:
	all all REJECT INFO		all all REJECT INFO
	#LAST LINE - ADD YOUR ENTRIES ABOVE THIS ONCE - DO NOT REMOVE		#LAST LINE - ADD YOUR ENTRIES ABOVE THIS ONCE - DO NOT REMOVE
	Edit /etc/shorewall/rules: (the following simply ~~allow~~ SSH traffic in to your two routers - more will probably be needed to accept or reject traffic based on your needs)		Edit /etc/shorewall/rules: (the following simply allows SSH traffic in to your two routers - more will probably be needed to accept or reject traffic based on your needs)
	#FIRST LINE		#FIRST LINE
	ACCEPT A fw tcp 22		ACCEPT A fw tcp 22
Line 190:		Line 190:
	shorewall restart}}		shorewall restart}}

	{{Tip\|This gives you a basic set of redundant policy routers, however you can continue on with section(s) below to add features to them}}		{{Tip\|This gives you a basic set of redundant policy routers, however you can continue with section(s) below to add features to them}}

	== DHCP Relaying ==		== DHCP Relaying ==

	This will allow DHCP broadcasts from one subnet to be sent on to a DHCP server in another subnet (so that ~~you don't have to have~~ your DHCP server ~~have~~ an interface in each subnet).		This will allow DHCP broadcasts from one subnet to be sent on to a DHCP server in another subnet (that way your DHCP server won't need an interface in each subnet).

	First, install dhcrelay:		First, install dhcrelay:
Line 201:		Line 201:
	IFACE="eth1 eth2.2 eth2.3"		IFACE="eth1 eth2.2 eth2.3"
	DHCRELAY_SERVERS="10.0.1.100 10.0.1.101"		DHCRELAY_SERVERS="10.0.1.100 10.0.1.101"
	Finally, ~~setup~~ your scopes on 10.0.1.100 and 10.0.1.101 for the 10.0.1.0/24, 10.0.2.0/24, and 10.0.3.0/24 subnets and test by requesting a lease from a computer in either 10.0.2.0/24 or 10.0.3.0/24.		Finally, set up your scopes on 10.0.1.100 and 10.0.1.101 for the 10.0.1.0/24, 10.0.2.0/24, and 10.0.3.0/24 subnets and test by requesting a lease from a computer in either 10.0.2.0/24 or 10.0.3.0/24.

	[[Category:Networking]]		[[Category:Networking]]

Dubiousjim: update links

2012-10-20T14:30:24Z

update links

← Older revision		Revision as of 14:30, 20 October 2012
Line 15:		Line 15:

	== Initial Setup ==		== Initial Setup ==
	First, [[~~Installing Alpine on~~ USB \| setup]] ~~Alpine~~ on a USB key or CF card on both computers. Connect both computers initially to 10.0.0.0/24 on eth0, and assign them ip addresses of 10.0.0.3/24 and 10.0.0.4/24 in the setup-alpine script(for router1 and router2, respectively). Do not configure other interfaces initially. Ensure that both machines are pingable.		First, [[Create a Bootable USB\|setup Alpine]] on a USB key or CF card on both computers. Connect both computers initially to 10.0.0.0/24 on eth0, and assign them ip addresses of 10.0.0.3/24 and 10.0.0.4/24 in the setup-alpine script(for router1 and router2, respectively). Do not configure other interfaces initially. Ensure that both machines are pingable.

	Next, connect them both to 10.0.1.0/24 on eth1, and assign them ip addresses of 10.0.1.2/24 and 10.0.1.3/24, respectively. Ensure that they can also ping each other. /etc/network/interfaces (for router1) at this point should look like:		Next, connect them both to 10.0.1.0/24 on eth1, and assign them ip addresses of 10.0.1.2/24 and 10.0.1.3/24, respectively. Ensure that they can also ping each other. /etc/network/interfaces (for router1) at this point should look like:

Jbilyk: tested with 2.2.3 now

2011-10-31T07:28:35Z

tested with 2.2.3 now

← Older revision		Revision as of 07:28, 31 October 2011
Line 1:		Line 1:
	This document will explain how to setup a fault-tolerant router using Alpine Linux. It has been tested using Alpine Linux 2.2.2.		This document will explain how to setup a fault-tolerant router using Alpine Linux. It has been tested using Alpine Linux 2.2.3.
	== Hardware and Network Setup ==		== Hardware and Network Setup ==
	The network used in this example is as follows:		The network used in this example is as follows:

Jbilyk: remove draft

2011-07-20T10:46:01Z

remove draft

← Older revision		Revision as of 10:46, 20 July 2011
Line 1:		Line 1:
	~~{{Draft}}~~
	This document will explain how to setup a fault-tolerant router using Alpine Linux. It has been tested using Alpine Linux 2.2.2.		This document will explain how to setup a fault-tolerant router using Alpine Linux. It has been tested using Alpine Linux 2.2.2.
	== Hardware and Network Setup ==		== Hardware and Network Setup ==

Jbilyk: High Performance and Fault Tolerant Routing with Alpine Linux moved to Fault Tolerant Routing with Alpine Linux: this setup isn't actually High Performance

2011-07-20T10:44:13Z

High Performance and Fault Tolerant Routing with Alpine Linux moved to Fault Tolerant Routing with Alpine Linux: this setup isn't actually High Performance

← Older revision	Revision as of 10:44, 20 July 2011
(No difference)

Jbilyk: spacing fixes

2011-07-19T19:24:29Z

spacing fixes

Jbilyk: use cmd template

2011-07-19T19:23:00Z

use cmd template

← Older revision		Revision as of 19:23, 19 July 2011
Line 56:		Line 56:
	=== Start ip forwarding ===		=== Start ip forwarding ===
	Next, turn them into simple routers by enabling ip forwarding (do this on each box):		Next, turn them into simple routers by enabling ip forwarding (do this on each box):
	echo 1 > /proc/sys/net/ipv4/ip_forward		{{Cmd\|echo 1 > /proc/sys/net/ipv4/ip_forward}}

	If you follow the ucarp section below, you'll also need to disable rp_filter (RFC3704 Ingress Filtering). Since this howto is designed for an internal router this should (or might not) be acceptable. Available options for this setting can be viewed at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/networking/ip-sysctl.txt;hb=HEAD#l855.		If you follow the ucarp section below, you'll also need to disable rp_filter (RFC3704 Ingress Filtering). Since this howto is designed for an internal router this should (or might not) be acceptable. Available options for this setting can be viewed at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/networking/ip-sysctl.txt;hb=HEAD#l855.
	echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter		{{Cmd\|echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
	echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter		echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter
	echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter		echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter
	echo 0 > /proc/sys/net/ipv4/conf/eth2.2/rp_filter		echo 0 > /proc/sys/net/ipv4/conf/eth2.2/rp_filter
	echo 0 > /proc/sys/net/ipv4/conf/eth2.3/rp_filter		echo 0 > /proc/sys/net/ipv4/conf/eth2.3/rp_filter}}

	== Install and start ucarp ==		== Install and start ucarp ==
Line 69:		Line 69:

	* Copy the scripts for each the interface:		* Copy the scripts for each the interface:
	apk add ucarp		{{Cmd\|apk add ucarp
	ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth0		ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth0
	ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth1		ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth1
Line 77:		Line 77:
	cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth1		cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth1
	cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth2.2		cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth2.2
	cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth2.3		cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth2.3}}
	* edit the /etc/conf/ucarp.eth0 file:		* edit the /etc/conf/ucarp.eth0 file:
	REALIP=		REALIP=
Line 113:		Line 113:
	for a in 550 440 330; do beep -f $a -l 100; done		for a in 550 440 330; do beep -f $a -l 100; done
	* Make the scripts executable		* Make the scripts executable
	chmod +x /etc/ucarp/*.sh		{{Cmd\|chmod +x /etc/ucarp/*.sh}}
	* Start ucarp and save the changes		* Start ucarp and save the changes
	rc-update add ucarp.eth0		{{Cmd\|rc-update add ucarp.eth0
	rc-update add ucarp.eth1		rc-update add ucarp.eth1
	rc-update add ucarp.eth2.2		rc-update add ucarp.eth2.2
	rc-update add ucarp.eth2.3		rc-update add ucarp.eth2.3
	/etc/init.d/ucarp.eth0 start		/etc/init.d/ucarp.eth0 start
	/etc/init.d/ucarp.eth1 start		/etc/init.d/ucarp.eth1 start
	/etc/init.d/ucarp.eth2.2 start		/etc/init.d/ucarp.eth2.2 start
	/etc/init.d/ucarp.eth2.3 start		/etc/init.d/ucarp.eth2.3 start
	lbu commit		lbu commit}}
	* Do the above steps for each router		* Do the above steps for each router

Line 136:		Line 136:
	C_3 = eth2.3 = 10.0.3.0/24		C_3 = eth2.3 = 10.0.3.0/24
	Install the needed package		Install the needed package
	apk add shorewall		{{Cmd\|apk add shorewall}}
	Edit /etc/shorewall/params:		Edit /etc/shorewall/params:
	#FIRST LINE		#FIRST LINE
Line 188:		Line 188:
	STARTUP_ENABLED=yes		STARTUP_ENABLED=yes
	Check config for errors then start shorewall:		Check config for errors then start shorewall:
	shorewall check		{{Cmd\|shorewall check
	shorewall restart		shorewall restart}}

	{{Tip\|This gives you a basic set of redundant policy routers, however you can continue on with section(s) below to add features to them}}		{{Tip\|This gives you a basic set of redundant policy routers, however you can continue on with section(s) below to add features to them}}
Line 198:		Line 198:

	First, install dhcrelay:		First, install dhcrelay:
	apk add dhcrelay		{{Cmd\|apk add dhcrelay}}
	Next, adjust /etc/conf.d/dhcrelay: (assuming you don't need DHCP on the 10.0.0.0/24 subnet, and that your DHCP servers are 10.0.1.100 and 10.0.1.101)		Next, adjust /etc/conf.d/dhcrelay: (assuming you don't need DHCP on the 10.0.0.0/24 subnet, and that your DHCP servers are 10.0.1.100 and 10.0.1.101)
	IFACE="eth1 eth2.2 eth2.3"		IFACE="eth1 eth2.2 eth2.3"

← Older revision		Revision as of 19:24, 19 July 2011
Line 60:		Line 60:
	If you follow the ucarp section below, you'll also need to disable rp_filter (RFC3704 Ingress Filtering). Since this howto is designed for an internal router this should (or might not) be acceptable. Available options for this setting can be viewed at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/networking/ip-sysctl.txt;hb=HEAD#l855.		If you follow the ucarp section below, you'll also need to disable rp_filter (RFC3704 Ingress Filtering). Since this howto is designed for an internal router this should (or might not) be acceptable. Available options for this setting can be viewed at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/networking/ip-sysctl.txt;hb=HEAD#l855.
	{{Cmd\|echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter		{{Cmd\|echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
	echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter		echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter
	echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter		echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter
	echo 0 > /proc/sys/net/ipv4/conf/eth2.2/rp_filter		echo 0 > /proc/sys/net/ipv4/conf/eth2.2/rp_filter
	echo 0 > /proc/sys/net/ipv4/conf/eth2.3/rp_filter}}		echo 0 > /proc/sys/net/ipv4/conf/eth2.3/rp_filter}}

	== Install and start ucarp ==		== Install and start ucarp ==
Line 70:		Line 70:
	* Copy the scripts for each the interface:		* Copy the scripts for each the interface:
	{{Cmd\|apk add ucarp		{{Cmd\|apk add ucarp
	ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth0		ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth0
	ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth1		ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth1
	ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth2.2		ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth2.2
	ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth2.3		ln -s /etc/init.d/ucarp /etc/init.d/ucarp.eth2.3
	cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth0		cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth0
	cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth1		cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth1
	cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth2.2		cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth2.2
	cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth2.3}}		cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth2.3}}
	* edit the /etc/conf/ucarp.eth0 file:		* edit the /etc/conf/ucarp.eth0 file:
	REALIP=		REALIP=
Line 189:		Line 189:
	Check config for errors then start shorewall:		Check config for errors then start shorewall:
	{{Cmd\|shorewall check		{{Cmd\|shorewall check
	shorewall restart}}		shorewall restart}}

	{{Tip\|This gives you a basic set of redundant policy routers, however you can continue on with section(s) below to add features to them}}		{{Tip\|This gives you a basic set of redundant policy routers, however you can continue on with section(s) below to add features to them}}