From: David Laight <David.Laight@ACULAB.COM>
To: "'Sun Paul'" <paulrbk@gmail.com>, Neil Horman <nhorman@tuxdriver.com>
Cc: "linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Problem on SCTP
Date: Thu, 12 Jan 2017 09:51:00 +0000 [thread overview]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DB025F9FD@AcuExch.aculab.com> (raw)
In-Reply-To: <CAFXGftLSFgPpxD6Oak8h1Y5y11-zXWLj0v4ziMFkjX8eZ4ZJgA@mail.gmail.com>
From: Sun Paul [mailto:paulrbk@gmail.com]
> Sent: 12 January 2017 09:31
> Let me clear the understanding. below is the flow.
>
> 1. Client sends to Linux Router: 192.168.206.83 -> 192.168.206.56,
> 2. Linux router sends to SERVER where the source IP is unchanged:
> 192.168.206.83 -> 192.168.206.66
>
> My question here is why SERVER cannot response this INIT chunk?
Probably because the IP addresses embedded in the SCTP packet
don't match the ones in the IP header.
David
next prev parent reply other threads:[~2017-01-12 9:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 9:34 Sun Paul
2017-01-06 11:43 ` Marcelo Ricardo Leitner
2017-01-09 2:06 ` Sun Paul
2017-01-06 12:37 ` Neil Horman
2017-01-09 2:08 ` Sun Paul
2017-01-09 2:30 ` Sun Paul
2017-01-09 9:51 ` David Laight
2017-01-09 10:00 ` Sun Paul
2017-01-09 12:25 ` Neil Horman
2017-01-09 16:31 ` Sun Paul
2017-01-09 19:18 ` Neil Horman
2017-01-10 1:30 ` Sun Paul
2017-01-10 1:31 ` Sun Paul
2017-01-10 14:33 ` Neil Horman
2017-01-11 8:39 ` Sun Paul
2017-01-11 12:57 ` Neil Horman
2017-01-12 9:30 ` Sun Paul
2017-01-12 9:51 ` David Laight [this message]
2017-01-12 10:53 ` Michael Tuexen
2017-01-13 3:27 ` Sun Paul
2017-01-13 3:27 ` Sun Paul
2017-01-13 3:29 ` Sun Paul
2017-01-13 9:43 ` Michael Tuexen
2017-01-13 13:19 ` Michael Tuexen
2017-02-21 4:26 ` Sun Paul
2017-02-21 15:53 ` Xin Long
2017-02-22 1:12 ` Sun Paul
2017-02-22 2:00 ` Xin Long
2017-02-22 2:29 ` Sun Paul
2017-02-22 3:03 ` Xin Long
2017-02-23 5:30 ` Sun Paul
2017-02-23 6:07 ` Xin Long
2017-02-27 9:01 ` Sun Paul
2017-02-27 15:06 ` Xin Long
2017-03-01 4:15 ` Sun Paul
2017-03-01 6:43 ` Xin Long
2017-01-16 18:47 ` Marcelo Ricardo Leitner
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=063D6719AE5E284EB5DD2968C1650D6DB025F9FD@AcuExch.aculab.com \
--to=david.laight@aculab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=paulrbk@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®