View source for Routing based on source, destination and other parameters

[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Network related configuration|Network configuration]] > [[IP routing 2 configuration]] > [[Routing based on source, destination and other parameters]]

With advanced IP routing II features of Linux we can route based on source, destination and various other parameters. To configure IP routing II features for routing the basic steps are:
#Create routing tables
#Add routes to routing tables
#Add rules for kernel IP routing 



==Creating routing tables==

To create routing table we have to edit file '<tt>/etc/iproute2/rt_tables</tt>'. In this file we have to add lines like at end
<pre>
200 dmztolocal
210 intranettolocal
220 publictolocal
230 localtopublic
</pre>
Here 200, 210, etc. are routing table numbers. The gap of 10 is just example we can use 200, 201 or 200, 300 any sort of numbers. 'dmztolocal', 'intranettolocal' etc. are names of routing tables. This is one time thing and this information would persist after rebooting.




==Adding routes to routing tables==

We can add routes to routing tables with command '<tt>ip route add table &lt;table_name&gt; via &lt;gateway&gt;</tt>'. We can also specify gateway specific to destinations as we do in normal routing with syntax '<tt>ip route add table &lt;table_name&gt; &lt;destination&gt; via &lt;gateway&gt;</tt>.  Here, table_name is name of routing table that we specify in file '<tt>/etc/iproute2/rt_tables</tt>', destination can be entered IP address/mask format to specify both single host or network, gateway can be any IP reachable by directly connected interfaces.

Using this approach we can populate all routing tables that we have created. The routing within routing table is done with longest prefix match the way it is done in normal routing tables. 

Note that routes added to routing table do not persist after rebooting. Hence permanent configuration of routing should be done by adding route lines in script and calling that script in some start-up file like /etc/rc.d/rc.local or from /etc/init.d/network, etc.



==Seeing routes of particular table==

We can use command '<tt>ip route list table &lt;table_name&gt;</tt>' to see routing entries of particular table. 




==Seeing default rules==

We can see existing routing rules by '<tt>ip rule list</tt>' command. The default rule list looks like
<pre>
0:      from all lookup 255 
32766:  from all lookup main 
32767:  from all lookup default
</pre>
Here 255, main and default are name of tables and 0, 32766, 32767 etc. are priorities. We can list the rules stored
in tables 255, main or default too. 255 table generally has rules related to broadcast or directly connected interfaces. Table main has routing table that we typically see with 'route -n' command. 'default' table is usually empty.

''Note: It is possible to delete rules for table main and default but there is no need to do it. We can always add routes with higher priority without disturbing existing tables.''




==Adding rules which specify which routing table to use==

After creating and populating various routing tables we can add rules which based on source, destination and other selection parameters determine which routing table should be used. To add rule we can use syntax '<tt>ip rule add [from &lt;source_network_or_host&gt;] [to &lt;destination_network_or_host&gt;] [pref &lt;pref_number&gt;] table &lt;table_name&gt;</tt>'.

Note:
*Except table name most parameters from, to, pref number etc. are optional. 
*Rules added via above approach are not persistent same as routes added to routing tables are not persistent. Hence even these lines should be added to some script for permanent configuration.





==Removing rules from rules table==

We can remove rules from rules table by using syntax '<tt>ip rule del pref &lt;pref_number&gt;</tt>'. Here preference number is same that we specify while adding rule or listed when we use 'ip rule list'. We can specify more constraints in case multiple rules with same preference exist in rule table.


==Do not use route command==

After using IP routing II the output of normal route command cannot be trusted as it will just list rules stored in main table which may not have higher priority than rules that we added in custom table. Hence '<tt>route</tt>' command should not be used at all while using IP routing II.


[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Network related configuration|Network configuration]] > [[IP routing 2 configuration]] > [[Routing based on source, destination and other parameters]]