SunLionet is a local-first, bundle-based privacy and resilient communication system designed for high-risk, restricted networks.
It ships as:
Migration note: this repository is still named SUNLIONET-agent during the transition, so some internal identifiers and older release artifacts may still use legacy SUNLIONET-* naming.
Minimal flow (example for Linux amd64):
VERSION="v0.3.0-rc1"
BASE_URL="https://github.com/SunLionet/Iran-Agent-Vpn/releases/download/${VERSION}"
curl -fL -O "${BASE_URL}/sunlionet-inside-${VERSION}-linux-amd64.tar.gz"
curl -fL -O "${BASE_URL}/sunlionet-inside-${VERSION}-linux-amd64.tar.gz.sha256"
sha256sum -c "sunlionet-inside-${VERSION}-linux-amd64.tar.gz.sha256"
tar -xzf "sunlionet-inside-${VERSION}-linux-amd64.tar.gz"
sudo ./install-linux.sh inside
Import a bundle and connect:
sunlionet-inside \
--import ./bundle.snb.json \
--trusted-signer-pub-b64url "<PASTE_TRUSTED_SIGNER_PUB_B64URL>" \
--age-identity "<PASTE_AGE_SECRET_KEY>" \
--master-key "<32_BYTE_HEX_MASTER_KEY>" \
--probe-url "https://example.com"
What to expect:
[SunLionet] Starting agent...[Profile] Selected: ...[Connection] Testing...[Connection] SUCCESS (when probe is enabled and succeeds)Start here:
SunLionet Dashboard can show the local runtime state if SunLionet Inside is running with the runtime API enabled.
sunlionet-inside --runtime-api-addr 127.0.0.1:8080 --runtime-api-keepalive ...
/dashboard/runtimeIf you see “No active SunLionet runtime detected”, check that:
127.0.0.1:<port> (localhost-only).