On 09/24/2014 11:42 AM, Varun Bhatia wrote: > Thanks Vlad for your response but they are already on different subnets :( Look at your neighbor cache (ip neigh list). If it shows the peer on the wrong interface, then you need arg_ignore|arp_announce changes. -vlad > > Sent from Iphone, > Varun > >> On 24-Sep-2014, at 18:36, Vlad Yasevich <vyasevich@xxxxxxxxx> wrote: >> >>> On 09/24/2014 08:56 AM, VARUN BHATIA wrote: >>> Hi, >>> >>> We have developed multihomed application now while testing my setup is: >>> >>> Eth4 as primary interface connected back to back to another machine. >>> Eth5 as secondary interface connected back to back to another machine. >>> >>> I make my porimary interface down now when the INIT is been sent it >>> reaches to peer machine seems using secondary interface but the source >>> ip address kept is of primary interface only due to which when peer >>> machine tries to respond INIT_ACK it tries to send on primary >>> interface ip which is down and due to ICMP it drops the packet. >>> >>> I am not too good in Routing but it seems that some routing has not >>> been configuered properly, why is it always using primary ip ? >>> >>> I have tested the same part when I have connected my primary & >>> secondary interface through router but facrd the same issue. >>> >>> Any inputs are appreciated as I am stuck in it since last 2 days. >>> >> >> Try to put the 2 interfaces into 2 different subnets. That should fix >> your issue. If you can't do that, then you'd have to play with arp_ignore >> and arp_announce sysctl values to make it do what you want. >> >> -vlad -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
