lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFXGftLc1Oi9yN-J2UdQxN4MALDhEHieZdGp5JCkOp6Ar+r4Qg@mail.gmail.com>
Date:   Mon, 9 Jan 2017 10:08:03 +0800
From:   Sun Paul <paulrbk@...il.com>
To:     Neil Horman <nhorman@...driver.com>
Cc:     linux-sctp@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Problem on SCTP

Hi

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?



On Fri, Jan 6, 2017 at 8:37 PM, Neil Horman <nhorman@...driver.com> wrote:
> On Fri, Jan 06, 2017 at 05:34:47PM +0800, Sun Paul wrote:
>> Hi
>>
>> 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.
>>
>> however, I found that there is no response from the SCTP server, any
>> idea on this?
>>
>> if I connect the client directly to the SCTP server, it do not have any issue.
>>
>> help pls
>>
>> rbk
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
>> the body of a message to majordomo@...r.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
> Start with a tcpdump on the client and the server and attempt a connection,
> check to see if the INIT and INIT-ACK chunks are arriving appropriately.
>
> Neil
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ