You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
edit 21-02-27:
Title was: "Feature request: implement ClientContext::wait_until_acked()"
Per #7896, renaming to "OTA: Investigate workaround delay when receiving 'OK'" implemented by #6351.
edit 21-04-01: It seems ClientContext::wait_until_sent() is not sufficient for a fully terminated transmission.
There are two OK in the ArduinoOTA protocol w/espota.py tool, one of them is UDP.
Changed title to: Add a non-breaking extension to the OTA protocol for getting rid of UDP.
changed the title [-]Feature request: implement ClientContext::wait_until_acked()[/-][+]OTA: Investigate workaround delay when receiving 'OK'[/+]on Feb 27, 2021
changed the title [-]OTA: Investigate workaround delay when receiving 'OK'[/-][+]Add a non-breaking extension to the OTA protocol for getting rid of UDP[/+]on Apr 1, 2021
I would like to add my observations when chasing a missing "OK" response upon a successful authorization. It turned out that basically a router bug was responsible for the packet loss, but it seems to me slightly naive in the ArduinoOTA code to rely on the successful transmission of a single UDP packet. UDP is per se subject to packet losses, so at least the packets should be sent twice or thrice to increase the reliability. This was in the end what saved me from the bug, as the router (an AVM Fritzbox with OS 7.21) would only drop the very first packet.
Activity
rename ClientContext::wait_until_sent() to wait_until_acked()
[-]Feature request: implement ClientContext::wait_until_acked()[/-][+]OTA: Investigate workaround delay when receiving 'OK'[/+]d-a-v commentedon Feb 27, 2021
(moved to OP)
rename ClientContext::wait_until_sent() to wait_until_acked() (#7896)
[-]OTA: Investigate workaround delay when receiving 'OK'[/-][+]Add a non-breaking extension to the OTA protocol for getting rid of UDP[/+]Miq1 commentedon Apr 2, 2021
I would like to add my observations when chasing a missing "OK" response upon a successful authorization. It turned out that basically a router bug was responsible for the packet loss, but it seems to me slightly naive in the ArduinoOTA code to rely on the successful transmission of a single UDP packet. UDP is per se subject to packet losses, so at least the packets should be sent twice or thrice to increase the reliability. This was in the end what saved me from the bug, as the router (an AVM Fritzbox with OS 7.21) would only drop the very first packet.
7 remaining items