On Tue, April 21, 2015 17:48, Alexey Orishko wrote: > ip route show > default via 192.168.10.10 dev eth0 > 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.10 > 192.168.10.0/24 dev eth1 proto kernel scope link src 192.168.10.11 > > PC2: eth0: 192.168.10.12/24 > > What bother me is the fact that PC2 located on the *same* network > segment is not capable of reaching PC1 via eth1 if eth0 is dead. > > I wonder if kernel multipath has any influence over this...
Hello Alexey, I'm confused as to why your default route is 192.168.10.10 with dev eth0 when eth0 itself is 192.168.10.10. The following may help. I've used both in the past. If you want eth0 and eth1 on the same network to use the gateway given by the dhcp server when eth0 or eth1 is not working, bridge them and use dhcp with the created bridge device. If you want multiple gateways on the same network if one goes down use iproute2's nexthop when setting up the default route. If you use dhcp for that, and each dhcp server gives a different gateway, you'll need hook scripts to use nexthop with iproute2. Sincerely, William Harrington -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
