linux-sctp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: multihoming client question
Date: Wed, 07 Dec 2016 12:37:28 +0000	[thread overview]
Message-ID: <CADvbK_cDRhXbyYky0YsagBLmcaHmCZ9owoz64eJJz7pLi7Gtrw@mail.gmail.com> (raw)
In-Reply-To: <CAJ0j_BYFOO+szALYGoFryCcpOrRoYjrgPOx_VVcUvOtSUX31Uw@mail.gmail.com>

On Thu, Dec 1, 2016 at 3:04 PM, tsoi andrew <tsoiandrew@gmail.com> wrote:
> Dear Sir,
>
> The connection is broken so that no data is sending at this moment.
> While testing failover(force no heartbeat ack replied from the IP X),
> I find that IP A try to send the heartbeat to IP Y but no heartbeat
> ack finally.  Can lksctp client try to send heartbeat from IP B to IP
> Y?     As only connection between IP B and IP Y is valid at that time.
>
I got your issue now.

http://marc.info/?l=linux-sctp&m\x143714727725657&w=2

This patch probably affect that.

after that fix, sctp asks the route oif address must be the src when
using secondary addresses

so in your case, oif's ip of that route to Y  must be A, instead of B.
that's why sctp never choose path B->Y.

if you want B->Y, I need you need to adjust your route.

  parent reply	other threads:[~2016-12-07 12:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 10:48 multihoming client question tsoi andrew
2016-11-30 11:39 ` Xin Long
2016-12-01  7:04 ` tsoi andrew
2016-12-07 12:37 ` Xin Long [this message]
2016-12-21  9:10 ` tsoi andrew
2016-12-21 14:04 ` Marcelo Ricardo Leitner
2017-01-11 10:24 ` tsoi andrew
2017-01-11 13:19 ` Xin Long
2017-02-21  8:51 ` tsoi andrew
2017-02-22  9:20 ` Xin Long

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=CADvbK_cDRhXbyYky0YsagBLmcaHmCZ9owoz64eJJz7pLi7Gtrw@mail.gmail.com \
    --to=lucien.xin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).