Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

SCTP chunk's padding value is not zero #15

Closed
ates opened this Issue · 3 comments

2 participants

@ates
Collaborator

Hello,

I've faced a strange situation when chunks's padding value was not filled with zeros, as it is stated in RFC. Here is an example of SCTP packet:

<<11,89,11,89,109,75,153,162,11,83,232,167,5,0,0,26,0,1,0,22,150,192,147,82,62,
  25,29,131,1,0,120,136,16,85,0,64,0,0,1,1>>

The last two bytes are "padding" and looks like it's incorrect behaviour to have value of padding different from zero.

Has someone seen anything like that before?

Please do not close this issue for some time. It's easy to fix that in pkt_sctp module, but I want to wait for someone who can share some knowledge about that.

@ates
Collaborator

Fixed in 87d90b5

@ates
Collaborator

@laf0rge, Hello Harald, do you have any idea? (I asked you because you have added initial support of SCTP in pkt, maybe you know something about that)

@ates ates closed this
@msantos
Owner

@ates Apologies for the long delay, I meant to look into this. From what I can tell, with sctp, the padding should be ignored (rfc4820):

Padding Data: n bytes (unsigned integer)
      This holds the Padding Data.  The Padding Data MUST be ignored by
      the receiver.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.