From: Vlad Yasevich <vyasevich@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: Problem with a host having an UNREACHABLE address ?
Date: Wed, 03 Dec 2014 16:31:03 +0000 [thread overview]
Message-ID: <547F3AC7.3080906@gmail.com> (raw)
In-Reply-To: <B8F3375A902A0648BD5D9A5ADDE687B005721E0A@cadine.france.prosodie.local>
On 12/03/2014 11:11 AM, Boiteux Frederic wrote:
> Hi,
>
> I've another problem to submit to your knowledge !
>
> I test my SCTP messaging small application between two hosts far away
> one from another, with possible packet loss on the net. Each of them is
> advertising two different [IPv4] addresses, but in fact, on one host,
> one IP isn't actually connected and can't be used for messages.
>
> When I start SCTP messages exchanges, the hosts are using the first
> address, which is working, and messages are correctly transmitted. On
> the peer of the failing-IP host, I get notifications that this IP
> address is UNREACHABLE, it's correct. In fact, I get one notification
> each 100ms, but this can probably be setup.
No, this was an issue that was recently addressed. See
https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id\x061079ac0b9be7a578dcd09f7865c2c0d6ac894a
> The problem is that after some time of message exchanges, about 20
> seconds, the hosts get a LOST notification for the association and no
> message can't be sent anymore until a new association is built.
Which host gets the LOST notification?
>
> Should I do something when I get a UNREACHABLE peer change notification
> ?
You don't have to do anything here.
> is the LOST related to these UNREACHABLE notifications, or should I
> look for other cause ?
It might be, or it might be related to some transport selection code
that has seen some good fixes.
It would be good if you could try this on a recent kernel to see if
you still see the issue.
-vlad
> I didn't saw this behavior during my tests (on
> virtual hosts)...
>
> Thanks for you help,
> Fred.
>
> --
> 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
>
next prev parent reply other threads:[~2014-12-03 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 16:11 Problem with a host having an UNREACHABLE address ? Boiteux Frederic
2014-12-03 16:31 ` Vlad Yasevich [this message]
2014-12-03 16:57 ` Boiteux Frederic
2014-12-04 9:54 ` Boiteux Frederic
2014-12-04 13:46 ` 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=547F3AC7.3080906@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.