All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: linux-sctp@vger.kernel.org
Subject: Re: got some questions on support for multihoming
Date: Thu, 13 Aug 2009 17:15:35 +0000	[thread overview]
Message-ID: <4A844A37.6070101@hp.com> (raw)
In-Reply-To: <4A835B67.2040202@nortel.com>

Chris Friesen wrote:
> Hi all,
> 
> I've got a few questions about the current implementation of SCTP.
> Suppose I have two network nodes, each of which has two IP addresses.
> Theoretically this results in four possible paths between the two nodes.

Theoretically, but often not in practice.

> 
> If the network device corresponding to the primary IP address goes down
> on the remote node, will the current implementation properly switch over
> to use the "most divergent source-destination pair" as suggested in the
> RFC?  I assume this would mean switching to the other IP address on both
> nodes?

It sort of depends on how the addresses are configured.  Assuming a typical
multihomed scenario where each address is in its own subnet, then the answer
is yes.  Ex:

node A (addrs: 1.2.3.4, 2.3.4.5)  <---------> Node B (addrs: 1.2.3.5, 2.3.4.6)

In this case, assuming 1.2.3.0/24 was primary, the path with switch to
2.3.4.5 <--> 2.3.4.5.

It really is a function of the routing looking by the kernel.

> 
> Same question, but with the device corresponding to the primary IP
> address going down on the local node.

Once the appropriate time-outs happen, it should switch the same as above.

> 
> If a chunk times out, will the current implementation retransmit it via
> the "most divergent source-destination pair" as suggested in the RFC?

Most of the time.  We simply try to pick a different destination address to
send to, and let the kernel pick a source.  As long as the source picked by
the kernel is within our bound set, we'll use it.  We don't check for
'mostly divergent pair'.

-vlad

> 
> Thanks,
> 
> Chris
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2009-08-13 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13  0:16 got some questions on support for multihoming Chris Friesen
2009-08-13 17:15 ` Vlad Yasevich [this message]

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=4A844A37.6070101@hp.com \
    --to=vladislav.yasevich@hp.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.