All of lore.kernel.org
 help / color / mirror / Atom feed
From: Varun Bhatia <varuninbharti@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: SCTP Multihoming Always sending primary interface ip I
Date: Wed, 24 Sep 2014 15:54:35 +0000	[thread overview]
Message-ID: <7ACBFD95-A2A3-47BB-9E8C-6A567F110907@gmail.com> (raw)
In-Reply-To: <CAFi7Gbw8e8_y-fmMNPW482os9gq+Y+psf6XyJaq1jm1_1UJt0A@mail.gmail.com>

Thanks Vlad for your response but they are already on different subnets :(

Sent from Iphone,
Varun

> On 24-Sep-2014, at 18:36, Vlad Yasevich <vyasevich@gmail.com> 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

  parent reply	other threads:[~2014-09-24 15:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 12:56 SCTP Multihoming Always sending primary interface ip I VARUN BHATIA
2014-09-24 13:06 ` Vlad Yasevich
2014-09-24 15:54 ` Varun Bhatia [this message]
2014-09-24 16:33 ` Vlad Yasevich
2014-09-24 17:38 ` VARUN BHATIA
2014-09-24 18:22 ` Vlad Yasevich
2014-09-25 10:35 ` VARUN BHATIA
2014-09-25 12:36 ` Neil Horman
2014-10-01 13:58 ` VARUN BHATIA
2014-10-03 13:24 ` Neil Horman
2014-10-03 14:54 ` Vlad Yasevich
2014-10-07  7:44 ` VARUN BHATIA
2014-10-08  7:19 ` VARUN BHATIA
2014-10-08 13:17 ` Neil Horman
2014-10-13 13:38 ` VARUN BHATIA
2014-10-14  9:08 ` Vladislav Yasevich
2014-10-14 13:14 ` VARUN BHATIA
2014-10-20 13:10 ` Neil Horman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7ACBFD95-A2A3-47BB-9E8C-6A567F110907@gmail.com \
    --to=varuninbharti@gmail.com \
    --cc=linux-sctp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.