Hellos Much thanks for your reply Im using RedHat 2.6.18-164.2.1.el5 without any patch The way Im using to test failed gateway is with iptables blocking the traffic, probably not the best simulation. What I want to test is a switch/router fail that wont forward my connection properly. The conf I have is 4ethernet bonded in 2bonds bond0 bond1 the bonding swithcs with arp_ping checks Everything is pretty ok, but since I have this critical IP and have to paths to get to it, though I could add extra redundancy with iproute tools Right now I did a test with your input, failing one path, and after putting it up again, doing ping to the gateway ip But no change happens.... Do you have any extra clues? Much Thanks Jose > jose nuno neto writes: > >> I'm trying to setup a failover static route that allow some redundancy >> in >> case one interface is not working ok >> >> I set this with ip route add >> >> 172.26.240.4 >> nexthop via 172.26.247.248 dev bond1 weight 1 >> nexthop via 172.26.31.248 dev bond0 weight 1 >> >> And if the first route fails the second gets active, but later if the >> that >> seconde fails and the first is ok, no failback happens >> >> Is this a timing? How does the kernel is doing the route check? > > Are you using Julian Anastasov's patches? [http://www.ssi.bg/~ja/] > > It might be that the kernel does not know the first route is available > again. Documentend in the dead gateway detection document is that you need > to actively ping the uplink gateways in order to make sure the kernel > knows > whether or not they are alive. > > And another thought: how does the route "fail"? If your interface is going > down, you might want to add the routes with "proto static" (though I don't > know if that's possible with an unpatched kernel). > > Regards, > > roel > > -- > To unsubscribe from this list: send the line "unsubscribe linux-net" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
