| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| caprock_0.50.0_linux_amd64.tar.gz | 2026-09-03 | 8.7 MB | |
| caprock_0.50.0_linux_arm64.tar.gz | 2026-09-03 | 8.1 MB | |
| checksums.txt | 2026-09-03 | 600 Bytes | |
| caprock_0.50.0_darwin_amd64.tar.gz | 2026-09-03 | 8.8 MB | |
| caprock_0.50.0_darwin_arm64.tar.gz | 2026-09-03 | 8.3 MB | |
| caprock_0.50.0_windows_amd64.zip | 2026-09-03 | 8.9 MB | |
| caprock_0.50.0_windows_arm64.zip | 2026-09-03 | 8.1 MB | |
| README.md | 2026-09-03 | 1.2 kB | |
| v0.50.0 source code.tar.gz | 2026-09-03 | 6.2 MB | |
| v0.50.0 source code.zip | 2026-09-03 | 6.5 MB | |
| Totals: 10 Items | 63.5 MB | 0 | |
Added
-
Let a tablet in from the dashboard, without a terminal. Reading Caprock from a phone shipped needing
caprock up --lan, which requires a terminal on the machine — and the person who wants this is holding the tablet. It is a button on the status screen now, with an off switch beside the device list. The flag still works for a machine administered over SSH. Unchanged: it is off again when Caprock restarts, and paired devices are kept. -
Caprock uses a Tailscale address when there is one, and says which kind of address you have. A LAN address works when the other device is on the same wifi and never from mobile data — no setting changes that, because the packets do not arrive. The panel said nothing about it, so the honest conclusion from a tablet on mobile data was that the feature is broken.
It now names the difference under the address, and points at Tailscale for the case a LAN address cannot serve. Tailscale's own range (100.64.0.0/10) is not "private" by the Go standard library's definition, so the one address that solves the problem was being filtered out as public; it is preferred over a LAN address when both exist.
