Doug Coats wrote: > I am not understanding somethings very fundamental to me > troubleshooting this issue. > > How do I clear the iproute2's that I have created? They are cleared by being deleted or a reboot takes place. Try 'ip route help' and 'ip rule help' > > How do I tell if they are in affect? Now that is a good one...ping/telnet tests from another host... > > What should they look like when listed if they are configured properly? Here is my output from ip rule list 0: from all lookup local 32764: from 203.174.45.30 lookup wharf 32765: from 220.232.217.78 lookup pacific 32766: from all lookup main 32767: from all lookup default Lower numbers mean higher priority. Routing tables: ip route list table wharf: 203.174.45.24/29 dev eth2 proto kernel scope link src 203.174.45.30 10.9.0.0/17 dev eth1 proto kernel scope link src 10.9.1.101 default via 203.174.45.25 dev eth2 ip route list table pacific 220.232.217.72/29 dev eth0 proto kernel scope link src 220.232.217.78 10.9.0.0/17 dev eth1 proto kernel scope link src 10.9.1.101 default via 220.232.217.73 dev eth0 ip route list will give you your main routing table which is the same one that route -n will report