← Back to team overview

rohc team mailing list archive

Re: Issues with feedback-2 when dropping context on compressor

 

An update -- when TCP profile gets disabled on the system, such problem does not occur.

Regards,
Yakir

From: Rohc <rohc-bounces+yakir.matusovsky=mimomax.com@xxxxxxxxxxxxxxxxxxx> on behalf of Yakir Matusovsky <yakir.matusovsky@xxxxxxxxxxx>
Date: Thursday, 5 March 2020 at 1:30 PM
To: Rohc <rohc@xxxxxxxxxxxxxxxxxxx>, "didier@xxxxxxxxxxx" <didier@xxxxxxxxxxx>
Subject: Re: [Rohc] Issues with feedback-2 when dropping context on compressor

An update, we’ve tried running same scenario over prototype code with RoHC-2.3.1 and the problem is still there.

Regards,
Yakir

From: Rohc <rohc-bounces+yakir.matusovsky=mimomax.com@xxxxxxxxxxxxxxxxxxx> on behalf of Yakir Matusovsky <yakir.matusovsky@xxxxxxxxxxx>
Date: Thursday, 5 March 2020 at 11:49 AM
To: Rohc <rohc@xxxxxxxxxxxxxxxxxxx>, "didier@xxxxxxxxxxx" <didier@xxxxxxxxxxx>
Subject: [Rohc] Issues with feedback-2 when dropping context on compressor

Experiencing an issue with RoHC 2.1.x code over a radio link, where if IPv4 pinging across a near end to the far end, after a reboot on the near end the compressor receives a malformed feedback from a far end decomp and seems that it can’t reduce its compression state, used optimistic mode,

rohc_comp.c:3108 rohc_comp_feedback_parse_opts()] malformed FEEDBACK-2: packet too short for 6-byte option 15, o
rohc_comp_rfc3095.c:961 rohc_comp_rfc3095_feedback_2()] malformed FEEDBACK-2: failed to parse options
rohc_comp_rfc3095.c:903 rohc_comp_rfc3095_feedback()] failed to handle FEEDBACK-2
rohc_comp.c:2004 __rohc_comp_deliver_feedback()] failed to deliver feedback: failed to handle FEEDBACK-2
rohc_comp.c:2101 rohc_comp_deliver_feedback2()] failed to deliver feedback item #1
rohc_comp.c:3108 rohc_comp_feedback_parse_opts()] malformed FEEDBACK-2: packet too short for 9-byte option 4, on
rohc_comp_rfc3095.c:961 rohc_comp_rfc3095_feedback_2()] malformed FEEDBACK-2: failed to parse options
rohc_comp_rfc3095.c:903 rohc_comp_rfc3095_feedback()] failed to handle FEEDBACK-2
rohc_comp.c:2004 __rohc_comp_deliver_feedback()] failed to deliver feedback: failed to handle FEEDBACK-2
rohc_comp.c:2101 rohc_comp_deliver_feedback2()] failed to deliver feedback item #1
rohc_comp.c:3108 rohc_comp_feedback_parse_opts()] malformed FEEDBACK-2: packet too short for 9-byte option 4, on
rohc_comp_rfc3095.c:961 rohc_comp_rfc3095_feedback_2()] malformed FEEDBACK-2: failed to parse options
rohc_comp_rfc3095.c:903 rohc_comp_rfc3095_feedback()] failed to handle FEEDBACK-2
rohc_comp.c:2004 __rohc_comp_deliver_feedback()] failed to deliver feedback: failed to handle FEEDBACK-2
rohc_comp.c:2101 rohc_comp_deliver_feedback2()] failed to deliver feedback item #1
rohc_comp.c:3108 rohc_comp_feedback_parse_opts()] malformed FEEDBACK-2: packet too short for 9-byte option 4, on
rohc_comp_rfc3095.c:961 rohc_comp_rfc3095_feedback_2()] malformed FEEDBACK-2: failed to parse options
rohc_comp_rfc3095.c:903 rohc_comp_rfc3095_feedback()] failed to handle FEEDBACK-2
rohc_comp.c:2004 __rohc_comp_deliver_feedback()] failed to deliver feedback: failed to handle FEEDBACK-2
rohc_comp.c:2101 rohc_comp_deliver_feedback2()] failed to deliver feedback item #1

The ping is stuck.

The product is about to go on 2.3.1 in future, however, could this be resolved in the current version mentioned?

Regards
Yakir

References