rohc team mailing list archive
-
rohc team
-
Mailing list archive
-
Message #02365
Re: Issues with feedback-2 when dropping context on compressor
-
To:
Rohc <rohc@xxxxxxxxxxxxxxxxxxx>, "didier@xxxxxxxxxxx" <didier@xxxxxxxxxxx>
-
From:
Yakir Matusovsky <yakir.matusovsky@xxxxxxxxxxx>
-
Date:
Thu, 5 Mar 2020 20:00:08 +0000
-
Accept-language:
en-NZ, en-US
-
Arc-authentication-results:
i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=mimomax.com; dmarc=pass action=none header.from=mimomax.com; dkim=pass header.d=mimomax.com; arc=none
-
Arc-message-signature:
i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jHAzrJr4bMFx2AG7KPbZvyx3PeRNlIqjd9eS8c8l+Wc=; b=ipPddJ+QK7AH4qcM8Z+6WZuSUxMU5rECylmQtmfPNoRQhRNcImuDIm5XiNSbHy3bjehmFvajc0bX5nC1gx/Sn1FMFKuGmhRi/92qmKQ4o7X3Ynyn/W7WyH2R/ixwcPf5HE7TSfZWiFaG/HsM+myOFmWTH5ObWTEBg2d1ed4n7+w+NisHpE9xsRIt0qahaidXWgIYqAcm4eGfiMIYw4IFXayX6CA6ZWrf50WxQ135erD4jAF3inZMwSBHZWxHg4ZgpcbHrbZ+eExXzZJGtk/PDh+AYv6fTFkMJVuFIzCMpuCjfjyQv7eiQYzJJDzVROXuJMBES9XNn82kEgO9tjAhBA==
-
Arc-seal:
i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=j085nrWzzwE/A92U9eG+TDtVjKmtRRHzNl6Fv8qp+DaAOf5THpZOSu0TIKrz8L+2S0/NzZPSYgXxLp/PxwS1NZCLNQisdWS/6ps5LcmGJAhtonUJXGTWTTnVDEQi0dDDa5/LElFrI5FxdwliF3T4HenKlTqSZp1Bnqs+fvmRufq6cME//mD2t+9JE1M/gjYelzIHT4bmTnmZG+MjAVQWJqiVZFHy78zwbnLEtQeeNxgvP3quId1dZKuR5szqFOLiXqUlGtnbUzNnyl5Rmx3zsha8e/aYnNmYelrhoxIwKOCksiTYHTxwdcNIk/VU6rdikHCGqQxKhIzFPR2yd1gVhQ==
-
Authentication-results:
spf=none (sender IP is ) smtp.mailfrom=yakir.matusovsky@xxxxxxxxxxx;
-
In-reply-to:
<92F94D27-7690-410A-99CF-C78BD67CF300@mimomax.com>
-
Thread-index:
AQHV8oUt3ByIqDmbbki/AKwT34kVx6g7RjeA
-
Thread-topic:
[Rohc] 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