So after figuring out that it was a iproute2 problem, I found the following link giving an example of
where to put all the route and rules and table information to be read at boot up.
http://lists.centos.org/pipermail/centos/2011-January/105072.htmlSo I created 4 files in /etc/sysconfig/network-scripts that implemented the following lines
ip route add default via 128.171.158.1 dev vlan158 table 1
ip route add default via 128.171.159.1 dev vlan159 table 2
ip rule add from 128.171.158.6 tab 1 priority 500
ip rule add from 128.171.159.253 tab 2 priority 501
route-vlan158:
default via 128.171.158.1 dev vlan158 table 1
route-vlan159:
default via 128.171.159.1 dev vlan159 table 2
rule-vlan158:
from 128.171.158.6 tab 1 priority 500
rule-vlan159:
from 128.171.159.253 tab 2 priority 501
The ip addresses specified in the rules files are the ip addresses that are defined on vlan158 and vlan159
and the ip addresses specified in the route-vlan files are the gateways for the respective subnets. After I
had all those in there, I just rebooted to check it and I can ping the 159.253 address from the 158 subnet
and vice versa.
Thank you jlehtone. I never would have figured this out without your hints.
This Post was from: https://www.centos.org/newbb/viewtopic.php?forum=58&topic_id=34611&post_id=148940