I was simply trying to follow the example in: http://lartc.org/howto/lartc.rpdb.multiple-links.html That is my introduction and main resource for what I was doing. If there is other resorces that any could suggest beyond the man page I wold be interested to understanding this better. As a follow up issue. The only thing that is not working properly is that I can not pull up my website that is hosted on this server from our private network. Do I need iproutes for my other two nics? I have never needed them before. Thanks again for all your help!!!!!!!!!!!! On Thu, Jul 2, 2009 at 8:06 AM, Chan Chung Hang Christopher < christopher.chan at bradbury.edu.hk> wrote: > Doug Coats wrote: > > I am ecstatically confused. > > > > After I entered the last two commands my routing is working the way that > I > > need it to. > > > > ip rule add from 173.11.51.46 table Cable > > ip rule add from 67.152.166.2 table T1 > > > > The problem is I don't know which actual commands worked. I had just > > rebooted. The other ip commands were all in the rc.local file so they > all > > ran. > > > > Why did the above commands make the Cable and T1 rules show up in the > rules > > list but the following two did not? > > > The following too are not ip rules. They are ip routing table entries. > They will show up if you run 'ip route list table Cable' > > > ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 table Cable > > ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 table T1 > > Do I need all of the commands? So that what is in rc.local looks like > this? > > > > Take a look at the ones I posted...they are taken from rc.local since I > have not taken to effort to integrate them elsewhere per interface. > > > ip rule add from 173.11.51.46 table Cable > > ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 table Cable > > ip route add default via 173.11.51.45 table Cable > > ip route add 173.11.51.44/30 dev eth2 src 173.11.51.45 > > ip route add default via 173.11.51.46 > > ip rule add from 173.11.51.45 to default lookup Cable > > ip rule add from 67.152.166.2 table T1 > > ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 table T1 > > ip route add default via 67.152.166.2 table T1 > > ip route add 67.152.166.0/27 dev eth3 src 67.152.166.2 > > ip rule add from 67.152.166.2 to default lookup T1 > > ip route flush cache > > > > > I find it interesting that you have ip rule commands before the relevant > ip route commands for the custom routing table... > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20090702/ba3048da/attachment-0005.html>