From: Vlad Yasevich <vyasevich@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: Source IP address of SCTP INIT chunk and the IPv4 address parameter inside SCTP INIT chunk
Date: Wed, 11 Mar 2015 13:27:31 +0000 [thread overview]
Message-ID: <550042C3.3010106@gmail.com> (raw)
In-Reply-To: <CAFXGftK0QQiazx3MCdz+8rXosOLbXS0E52DyTjwDGiYZzTB8GQ@mail.gmail.com>
On 03/10/2015 10:55 PM, Sun Paul wrote:
> Hi
>
> I would like to ask about the IP address on dource IP address of SCTP
> INIT chunk and the IPv4 address parameter inside SCTP INIT chunk.
>
> If the source IP of the SCTP INIT chunk is 10.1.1.84, but the IP
> address INSIDE the INIT chunk, i.e. the IPv4 address parameter, is
> using a different IP address, says 192.1.1.84, what will be happened?
This is part of multihoming support of sctp. The system generating
such INIT chunk says that is can be reached via either address. The
peer system will the create 2 paths, one to 10.1.1.84 and the other
to 192.1.1.84 and will use them in cases of failover and retransmission.
>
> I did a testing on a SCTP server and client environment, and it seems
> the SCTP server tried to send INIT_ACK back to the source IP to the
> client, i.e. the destination IP address is 10.1.1.84. but somehow, the
> SCTP server generate two HEARTBEAT request, one to 10.1.1.84 and one
> to 192.1.1.84.
>
> is it a problem on our SCTP server application?
No, this is behaving exactly how specified in the SCTP specification.
-vlad
>
> any idea on this?
>
> Thanks
>
> - RBK
> --
> 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:[~2015-03-11 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 2:55 Source IP address of SCTP INIT chunk and the IPv4 address parameter inside SCTP INIT chunk Sun Paul
2015-03-11 13:27 ` 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=550042C3.3010106@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.