From: Sun Paul <paulrbk@gmail.com>
To: David Laight <David.Laight@aculab.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
"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: Mon, 9 Jan 2017 18:00:36 +0800 [thread overview]
Message-ID: <CAFXGftJkR75OjWOKZhF_jgv_W1ysFky-msMj1asCU5MQMFE43w@mail.gmail.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DB025A97E@AcuExch.aculab.com>
Hi
the linux router just change the destination, so it can arrive on the
the SERVER.
On Mon, Jan 9, 2017 at 5:51 PM, David Laight <David.Laight@aculab.com> wrote:
> From: Sun Paul
>> Sent: 09 January 2017 02:08
>
>> >> I am setting up a lab where the SCTP traffics from client is passing
>> >> through a linux router before reaching to the SCTP server running
>> >> LKSCTP.
>> >>
>> >> The linux router did not change the source address of the client, so
>> >> when it arrived to the SCTP server, the source address is the oriingal
>> >> one.
>>
>> the INIT chunk arrive on the SERVER, but then no response. the
>> application that using in SERVER is the same as the other test.
>>
>> I noticed one thing in Ethernet frame of the incoming packet on the
>> SERVER compared to the one captured from the client is the LG bit on
>> the source address.
>>
>> The LG bit is set to 0 on the request packet received in the
>> SERVER,but it is 0 from the one originated on the client. willl it be
>> the root cause?
>
> Which addresses are you talking about, and what do you mean by the LG bit?
>
> Is your linux 'router' just routing (ie IP forwarding) or is it doing NAT?
> If it is changing the IP addresses then the addresses inside some SCTP
> chunks also need changing.
>
> David
>
next prev parent reply other threads:[~2017-01-09 10:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 9:34 Problem on SCTP 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 [this message]
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
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=CAFXGftJkR75OjWOKZhF_jgv_W1ysFky-msMj1asCU5MQMFE43w@mail.gmail.com \
--to=paulrbk@gmail.com \
--cc=David.Laight@aculab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=nhorman@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).