First login?
Lost password?
 
 
sctp-discussion AT lists.franken.de 
SCTP Discussions

Text archives Help


Re: [SCTP-Discussion] Problem with CRC32


Chronological Thread 
  • From: Michael Tuexen <Michael.Tuexen AT micmac.franken.de>
  • To: ALLEGRET PILAUD Pierre RD-CORE-ISS <pierre.allegret AT orange-ft.com>
  • Cc: <discussion AT sctp.de>
  • Subject: Re: [SCTP-Discussion] Problem with CRC32
  • Date: Fri Jun 9 10:02:46 2006
  • List-id: SCTP Discussions <discussion.sctp.de>
Are you running two SCTP implementations on the left host? Maybe a kernel SCTP and
an sctplib instance or two instances of the sctplib using the same port number?
This does not work.

Please note also, that the sender of the ABORT has a bug. He is using
the correct V-Tag, which is the initiate tag contained in the INIT, but
the T-bit is set, which is incorrect.

Best regards
Michael


On Jun 9, 2006, at 8:58 AM, ALLEGRET PILAUD Pierre RD-CORE-ISS wrote:

Hi to all,

I have a problem with CRC32 and an SCTP implementation. Is it possible to have a help ?
I performed SCTP interconnection tests with other SCTP implementations with CRC32 or ADLER32 and all worked fine.

When I perform tests with a new equipment, all is OK with ADLER32. If I configure to perform tests with CRC32, I have the following messages:

sctplib S.U.T.
<---------------------- INIT
ABORT ----------------------->
INIT_ACK -------------------->

I don't understand why sctplib send ABORT. With Ethereal traces, I don't see any trouble. Have you an idea ?
(If I perform the same tests with SCTP Linux kernel all works fine)

Thanks. Regards.

Pierre Allégret
<CRC32_pb.txt>



Archive powered by MHonArc 2.6.19+.

Top of page