Super cool work!

[iliabaranov]

This is great, thank you for taking a first crack at this. :D

I've been wanting to get ESP32 able to talk natively with tailscale forever

[iliabaranov]

Your default project here wouldn't build for me on Ubuntu 24.04, I used Claude to help fix it up, here's what it outputs:

Issues Found:

1. Multiple backend compilation: Both reference and sodium backends of noise-c were being compiled, causing duplicate function definitions
   (noise_chachapoly_new, noise_curve25519_new, etc.)
2. Duplicate noise_rand_bytes: Defined in both noise-c's rand_sodium.c and tailscale.cpp
3. poly1305 conflict: Both noise-c's crypto/donna and esp_wireguard provided the same implementation

Fix Applied:

Updated the noise-c patch at patches/noise-c/0001-Add-srcFilter-to-exclude-conflicting-sources.patch to exclude conflicting sources:

• Excluded protocol/rand_sodium.c (using custom ESP32 implementation)
• Excluded crypto/donna directory (to avoid conflict with esp_wireguard)
• Excluded ref backend for ChaCha20-Poly1305, Curve25519, SHA256, and AESGCM (using optimized sodium backend instead)
• Kept ref backend only for BLAKE2s/BLAKE2b (not available in libsodium)

Build Results:

• Status: SUCCESS (took 5.23 seconds)
• RAM usage: 14.7% (48,080 / 327,680 bytes)
• Flash usage: 73.1% (1,341,918 / 1,835,008 bytes)
• Output: .esphome/build/esp32-ts/firmware.bin

[alfs]

Thanks, there was an external/required/noise-c/library.json file created in my local repo that did the filtering, which was not commited (since it was in a submodule) and I didn't notice it should also be patched in.

[alfs]

Hey @iliabaranov, I've done bunch of updates. I vendored noice-c, and re-architected everything to provide a netif network interface, so applications don't need any modification (it's just like a vpn service on the IP level).

I just now enabled the internal web server and curl'ed it without any other changes.

Note that memory can be an issue - haven't optimized here. In case there are crashes, it's probably it.