Hello all\n\nI'm trying to verify whether host routes will work in our network.\nWhat I want to do, for testing purposes only, is route a connection\nfrom A, through B, to C. Normally traffic goes directly from A to C.\n\nWe have a frame network - our operation center has 2 pipes coming in.\nEach remote branch is connected directly to our operation center via\none of those pipes. Each branch also has a PVC to our St. Paul\nlocation for backup purposes. St. Paul pushes traffic over either of\nthe 2 pipes going into the operation center. What I'm trying to\nconfirm is if one pipe at operations goes down, the remote branches\nconnecting through that line can re-route traffic to St. Paul and then\non to Ops. Hope that makes sense.\n\n172.17.1.0 network is for the Operation center\n192.168.2.0 is for the remote branch\n192.168.1.0 is for St. Paul\n\nHere is the config from the remote branch:\n\nip route 0.0.0.0 0.0.0.0 172.17.1.1\nip route 172.17.1.0 255.255.255.0 10.1.1.69\nip route 172.17.1.188 255.255.255.255 10.1.1.133\nip route 192.168.1.0 255.255.255.0 10.1.1.133\n\nHere is the config from the St. Paul router:\n\nip route 0.0.0.0 0.0.0.0 172.17.1.1\nip route 172.17.1.0 255.255.255.0 10.1.1.65\nip route 172.17.1.0 255.255.255.0 10.1.1.13\nip route 192.168.2.0 255.255.255.0 10.1.1.132\n\nHere is the config from the Operation Center:\n\nip route 0.0.0.0 0.0.0.0 172.17.1.241\nip route 192.168.1.0 255.255.255.0 10.1.1.66\nip route 192.168.1.0 255.255.255.0 10.1.1.14\nip route 192.168.2.0 255.255.255.0 10.1.1.70\n\nWhen those configs are in place I am unable to ping from the remote\nbranch router to the 172.17.1.188 address at Operations. The\nconnection just times out. Shouldn't the St. Paul router see that\nrequest coming through and route it to the 172.17.1.0 subnet? Am I\nmissing something extremely obvious?\n\nAny insight would be great!