From: Vlad Yasevich <vyasevich@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: sctp client not binding to all available addresses
Date: Thu, 07 Mar 2013 02:01:31 +0000 [thread overview]
Message-ID: <5137F4FB.9050305@gmail.com> (raw)
In-Reply-To: <5137797D.3000706@cis.udel.edu>
On 03/06/2013 02:38 PM, Jonathan T. Leighton wrote:
> On 03/06/13 12:42, Vlad Yasevich wrote:
>> On 03/06/2013 12:14 PM, Jon Leighton wrote:
>>> I'm almost certain that calling connect() on an unbound socket used to
>>> result in an INIT being sent with all available IP addresses advertised,
>>> but that's not happening with the code I'm running right now. Has there
>>> been a change in the default behaviour, or do I misremember it? Thanks.
>>>
>>
>> It will list all available addresses that are of a scope that is larger
>> or the same as the destination. You can control selection with the
>> scope_policy sysctl. Check to see what it is set to on your system.
>
> Thanks. Does addr_scope_policy=1 implement the policy described in
> draft-stewart-tsvwg-sctp-ipv4-00, or is there a more recent reference?
> And does addr_scope_policy=0 imply all available addresses are
> advertised (previous behavior)?
The sysctl description is the documentation. You can find it here:
ttps://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/networking/ip-sysctl.txt
Around line 1590.
-vlad
>
> - Jon
>
>> Otherwise, no changes have been made recently to this code. For
>> any more help, we'll need more information.
>>
>> -vlad.
>>> - Jon
>>> --
>>> 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
prev parent reply other threads:[~2013-03-07 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 17:14 sctp client not binding to all available addresses Jon Leighton
2013-03-06 17:42 ` Vlad Yasevich
2013-03-07 2:01 ` 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=5137F4FB.9050305@gmail.com \
--to=vyasevich@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.