Source based routing - Revision history

Aaron Stephens at 18:33, 16 December 2013

2013-12-16T18:33:32Z

Mmonk: how to access hardware node from container when hardware node uses routing polisy

2012-08-23T18:31:24Z

how to access hardware node from container when hardware node uses routing polisy

Ptman: Added some info that helped me recently

2008-04-16T12:01:05Z

Added some info that helped me recently

Botinki Kira: Robot: Automated text replacement (-VE +container)

2008-03-11T11:36:08Z

Robot: Automated text replacement (-VE +container)

Botinki Kira: Robot: Automated text replacement (-VEs +containers)

2008-03-11T09:49:27Z

Robot: Automated text replacement (-VEs +containers)

Kir: added missing bracket

2006-07-20T17:42:32Z

added missing bracket

Kir: fixed forum links, use template:forum

2006-07-20T17:42:08Z

fixed forum links, use template:forum

Kir: wikified, categorized, enlarged

2006-07-20T17:41:31Z

wikified, categorized, enlarged

Dev at 16:39, 20 July 2006

2006-07-20T16:39:34Z

New page

IP source based routing

to setup src-based routing rules in host system. e.g.

<pre>
# /sbin/ip rule add from $IP table $TBL
# /sbin/ip route add default dev eth0 via $GW table $TBL
</pre>

where $IP is ip address which should use non-default GW.
$GW is gateway for this IP addr
$TBL - any free table number, I use numbers from 6 to ...
every next non-std GW will require another table number

read `man ip` for routing rules details.

http://forum.openvz.org/index.php?t=msg&goto=1631&&srch=src+routing#msg_1631
http://forum.openvz.org/index.php?t=tree&th=492&mid=2881&&rev=&reveal=

Category:HOWTO

@@ Line 1: / Line 1: @@
-Sometimes you have more than one router in your network, and want different [[container]]s to use different routers. For that, you need to set up source-based routing on the host system. For example:
+Sometimes you have more than one router in your network, and want different [[container]]s to use different routers.  Other times you may have a single HN with IP addresses on different networks and want to assign containers addresses from those networks.
 <pre>
-# /sbin/ip rule add from $IP table $TBL
+# /sbin/ip rule add from 192.168.100.0/24 table 10000
-# /sbin/ip route add default dev $ETH via $GW table $TBL
+# /sbin/ip route add throw 192.168.100.0/24 table 10000
-# /sbin/ip route add $NET dev $ETH table $TBL
+# /sbin/ip route add default via 192.168.100.1 table 10000
 </pre>
-where
+Next we add two routing rules to table 10000.  The first one is a throw rule.  A throw rule merely tells the system to stop processing the current table if the destination address matches the criteria provided.  This will allow the host system and the VPSs to continue to reach other systems on our 192.168.100.0/24 network without trying to use the default gateway we provide.  And the second rule provides that default gateway.
-Note that every new non-standard gateway will require another table number.
+Now all we need to do is repeat this for our second network:
 <pre>
-# /sbin/ip route add table $TBL "$IP" dev venet0 scope link
+# /sbin/ip rule add from 192.168.200.0/24 table 10001
 </pre>
-The same routes are added into 'main' table by vzctl set <CTID> --ipadd <$IP>.
-Similar routes should be added for containers to communicate each other.
+Here we have changed the networks in the rule and routes and used a different table number.  Everything else stays the same.  You can, of course, as as many complex routes to a particular table as you like.  If you want to allow a container in the 192.168.100.0/24 network to reach the 192.168.200.0/24 network without using the gateway, you can add another throw rule and allow the HN's default routing table to take effect:
 For more details on routing rules, see <code>man ip</code>.

← Older revision		Revision as of 18:31, 23 August 2012
Line 16:		Line 16:

	Note that every new non-standard gateway will require another table number.		Note that every new non-standard gateway will require another table number.
		+
		+	It is likely that your hardware node uses same table to be accessible via both links, not just the link where it's default gateway points. In this case hardware node will not be able to communicate with container. To fix that one needs to add this route into table $TBL
		+	<pre>
		+	# /sbin/ip route add table $TBL "$IP" dev venet0 scope link
		+	</pre>
		+	The same routes are added into 'main' table by vzctl set <CTID> --ipadd <$IP>.
		+	Similar routes should be added for containers to communicate each other.

	For more details on routing rules, see <code>man ip</code>.		For more details on routing rules, see <code>man ip</code>.

@@ Line 3: / Line 3: @@
 <pre>
 # /sbin/ip rule add from $IP table $TBL
-# /sbin/ip route add default dev eth0 via $GW table $TBL
+# /sbin/ip route add default dev $ETH via $GW table $TBL
 </pre>
 where
 * <code>$IP</code> is an IP address which should use non-default gateway. You can also use netmask here, e.g. <code>10.9.8.0/24</code> will mean that all containers with addresses like 10.9.8.x will be routed through the given gateway.
 * <code>$GW</code> is a gateway for this IP address.
 * <code>$TBL</code> is any free table number, I use numbers from 6 upwards. Note that tables 250-255 are usually reserved (see <code>/etc/iproute2/rt_tables</code>).

← Older revision		Revision as of 11:36, 11 March 2008
Line 1:		Line 1:
−	Sometimes you have more than one router in your network, and want different [[VE]]s to use different routers. For that, you need to set up source-based routing on the host system. For example:	+	Sometimes you have more than one router in your network, and want different [[container]]s to use different routers. For that, you need to set up source-based routing on the host system. For example:

	<pre>		<pre>

@@ Line 7: / Line 7: @@
 where
-* <code>$IP</code> is an IP address which should use non-default gateway. You can also use netmask here, e.g. <code>10.9.8.0/24</code> will mean that all VEs with addresses like 10.9.8.x will be routed through the given gateway.
+* <code>$IP</code> is an IP address which should use non-default gateway. You can also use netmask here, e.g. <code>10.9.8.0/24</code> will mean that all containers with addresses like 10.9.8.x will be routed through the given gateway.
 * <code>$GW</code> is a gateway for this IP address.
 * <code>$TBL</code> is any free table number, I use numbers from 6 upwards. Note that tables 250-255 are usually reserved (see <code>/etc/iproute2/rt_tables</code>).

@@ Line 16: / Line 16: @@
 == See also ==
-[http://forum.openvz.org/index.php?t=msg&th=268 Forum thread #268]
+* {{Forum|268}}
-[http://forum.openvz.org/index.php?t=msg&th=492 Forum thread #492]
+* {{Forum|492}}
 [[Category:Networking]]
 [[Category:HOWTO]]

@@ Line 1: / Line 1: @@
-IP source based routing
+Sometimes you have more than one router in your network, and want different [[VE]]s to use different routers. For that, you need to set up source-based routing on the host system. For example:
 <pre>
@@ Line 8: / Line 6: @@
 </pre>
-where $IP is ip address which should use non-default GW.
+where
-$GW is gateway for this IP addr
+* <code>$IP</code> is an IP address which should use non-default gateway. You can also use netmask here, e.g. <code>10.9.8.0/24</code> will mean that all VEs with addresses like 10.9.8.x will be routed through the given gateway.
-$TBL - any free table number, I use numbers from 6 to ...
+* <code>$GW</code> is a gateway for this IP address.
-every next non-std GW will require another table number
+* <code>$TBL</code> is any free table number, I use numbers from 6 upwards. Note that tables 250-255 are usually reserved (see <code>/etc/iproute2/rt_tables</code>.
-read `man ip` for routing rules details.
+For more details on routing rules, see <code>man ip</code>.
-http://forum.openvz.org/index.php?t=msg&goto=1631&&srch=src+routing#msg_1631
+== See also ==
-http://forum.openvz.org/index.php?t=tree&th=492&mid=2881&&rev=&reveal=
+[http://forum.openvz.org/index.php?t=msg&th=268 Forum thread #268]
-Category:HOWTO
+[[Category:Networking]]