Hello, On Wed, 20 Jun 2018, Akshat Kakkar wrote: > Hi netdev community, > > I have 2 interfaces > eno1 : 192.168.1.10/24 > eno2 : 192.168.2.10/24 > > I added routes as > 172.16.0.0/12 via 192.168.1.254 metric 1 > 172.16.0.0/12 via 192.168.2.254 metric 2 > > My intention : All traffic to 172.16.0.0/12 should go thru eno1. If > 192.168.1.254 is not reachable (no arp entry or link down), then it > should fall back to eno2. You can also try alternative routes. But as the kernel supports only default alternative routes, you can put them in their own table: # Alternative routes use same metric!!! ip route append default via 192.168.1.254 dev eno1 table 100 ip route append default via 192.168.2.254 dev eno2 table 100 ip rule add prio 100 to 172.16.0.0/12 table 100 Of course, you will get better results if an user space tool puts only alive routes in service after doing health checks of all near gateways. Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lartc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
