CipherSpace Virtual Router - Revision history

Stoyan at 06:49, 10 May 2017

2017-05-10T06:49:48Z

← Older revision		Revision as of 06:49, 10 May 2017
Line 3:		Line 3:
	[[Category:CloudInfrastructure]]		[[Category:CloudInfrastructure]]

	'''CipherSpace Virtual Router''' ~~is based on '''OpenNebula Virtual Router''' (http://docs.opennebula.org/4.8/administration/networking/router.html) with some modifications plus OpenVPN. It~~ is meant to be used as:		'''CipherSpace Virtual Router''' is meant to be used as:
	* Router (masquerade)		* Router (masquerade)
	* DHCP server		* DHCP server
Line 70:		Line 70:
	openssl passwd -1 \| base64		openssl passwd -1 \| base64

	* '''SSH_PUBLIC_KEY''' - single line, base64 encoded list of SSH keys to be set as '''root's authorized_keys'''. That is the '''Public key''' field in '''Context'''->'''Network & SSH'''. This is not a custom field. The way scripts are implemented they cannot parse parameters which contain 'new line' character. Because of that CipherSpace Virtual Router expects the value of SSH_PUBLIC_KEY to be a single base64 encoded string. That way we can pass multiple SSH keys. To generate the string you can use command like this:		* '''SSH_PUBLIC_KEY''' - single line, base64 encoded list of SSH keys to be set as '''root's authorized_keys'''. That is the '''Public key''' field in '''Context'''->'''Network & SSH'''. This is not a custom field. To generate the string you can use command like this:
	cat <pub_key1> <pub_key2> ... <pub_keyN> \| base64 \| paste -s -d '\0' -		cat <pub_key1> <pub_key2> ... <pub_keyN> \| base64 \| paste -s -d '\0' -

	* '''SSHD''' - if set to YES and SSH_PUBLIC_KEY is set, then sshd will be launched. The idea is that Virtual Router VMs will not need active maintenance thus sshd does not need to be on all the time. If SSH_PUBLIC_KEY is set keys will be installed for root regardless of whether SSHD is enabled or not. That way one can login on the console and launch sshd if required. Command ~~for Apline Linux~~ is:		* '''SSHD''' - if set to YES and SSH_PUBLIC_KEY is set, then sshd will be launched. The idea is that Virtual Router VMs will not need active maintenance thus sshd does not need to be on all the time. If SSH_PUBLIC_KEY is set keys will be installed for root regardless of whether SSHD is enabled or not. That way one can login on the console and launch sshd if required. Command is:
	rc-service sshd start		rc-service sshd start

Line 84:		Line 84:
	* '''OPENVPN_SERVER_KEY''' - single line, PEM formatted, base64 encoded, server key		* '''OPENVPN_SERVER_KEY''' - single line, PEM formatted, base64 encoded, server key

	* '''OPENVPN_TA_KEY''' - optional but '''highly recommended''', single line, PEM formatted, base64 encoded, ~~preshared~~ key to use with '''--tls-auth'''. This features adds "extra protection" to the TLS channel by requiring that incoming packets have a valid signature generated using the ~~PSK~~ key. '''Key must be set on both server and client.''' If this key is ever changed, it must be changed on all peers at the same time.		* '''OPENVPN_TA_KEY''' - optional but '''highly recommended''', single line, PEM formatted, base64 encoded, pre-shared key to use with '''--tls-auth'''. This features adds "extra protection" to the TLS channel by requiring that incoming packets have a valid signature generated using the pre-shared key. '''Key must be set on both server and client.''' If this key is ever changed, it must be changed on all peers at the same time.

	* '''OPENVPN_REVOKED''' - optional, single line, base64 encoded content of a file containing revoked certificates.		* '''OPENVPN_REVOKED''' - optional, single line, base64 encoded content of a file containing revoked certificates.

	* '''OPENVPN_INT_NET''' - Network to be used for communication between the server and the clients. It has to be different from the internal OpenNebula network and client's network. Is omitted it default to 10.255.255.0. It is good idea to use different networks especially in ~~one~~ client setup. That way one can have multiple tunnels at the same time if destination networks don't overlap of course.		* '''OPENVPN_INT_NET''' - Network to be used for communication between the server and the clients. It has to be different from the internal OpenNebula network and client's network. Is omitted it default to 10.255.255.0. OpenVPN allows user to maintain more than one tunnel at the same time. It is good idea to use different networks especially in the same client setup. That way one can have multiple tunnels opened at the same time if destination networks don't overlap of course.

	* '''OPENVPN_INT_NETMASK''' - Network mask for the network between the server and the clients. Defaults to 255.255.255.0. '''Warning:''' OpenVPN is very picky. It will complain and it will not start if netmask zeros out any bit from the network. For example: net 10.1.1.1 netmask 255.255.255.0 will not work. ~~One needs~~ to use: net 10.1.1.0 netmask 255.255.255.0		* '''OPENVPN_INT_NETMASK''' - Network mask for the network between the server and the clients. Defaults to 255.255.255.0. '''Warning:''' OpenVPN is very picky. It will complain and it will not start if netmask zeros out any bit from the network. For example: net 10.1.1.1 netmask 255.255.255.0 will not work. You need to use: net 10.1.1.0 netmask 255.255.255.0

	* '''OPENVPN_MAX_CLIENTS''' - Maximum number of simultaneously connected users. It defaults to 3. Tests showed that is a good number for the default size VM.		* '''OPENVPN_MAX_CLIENTS''' - Maximum number of simultaneously connected users. It defaults to 3. Tests showed that is a good number for the default size VM.

Client Admin at 22:10, 20 March 2017

2017-03-20T22:10:55Z

← Older revision		Revision as of 22:10, 20 March 2017
Line 1:		Line 1:
	[[Category:OpenNebula]]		[[Category:OpenNebula]]
	[[Category:How To]]		[[Category:How To]]
	[[Category:~~Cloud Infrastructure~~]]		[[Category:CloudInfrastructure]]

	'''CipherSpace Virtual Router''' is based on '''OpenNebula Virtual Router''' (http://docs.opennebula.org/4.8/administration/networking/router.html) with some modifications plus OpenVPN. It is meant to be used as:		'''CipherSpace Virtual Router''' is based on '''OpenNebula Virtual Router''' (http://docs.opennebula.org/4.8/administration/networking/router.html) with some modifications plus OpenVPN. It is meant to be used as:

Client Admin at 22:09, 20 March 2017

2017-03-20T22:09:27Z

← Older revision		Revision as of 22:09, 20 March 2017
Line 1:		Line 1:
	[[Category:OpenNebula]]		[[Category:OpenNebula]]
	[[Category:How To]]		[[Category:How To]]
			[[Category:Cloud Infrastructure]]

	'''CipherSpace Virtual Router''' is based on '''OpenNebula Virtual Router''' (http://docs.opennebula.org/4.8/administration/networking/router.html) with some modifications plus OpenVPN. It is meant to be used as:		'''CipherSpace Virtual Router''' is based on '''OpenNebula Virtual Router''' (http://docs.opennebula.org/4.8/administration/networking/router.html) with some modifications plus OpenVPN. It is meant to be used as:

Stoyan at 09:26, 5 October 2016

2016-10-05T09:26:59Z

← Older revision		Revision as of 09:26, 5 October 2016
Line 1:		Line 1:
			[[Category:OpenNebula]]
			[[Category:How To]]

	'''CipherSpace Virtual Router''' is based on '''OpenNebula Virtual Router''' (http://docs.opennebula.org/4.8/administration/networking/router.html) with some modifications plus OpenVPN. It is meant to be used as:		'''CipherSpace Virtual Router''' is based on '''OpenNebula Virtual Router''' (http://docs.opennebula.org/4.8/administration/networking/router.html) with some modifications plus OpenVPN. It is meant to be used as:

Valentina at 13:06, 16 September 2016

2016-09-16T13:06:28Z

← Older revision		Revision as of 13:06, 16 September 2016
Line 20:		Line 20:
	<span style="color: red">'''When using DHCP or OpenVPN make sure IP spoofing and MAC spoofing protections are turned off for the internal network.'''</span> Otherwise it will not work.		<span style="color: red">'''When using DHCP or OpenVPN make sure IP spoofing and MAC spoofing protections are turned off for the internal network.'''</span> Otherwise it will not work.

	== ~~Contextualization Options~~ ==		== Virtual Router Configuration ==
			Following configurations can be added in the virtual router template in "Context" menu under "Custom Vars".

	~~Appliance~~ can be configured with 1 or 2 network interfaces. With 1 network interface it can be used only as '''DHCP''' or '''RADVD''' server.		The virtual router can be configured with 1 or 2 network interfaces. With 1 network interface it can be used only as '''DHCP''' or '''RADVD''' server.

	* '''TEMPLATE''' - this is '''required'''. Otherwise most of the other functionality will not work. Usage:		* '''TEMPLATE''' - this is '''required'''. Otherwise most of the other functionality will not work. Usage:

Valentina at 12:45, 16 September 2016

2016-09-16T12:45:21Z

← Older revision		Revision as of 12:45, 16 September 2016
Line 90:		Line 90:
	* '''OPENVPN_MAX_CLIENTS''' - Maximum number of simultaneously connected users. It defaults to 3. Tests showed that is a good number for the default size VM.		* '''OPENVPN_MAX_CLIENTS''' - Maximum number of simultaneously connected users. It defaults to 3. Tests showed that is a good number for the default size VM.

	~~Please follow [[OpenVPN Key Management]] guide to generate keys.~~

	CipherSpace Virtual Router can be used as a bastion host to build ssh tunnels. This is controlled by the following context variables:		CipherSpace Virtual Router can be used as a bastion host to build ssh tunnels. This is controlled by the following context variables:

Valentina at 12:38, 16 September 2016

2016-09-16T12:38:29Z

← Older revision		Revision as of 12:38, 16 September 2016
Line 19:		Line 19:

	<span style="color: red">'''When using DHCP or OpenVPN make sure IP spoofing and MAC spoofing protections are turned off for the internal network.'''</span> Otherwise it will not work.		<span style="color: red">'''When using DHCP or OpenVPN make sure IP spoofing and MAC spoofing protections are turned off for the internal network.'''</span> Otherwise it will not work.

			== Contextualization Options ==

			Appliance can be configured with 1 or 2 network interfaces. With 1 network interface it can be used only as '''DHCP''' or '''RADVD''' server.

			* '''TEMPLATE''' - this is '''required'''. Otherwise most of the other functionality will not work. Usage:
			TEMPLATE = "$TEMPLATE"

			* '''PRIVNET''' - private network. For example:
			PRIVNET = "$NETWORK[TEMPLATE, NETWORK=\"<private_network_name>\"]"

			* '''PUBNET''' - public network. For example:
			PUBNET = "$NETWORK[TEMPLATE, NETWORK=\"<public_network_name>\"]"

			* '''RADVD''' - enables or disabled RADVD server. Possible values are '''YES''' and '''NO'''. For example
			RADVD = "NO"

			* '''DHCP''' - enables or disabled DHCP server. Possible values are '''YES''' and '''NO'''. For example
			DHCP = "YES"

			* '''DNS''' - list of DNS servers to use in DHCP leases. If not specified DHCP server will use VMs private network IP address. For example:
			DNS = "10.1.1.1 10.2.2.2"

			* '''SEARCH''' - DNS search option. For example:
			SEARCH = "zh4.cipherspace.net"

			* '''NTP_SERVER''' - IP of the NTP server. The DHCP server will be configured to serve the NTP parameter to its leases. For example:
			NTP_SERVER = "10.0.0.10"

			* '''FORWARDING''' - list of forwarding rules separated by spaces. Syntax:
			[[protocol:]route_port:]destination:vm_port
			'''protocol''' is not validated but it only makes sense to use '''tcp''' or '''udp'''.Default is '''tcp'''. If '''router_port''' is omitted too then port '''vm_port''' on the router will be forwarded to '''vm_port''' on the VM. For example:
			FORWARDING = "udp:8888:10.0.0.10:53 8080:10.0.0.10:80 10.0.0.10:22"
			{\|
			\|style="text-align:right;"\|<code lang="text">udp:8888:10.0.0.10:53</code>
			\|style="padding-left: 15px"\|Forward UDP port 8888 on the router to port 53 on 10.0.0.10.
			\|-
			\|style="text-align:right;"\|<code lang="text">8080:10.0.0.10:80</code>
			\|style="padding-left: 15px"\|Forward TCP port 8080 on the router to port 80 on 10.0.0.10.
			\|-
			\|style="text-align:right;"\|<code lang="text">10.0.0.10:22</code>
			\|style="padding-left: 15px"\|Forward TCP port 22 the router to port 22 on 10.0.0.10.
			\|}

			* '''ROOT_PASSWORD''' - base64 encoded '''root''' password hash. For example one can use the following command:
			openssl passwd -1 \| base64

			* '''SSH_PUBLIC_KEY''' - single line, base64 encoded list of SSH keys to be set as '''root's authorized_keys'''. That is the '''Public key''' field in '''Context'''->'''Network & SSH'''. This is not a custom field. The way scripts are implemented they cannot parse parameters which contain 'new line' character. Because of that CipherSpace Virtual Router expects the value of SSH_PUBLIC_KEY to be a single base64 encoded string. That way we can pass multiple SSH keys. To generate the string you can use command like this:
			cat <pub_key1> <pub_key2> ... <pub_keyN> \| base64 \| paste -s -d '\0' -

			* '''SSHD''' - if set to YES and SSH_PUBLIC_KEY is set, then sshd will be launched. The idea is that Virtual Router VMs will not need active maintenance thus sshd does not need to be on all the time. If SSH_PUBLIC_KEY is set keys will be installed for root regardless of whether SSHD is enabled or not. That way one can login on the console and launch sshd if required. Command for Apline Linux is:
			rc-service sshd start

			* '''OPENVPN''' - controls whether OpenVPN should be started or not. If OPENVPN_CA_CERT, OPENVPN_SERVER_CERT and OPENVPN_SERVER_KEY are defined openvpn is configured but it is only launched if OPENVPN is set to YES. Please note that when image is instantiated and openvpn is configured it will take '''several minutes''', depending on allocated CPU, to boot because VM is generating DH 2048 bit parameters file.
			* '''OPENVPN_CA_CERT''' - single line, PEM formatted, base64 encoded, Certification Authority certificate. That is the certificate used to sign OPENVPN_SERVER_CERT and all client certificates. Use the following command to encode:
			cat ca.crt \| base64 \| paste -s -d '\0' -

			* '''OPENVPN_SERVER_CERT''' - single line, PEM formatted, base64 encoded, server certificate.

			* '''OPENVPN_SERVER_KEY''' - single line, PEM formatted, base64 encoded, server key

			* '''OPENVPN_TA_KEY''' - optional but '''highly recommended''', single line, PEM formatted, base64 encoded, preshared key to use with '''--tls-auth'''. This features adds "extra protection" to the TLS channel by requiring that incoming packets have a valid signature generated using the PSK key. '''Key must be set on both server and client.''' If this key is ever changed, it must be changed on all peers at the same time.

			* '''OPENVPN_REVOKED''' - optional, single line, base64 encoded content of a file containing revoked certificates.

			* '''OPENVPN_INT_NET''' - Network to be used for communication between the server and the clients. It has to be different from the internal OpenNebula network and client's network. Is omitted it default to 10.255.255.0. It is good idea to use different networks especially in one client setup. That way one can have multiple tunnels at the same time if destination networks don't overlap of course.

			* '''OPENVPN_INT_NETMASK''' - Network mask for the network between the server and the clients. Defaults to 255.255.255.0. '''Warning:''' OpenVPN is very picky. It will complain and it will not start if netmask zeros out any bit from the network. For example: net 10.1.1.1 netmask 255.255.255.0 will not work. One needs to use: net 10.1.1.0 netmask 255.255.255.0

			* '''OPENVPN_MAX_CLIENTS''' - Maximum number of simultaneously connected users. It defaults to 3. Tests showed that is a good number for the default size VM.

			Please follow [[OpenVPN Key Management]] guide to generate keys.

			CipherSpace Virtual Router can be used as a bastion host to build ssh tunnels. This is controlled by the following context variables:

			* '''TUNNEL_USER''' - user name. '''It must not exist.''' If user exists it will not be reconfigured. That is to prevent messing up system users. User shell is set to /bin/false.

			* '''TUNNEL_USER_SSH_PUBLIC_KEY''' - single line, base64 encoded, list of keys to install in '''authorized_keys''' file. Since it can can be multi-line it has to be formatted the same way as SSH_PUBLIC_KEY.

			* '''TUNNEL_USER_KEY_RESTRICTIONS''' - optional string that goes before the key in authorized_keys file. Defaults to '''"no-pty,no-agent-forwarding,no-X11-forwarding,no-user-rc"'''. Even though user shell is set to /bin/false one must be careful what goes in this variable.

Valentina at 11:12, 16 September 2016

2016-09-16T11:12:14Z

← Older revision		Revision as of 11:12, 16 September 2016
Line 1:		Line 1:
	~~[[Category:OpenNebula]]~~

	'''CipherSpace Virtual Router''' is based on '''OpenNebula Virtual Router''' (http://docs.opennebula.org/4.8/administration/networking/router.html) with some modifications plus OpenVPN. It is meant to be used as:		'''CipherSpace Virtual Router''' is based on '''OpenNebula Virtual Router''' (http://docs.opennebula.org/4.8/administration/networking/router.html) with some modifications plus OpenVPN. It is meant to be used as:

Valentina at 11:12, 16 September 2016

2016-09-16T11:12:05Z

← Older revision		Revision as of 11:12, 16 September 2016
Line 20:		Line 20:

	<span style="color: red">'''When using DHCP or OpenVPN make sure IP spoofing and MAC spoofing protections are turned off for the internal network.'''</span> Otherwise it will not work.		<span style="color: red">'''When using DHCP or OpenVPN make sure IP spoofing and MAC spoofing protections are turned off for the internal network.'''</span> Otherwise it will not work.

	~~== Contextualization Options ==~~

	~~The virtual router can be configured with 1 or 2 network interfaces. With 1 network interface it can be used only as '''DHCP''' or '''RADVD''' server.~~

	* '''TEMPLATE''' - this is '''required'''. Otherwise most of the other functionality will not work. Usage:
	~~TEMPLATE = "$TEMPLATE"~~

	* '''PRIVNET''' - private network. For example:
	~~PRIVNET = "$NETWORK[TEMPLATE, NETWORK=\"<private_network_name>\"]"~~

	* '''PUBNET''' - public network. For example:
	~~PUBNET = "$NETWORK[TEMPLATE, NETWORK=\"<public_network_name>\"]"~~

	* '''RADVD''' - enables or disabled RADVD server. Possible values are '''YES''' and '''NO'''. For example
	~~RADVD = "NO"~~

	* '''DHCP''' - enables or disabled DHCP server. Possible values are '''YES''' and '''NO'''. For example
	~~DHCP = "YES"~~

	* '''DNS''' - list of DNS servers to use in DHCP leases. If not specified DHCP server will use VMs private network IP address. For example:
	~~DNS = "10.1.1.1 10.2.2.2"~~

	* '''SEARCH''' - DNS search option. For example:
	~~SEARCH = "zh4.cipherspace.net"~~

	* '''NTP_SERVER''' - IP of the NTP server. The DHCP server will be configured to serve the NTP parameter to its leases. For example:
	~~NTP_SERVER = "10.0.0.10"~~

	* '''FORWARDING''' - list of forwarding rules separated by spaces. Syntax:
	~~[[protocol:]route_port:]destination:vm_port~~
	'''protocol''' is not validated but it only makes sense to use '''tcp''' or '''udp'''.Default is '''tcp'''. If '''router_port''' is omitted too then port '''vm_port''' on the router will be forwarded to '''vm_port''' on the VM. For example:
	~~FORWARDING = "udp:8888:10.0.0.10:53 8080:10.0.0.10:80 10.0.0.10:22"~~
	{\|
	~~\|style="text-align:right;"\|<code lang="text">udp:8888:10.0.0.10:53</code>~~
	~~\|style="padding-left: 15px"\|Forward UDP port 8888 on the router to port 53 on 10.0.0.10.~~
	\|-
	~~\|style="text-align:right;"\|<code lang="text">8080:10.0.0.10:80</code>~~
	~~\|style="padding-left: 15px"\|Forward TCP port 8080 on the router to port 80 on 10.0.0.10.~~
	\|-
	~~\|style="text-align:right;"\|<code lang="text">10.0.0.10:22</code>~~
	~~\|style="padding-left: 15px"\|Forward TCP port 22 the router to port 22 on 10.0.0.10.~~
	\|}

	* '''ROOT_PASSWORD''' - base64 encoded '''root''' password hash. For example one can use the following command:
	~~openssl passwd -1 \| base64~~

	* '''SSH_PUBLIC_KEY''' - single line, base64 encoded list of SSH keys to be set as '''root's authorized_keys'''. That is the '''Public key''' field in '''Context'''->'''Network & SSH'''. This is not a custom field. The way scripts are implemented they cannot parse parameters which contain 'new line' character. Because of that CipherSpace Virtual Router expects the value of SSH_PUBLIC_KEY to be a single base64 encoded string. That way we can pass multiple SSH keys. To generate the string you can use command like this:
	~~cat <pub_key1> <pub_key2> ... <pub_keyN> \| base64 \| paste -s -d '\0' -~~

	* '''SSHD''' - if set to YES and SSH_PUBLIC_KEY is set, then sshd will be launched. The idea is that Virtual Router VMs will not need active maintenance thus sshd does not need to be on all the time. If SSH_PUBLIC_KEY is set keys will be installed for root regardless of whether SSHD is enabled or not. That way one can login on the console and launch sshd if required. Command for Apline Linux is:
	~~rc-service sshd start~~

	* '''OPENVPN''' - controls whether OpenVPN should be started or not. If OPENVPN_CA_CERT, OPENVPN_SERVER_CERT and OPENVPN_SERVER_KEY are defined openvpn is configured but it is only launched if OPENVPN is set to YES. Please note that when image is instantiated and openvpn is configured it will take '''several minutes''', depending on allocated CPU, to boot because VM is generating DH 2048 bit parameters file.
	* '''OPENVPN_CA_CERT''' - single line, PEM formatted, base64 encoded, Certification Authority certificate. That is the certificate used to sign OPENVPN_SERVER_CERT and all client certificates. Use the following command to encode:
	~~cat ca.crt \| base64 \| paste -s -d '\0' -~~

	* '''OPENVPN_SERVER_CERT''' - single line, PEM formatted, base64 encoded, server certificate.

	* '''OPENVPN_SERVER_KEY''' - single line, PEM formatted, base64 encoded, server key

	* '''OPENVPN_TA_KEY''' - optional but '''highly recommended''', single line, PEM formatted, base64 encoded, preshared key to use with '''--tls-auth'''. This features adds "extra protection" to the TLS channel by requiring that incoming packets have a valid signature generated using the PSK key. '''Key must be set on both server and client.''' If this key is ever changed, it must be changed on all peers at the same time.

	* '''OPENVPN_REVOKED''' - optional, single line, base64 encoded content of a file containing revoked certificates.

	* '''OPENVPN_INT_NET''' - Network to be used for communication between the server and the clients. It has to be different from the internal OpenNebula network and client's network. Is omitted it default to 10.255.255.0. It is good idea to use different networks especially in one client setup. That way one can have multiple tunnels at the same time if destination networks don't overlap of course.

	* '''OPENVPN_INT_NETMASK''' - Network mask for the network between the server and the clients. Defaults to 255.255.255.0. '''Warning:''' OpenVPN is very picky. It will complain and it will not start if netmask zeros out any bit from the network. For example: net 10.1.1.1 netmask 255.255.255.0 will not work. One needs to use: net 10.1.1.0 netmask 255.255.255.0

	* '''OPENVPN_MAX_CLIENTS''' - Maximum number of simultaneously connected users. It defaults to 3. Tests showed that is a good number for the default size VM.

	~~CipherSpace Virtual Router can be used as a bastion host to build ssh tunnels. This is controlled by the following context variables:~~

	* '''TUNNEL_USER''' - user name. '''It must not exist.''' If user exists it will not be reconfigured. That is to prevent messing up system users. User shell is set to /bin/false.

	* '''TUNNEL_USER_SSH_PUBLIC_KEY''' - single line, base64 encoded, list of keys to install in '''authorized_keys''' file. Since it can can be multi-line it has to be formatted the same way as SSH_PUBLIC_KEY.

	* '''TUNNEL_USER_KEY_RESTRICTIONS''' - optional string that goes before the key in authorized_keys file. Defaults to '''"no-pty,no-agent-forwarding,no-X11-forwarding,no-user-rc"'''. Even though user shell is set to /bin/false one must be careful what goes in this variable.

Valentina at 11:08, 16 September 2016

2016-09-16T11:08:55Z

← Older revision		Revision as of 11:08, 16 September 2016
Line 23:		Line 23:
	== Contextualization Options ==		== Contextualization Options ==

	~~Appliance~~ can be configured with 1 or 2 network interfaces. With 1 network interface it can be used only as '''DHCP''' or '''RADVD''' server.		The virtual router can be configured with 1 or 2 network interfaces. With 1 network interface it can be used only as '''DHCP''' or '''RADVD''' server.

	* '''TEMPLATE''' - this is '''required'''. Otherwise most of the other functionality will not work. Usage:		* '''TEMPLATE''' - this is '''required'''. Otherwise most of the other functionality will not work. Usage: