ESP KVM
Replies: 3 comments 4 replies
|
Hello. The Tailscale client is Go, and there's no Go runtime for the ESP32-P4, so it can't be ported the way "tailscale-embedded" runs on Linux. Reimplementing the coordination/DERP/key-exchange protocol in C would be a huge job - more than this firmware can reasonably carry. So native Tailscale is stuck for now, not for lack of wanting it, but because the runtime just isn't there on this chip. What I am working on right now is WireGuard (which Tailscale is built on top of). If it comes together I'll ship it soon - a settings page for the keys/endpoint, a status line with the assigned IP and last handshake, and an on/off toggle. It won't be Tailscale's zero-config magic, but it's real built-in encrypted remote access. And if you want full Tailscale today with zero firmware changes: run it as a subnet router on something already on your LAN (a Pi, a mini-PC, an OpenWrt/GL.iNet router, even the machine the KVM is attached to) and advertise the KVM's IP - your whole tailnet then reaches it over Tailscale. That's Tailscale's own recommended pattern for hardware that can't run the client. |
|
There is https://github.com/CamM2325/microlink |
|
Oh nice, thanks for the link - hadn't seen this one, I'll definitely take a look. ;) |
|
https://github.com/Csontikka/microlink |
|
Already got it running on my esp. I'm now porting it to ESP-IDF 6, since microlink currently targets IDF5. |
|
Native Tailscale has landed 🎉 |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
Please consider adding native support for Tailscale to espkvm.
Possible Solution
Tailscale Node Integration: Embed or port the lightweight Tailscale node/client (e.g., using tailscale-embedded) into the firmware.
Web UI Configuration: Add a settings tab in the espkvm web interface to:
Enter an Auth Key.
Display connection status and assigned Tailscale IP (100.x.y.z).
Enable/disable the Tailscale interface.
Thanks !
All reactions