login
Search
Hi
we are two students of university of Naples Federico II; we are working on an Traffic generator (D-ITG), and we are implementing the support for SCTP multi-streaming for this software. We are using the Linux Distribution UBUNTU 7.04 with the Kernel version 2.6.20-16 and the lksctp libraries version 1.0.6-2. We have some problem when we try to generate three streams on the same association with variable packet size (in particular with exponential distribution for packet size). In particular during the transmission the sender get blocked on the sctp_sendmsg(), but with constant packet size there is no problem, even with high values of packet size. Is there any problem in lksctp libraries with ubuntu and this configuration?
thanks for help
sorry for our bad english
Diana Luigi
Ercolino Fabio
Change Logs for SCTP
All I can advice is to get very latest versions of all softwares to see if bug might already fixed, that would mean 2.6.23-rc5, it is quite stable, although yesterday my machine locks up with blinking LEDs after many hours whilst running that version (probably some kernel panic but I cannot see which one because I am in the X Window). Also, any library you use, see if newer version has fixed some SCTP bug by reading change logs for that library, then you might like to upgrade that library. Here are some changes in kernel.org kernel since your version that could have effect on your issue. You can find these ChangeLog file at ftp.kernel.org, look for date that exceed your version 2.6.20.16 == 20070816.
ChangeLog-2.6.20.17: the addresses are removed from the interface. This caused SCTP
ChangeLog-2.6.20.17: [PATCH] SCTP scope_id handling fix
ChangeLog-2.6.20.17: SCTP: Add scope_id validation for link-local binds
ChangeLog-2.6.20.17: SCTP currently permits users to bind to link-local addresses,
ChangeLog-2.6.22.6: IPV6: Fix kernel panic while send SCTP data with IP fragments
ChangeLog-2.6.22.6: If ICMP6 message with "Packet Too Big" is received after send SCTP DATA,
ChangeLog-2.6.22.6: kernel panic will occur when SCTP DATA is send again.
ChangeLog-2.6.22.6: <------- SCTP DATA (size=1432)
ChangeLog-2.6.22.6: <------- Resend SCTP DATA (size=1432)
ChangeLog-2.6.23-rc4: [IPV6]: Fix kernel panic while send SCTP data with IP fragments
ChangeLog-2.6.23-rc4: If ICMP6 message with "Packet Too Big" is received after send SCTP DATA,
ChangeLog-2.6.23-rc4: kernel panic will occur when SCTP DATA is send again.
ChangeLog-2.6.23-rc4: <------- SCTP DATA (size=1432)
ChangeLog-2.6.23-rc4: <------- Resend SCTP DATA (size=1432)
ChangeLog-2.6.23-rc5: SCTP: Fix to handle invalid parameter length correctly
ChangeLog-2.6.23-rc5: and not contain any payload, SCTP will ignore this parameter and send
ChangeLog-2.6.23-rc5: SCTP: Abort on COOKIE-ECHO if backlog is exceeded.
ChangeLog-2.6.23-rc5: SCTP: Correctly disable listening when backlog is 0.
ChangeLog-2.6.23-rc5: SCTP: Do not retransmit chunks that are newer then rtt.
ChangeLog-2.6.23-rc5: SCTP: Uncomfirmed transports can't become Inactive
ChangeLog-2.6.23-rc5: This was found at the SCTP interop event.
ChangeLog-2.6.23-rc5: SCTP: Pick the correct port when binding to 0.
ChangeLog-2.6.23-rc5: SCTP: Use net_ratelimit to suppress error messages print too fast
ChangeLog-2.6.23-rc5: SCTP: Fix to encode PROTOCOL VIOLATION error cause correctly
ChangeLog-2.6.23-rc5: chunk. When SCTP encode ABORT chunk with PROTOCOL VIOLATION error cause,
ChangeLog-2.6.23-rc5: SCTP: Fix sctp_addto_chunk() to add pad with correct length
ChangeLog-2.6.23-rc5: SCTP: Assign stream sequence numbers to the entire message
ChangeLog-2.6.23-rc5: it. In such cases, if the message contained multiple SCTP
ChangeLog-2.6.23-rc5: SCTP: properly clean up fragment and ordering queues during FWD-TSN.