OTA update using microlink

[djorr5]

Hi, has anyone successfully done an OTA update to an ESP32S3 board whilst on the tailscale network using microlink? If I put my board on my local LAN and remove connection using microlink I can successfully do it but if I am on my Tailscale network it fails. I can see the download begin no problems:

`I (10123051) esp_app_thingsboard: OTA: new firmware available:
I (10123055) esp_app_thingsboard: OTA download: http://firmware?title=
I (10123063) esp_app_thingsboard: OTA state: DOWNLOADING
I (10123067) ml_tcp: TCP connect to x.x.x.x:xxxx (timeout=30000ms)
I (10123105) ml_tcp: WG tunnel up after 0ms
[WG_RX] type=4 (DATA) len=80 from 192.168.1.115:41641
I (10123111) ml_tcp: TCP socket bound to VPN IP
[WG_RX] type=4 (DATA) len=80 from 192.168.1.115:41641
[WG_RX] type=4 (DATA) len=80 from 192.168.1.115:41641
[WG_RX] type=4 (DATA) len=80 from 192.168.1.115:41641
I (10123129) ml_tcp: TCP connected to (13 ms)
[WG_RX] type=4 (DATA) len=80 from 192.168.1.115:41641
[WG_RX] type=4 (DATA) len=1312 from 192.168.1.115:41641
[WG_RX] type=4 (DATA) len=1312 from 192.168.1.115:41641
[WG_RX] type=4 (DATA) len=352 from 192.168.1.115:41641
[WG_RX] type=4 (DATA) len=1312 from 192.168.1.115:41641
[WG_RX] type=4 (DATA) len=1312 from 192.168.1.115:41641

But it crashes before it finishes the download:

Guru Meditation Error: Core 0 panic'ed (LoadProhibited). Exception was unhandled

[antonmeyer]

This looks like the same root cause we just tracked down and fixed in #28 (also fixes #17) — a thread-safety violation in wireguardif.c's RX path that only manifests under sustained real TCP load through the tunnel (which is exactly what a firmware download is), not under lighter control-plane traffic. That would also explain why it works fine over plain LAN for you: that path never goes through the affected code at all.

The crash signature matches closely (Guru Meditation Error / LoadProhibited, mid-download under sustained WG_RX DATA traffic). Worth trying PR #28's fix on your setup if you're still hitting this — would be useful confirmation either way.