VRF - Revision history

Sertonix: add category networking

2023-11-10T10:52:27Z

add category networking

← Older revision		Revision as of 10:52, 10 November 2023
Line 67:		Line 67:
	# ip vrf exec vrf-mgmt apk update		# ip vrf exec vrf-mgmt apk update
	</pre>		</pre>

			[[Category:Networking]]

2020-11-06T14:06:56Z

add #

← Older revision		Revision as of 14:06, 6 November 2020
Line 65:		Line 65:
	For other process like apk we use the ip vrf command		For other process like apk we use the ip vrf command
	<pre>		<pre>
	ip vrf exec vrf-mgmt apk update		# ip vrf exec vrf-mgmt apk update
	</pre>		</pre>

2020-11-06T14:06:19Z

Running netowork clients in a specific VRF

← Older revision		Revision as of 14:06, 6 November 2020
Line 54:		Line 54:
	</pre>		</pre>

	== Running ~~netowork~~ clients in a specific VRF ==		== Running network clients in a specific VRF ==

	For ping is a simple as specifying a local interface that is already bound to a specific vrf		For ping is a simple as specifying a local interface that is already bound to a specific vrf

2020-11-06T14:06:11Z

running interactive commands

@@ Line 52: / Line 52: @@
 <pre>
 # ip route add default table mgmt via 1.2.3.1
 </pre>

2020-11-06T13:38:05Z

again

← Older revision		Revision as of 13:38, 6 November 2020
Line 50:		Line 50:

	Then instead of having to remember that 42 is is used for mgmt it can be used directly with ip route, example		Then instead of having to remember that 42 is is used for mgmt it can be used directly with ip route, example
	~~```~~		<pre>
	# ip route add default table mgmt via 1.2.3.1		# ip route add default table mgmt via 1.2.3.1
	~~```~~		</pre>

2020-11-06T13:37:48Z

markdown to wiki :-)

← Older revision		Revision as of 13:37, 6 November 2020
Line 43:		Line 43:

	Example vrf.conf		Example vrf.conf
	~~```~~		<pre>
	42 mgmt		42 mgmt
	43 int		43 int
	44 ext		44 ext
	~~```~~		</pre>

	Then instead of having to remember that 42 is is used for mgmt it can be used directly with ip route, example		Then instead of having to remember that 42 is is used for mgmt it can be used directly with ip route, example

2020-11-06T13:37:19Z

about routing table names

← Older revision		Revision as of 13:37, 6 November 2020
Line 37:		Line 37:
	# rc-service sshd restart		# rc-service sshd restart
	</pre>		</pre>

			== Name route tables ==

			Routing tables can be named i.e. 42 can be named mgmt be editing /etc/iproute2/rt_tables or creating and separate config (e.g. /etc/iproute2/rt_tables.d/vrf.conf)

			Example vrf.conf
			```
			42 mgmt
			43 int
			44 ext
			```

			Then instead of having to remember that 42 is is used for mgmt it can be used directly with ip route, example
			```
			# ip route add default table mgmt via 1.2.3.1
			```

2020-11-06T13:33:19Z

fix route, gateway can not be used as the route ends up in the wrong table

← Older revision		Revision as of 13:33, 6 November 2020
Line 23:		Line 23:
	address 1.2.3.4		address 1.2.3.4
	netmask 255.255.255.0		netmask 255.255.255.0
	~~gateway 1.2.3.1~~
	pre-up ip link set $IFACE master vrf-mgmt		pre-up ip link set $IFACE master vrf-mgmt
			up ip route add default table 42 via 1.2.3.1
	</pre>		</pre>

2020-11-06T12:44:59Z

fix vrf-mgmt still in state down and swtich to $IFACE

← Older revision		Revision as of 12:44, 6 November 2020
Line 12:		Line 12:
	auto vrf-mgmt		auto vrf-mgmt
	iface vrf-mgmt inet manual		iface vrf-mgmt inet manual
	pre-up ip link add ~~vrf-mgmt~~ type vrf table 42		pre-up ip link add $IFACE type vrf table 42
			up ip link set dev $IFACE up
	</pre>		</pre>

Line 23:		Line 24:
	netmask 255.255.255.0		netmask 255.255.255.0
	gateway 1.2.3.1		gateway 1.2.3.1
	pre-up ip link set ~~eth0~~ master vrf-mgmt		pre-up ip link set $IFACE master vrf-mgmt
	</pre>		</pre>

2020-02-14T16:58:53Z

← Older revision		Revision as of 16:58, 14 February 2020
Line 1:		Line 1:
	[[VRF]] or Virtual Routing Functions provide virtualization of the routing table. They are useful for isolating services and entire networks from each other while avoiding the complexity of network namespaces.		[[VRF]] or Virtual Routing and Forwarding (or perhaps Virtual Routing Functions) provide virtualization of the routing table. They are useful for isolating services and entire networks from each other while avoiding the complexity of network namespaces.

	== Prerequisites ==		== Prerequisites ==