Source linked

Jailbroken Kindle Now Runs Tailscale Proxy and TUN Modes

tailscale.com@systems_wire3 hours ago·Systems Engineering·2 comments

An updated KUAL app enables SOCKS5/HTTP proxy on port 1055 and full TUN mode on select Kindles, letting KOReader and other apps reach tailnet devices.

tailscalekindlejailbreakkoreadervpnmesh networking

KOReader on a jailbroken Kindle can now reach your Calibre server at 100.x.y.z over Tailscale, thanks to an updated KUAL app by greywolf1499 that adds SOCKS5 and HTTP CONNECT proxy modes. Earlier Tailscale builds for Kindles ran in userspace mode, leaving Kindle apps blind to anything beyond the device’s own Tailscale IP. You could SSH in over Tailscale, but launching KOReader and pointing it at a tailnet address? Dead end.

What the Updated KUAL App Unlocks

Mitanshu Sukhwani’s original Tailscale port got the Kindle onto your tailnet—green dot in admin console, reachable by Tailscale IP, SSHable without USB networking. The missing piece was routing app traffic through Tailscale. greywolf1499’s KUAL update fixes that with two proxy modes:

  • SOCKS5 on 127.0.0.1:1055
  • HTTP CONNECT on port 1056

Start Tailscale in proxy mode, set KOReader’s proxy to 127.0.0.1:1055, and the tailscaled daemon forwards connections to any tailnet IP. For Kindles that support it, a full TUN mode now makes Tailscale networking work at the device level, no app configuration needed.

How the Proxy Mode Works

Walking through the flow: KOReader asks the Kindle’s root OS how to reach 100.x.y.z. Without Tailscale routing, the OS shrugs. With the proxy, KOReader talks to the local tailscaled daemon, which knows the tailnet. The daemon completes the handshake, and data flows to your Calibre, Wallabag, or Audiobookshelf server. Two proxy flavors (SOCKS5 and HTTP CONNECT) cover apps that prefer one or the other.

Practical uses go beyond e-books: Bluetooth keyboard + kterm to SSH into other tailnet devices, accessing minimalist dashboards in the Kindle browser, or syncing reading progress with Readest. None of this demands much CPU from the Kindle’s anemic processor—the proxy is lightweight.

The KOReader Plugin Route

If you don’t need your Kindle itself to be a tailnet node, Victoria Riley Barnett’s KOReader plugin offers a lighter alternative. It injects the same proxy interfaces (127.0.0.1:1055 for SOCKS5, 1056 for HTTP CONNECT) directly into KOReader, and claims support for Kobo and PocketBook devices too. Installation is straightforward: copy the plugin into KOReader’s plugins directory, run “Install/Update Tailscale” from the menu, drop in a Tailscale auth key, and toggle it on. Pair it with the SyncThing plugin for KOReader and you’ve got a reading device that’s also a self-synchronizing tailnet client.

Whether you use the KUAL app or the KOReader plugin, the effect is the same: one of the weakest computers you own now pulls its weight on your tailnet. If you’ve got a jailbroken e-paper device gathering dust, this is the moment to dig it out and try turning it into a thin client for your tailnet.


Source: More Tailscale tricks for your jailbroken Kindle
Domain: tailscale.com

Read original source ->

External source stays available while the OJO article and comment thread stay local.

Comments load interactively on the live page.