I have following setup:
I want to send files from 10.1.1.7 to 10.1.1.3 with the caveat that if link AB goes down, then file transfer should switch to link AC and CB.
However, problem is that the other interface IP is 10.1.1.17 and hence even if it receives packets for 10.1.1.3, it will ignore them.
One possible solution that I tried is I created a software bridge on receiving machine and added 10.1.1.3 & 10.1.1.17 under it. However, as soon as I do that, both interfaces stop responding to ARP queries even if all the links are up.
Any ideas about how to solve this?
UPDATE:
Here is how setup the bridge: (Linux ubuntu 9.04)
I first start ping from machine one to machine two (on ip 10.1.1.3 (eth10))
$$brctl addbr br0 $$brctl addif br0 eth8 $$brctl addif br0 eth10 (After this ping immediately stops) $$ifconfig br0 0
But once I do this, eth10 (10.1.1.3) stops responding to ARP queries for IP address 10.1.1.3 even if it relieves them.
What gets appended to dmesg after executing above commands:
[132445.491404] device eth8 left promiscuous mode [132445.491433] br0: port 2(eth8) entering disabled state [132445.491520] device eth10 left promiscuous mode [132445.491532] br0: port 1(eth10) entering disabled state [132472.721188] device eth8 entered promiscuous mode [132474.881542] device eth10 entered promiscuous mode [132480.161572] br0: port 2(eth10) entering learning state [132480.161585] br0: port 1(eth8) entering learning state