Fix Go Reboot on ZTE MF79U
Budget: $30 – $250 USD
I’m maintaining a small Go utility that manages ZTE MF79U USB modems. Every call I make to the firmware’s reboot API is accepted—yet the device never actually restarts. The request is definitely reaching the modem, but something in the handshake or payload is off.
What I already have
• The original firmware documentation for this model, including every API endpoint, header requirement, token flow, and sample JSON.
• A concise Go client (≈150 lines, Go 1.20) that authenticates, retrieves status info, and sends the reboot command.
• Logs showing a clean 200 response when the reboot is triggered, followed by… nothing.
What I need from you
• Audit the existing Go code and pinpoint why the reboot sequence stalls.
• Adjust headers, CSRF token handling, cookies, timing, or any other detail the modem expects.
• Supply a working patch or new function that reboots the MF79U reliably—multiple consecutive tests must succeed.
• Provide a brief changelog or annotated diff so I can merge the fix into our repo.
You may run tests on your own hardware or guide me through remote trials; I can execute binaries and return logs in real time. The final deliverable is an updated .go file (or diff) plus a concise explanation of the fix that proves the modem now reboots via API without fail.
What I already have
• The original firmware documentation for this model, including every API endpoint, header requirement, token flow, and sample JSON.
• A concise Go client (≈150 lines, Go 1.20) that authenticates, retrieves status info, and sends the reboot command.
• Logs showing a clean 200 response when the reboot is triggered, followed by… nothing.
What I need from you
• Audit the existing Go code and pinpoint why the reboot sequence stalls.
• Adjust headers, CSRF token handling, cookies, timing, or any other detail the modem expects.
• Supply a working patch or new function that reboots the MF79U reliably—multiple consecutive tests must succeed.
• Provide a brief changelog or annotated diff so I can merge the fix into our repo.
You may run tests on your own hardware or guide me through remote trials; I can execute binaries and return logs in real time. The final deliverable is an updated .go file (or diff) plus a concise explanation of the fix that proves the modem now reboots via API without fail.