rohc team mailing list archive

[Didier Barvaux <didier@xxxxxxxxxxx>]

>  Here is more info.  I also get a few of these
> 
> 	rohc_lsb_decode() assert
> 	cannot use scaled TCP sequence number for a packet with an
> empty payload.
> 
> In this case, the payload_len is 0.  Is this caused by mismatched
> list options, or something else? Thanks,

Something else. The compressor seems to have used the scaling encoding
for the TCP sequence number of a packet without payload. That's not
allowed. I fixed a similar problem at revision 1085. What revision do
you use?

------------------------------------------------------------
revno: 1085
committer: Didier Barvaux
branch nick: rohc-main
timestamp: Sun 2014-04-27 19:15:21 +0200
message:
  TCP profile: do not compute the scaled TCP sequence number if the TCP
payload is empty
------------------------------------------------------------

If you use one older revision, please test again with the latest
revision. If not, could you tell me the ROHC packet (co_common, rnd_X,
seq_X...) for which the decompressor emits those warnings?

Regards,
Didier

Attachment: signature.asc
Description: PGP signature