All of lore.kernel.org
 help / color / mirror / Atom feed
* Source IP address of SCTP INIT chunk and the IPv4 address parameter inside SCTP INIT chunk
@ 2015-03-11  2:55 Sun Paul
  2015-03-11 13:27 ` Vlad Yasevich
  0 siblings, 1 reply; 2+ messages in thread
From: Sun Paul @ 2015-03-11  2:55 UTC (permalink / raw)
  To: linux-sctp

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?

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?

any idea on this?

Thanks

- RBK

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Source IP address of SCTP INIT chunk and the IPv4 address parameter inside SCTP INIT chunk
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Vlad Yasevich @ 2015-03-11 13:27 UTC (permalink / raw)
  To: linux-sctp

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
> 


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-03-11 13:27 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.