Loading HoneyMesh...
Loading HoneyMesh...
Ubuntu App Center beta
Set up the free, local Console and inspect what it can observe. The published Snap is an observation-only beta for AMD64. It does not install HoneyMesh Core, attach XDP, block traffic, or protect a host by itself. The installed package was smoke-tested on Ubuntu 24.04 AMD64; use a noncritical host for evaluation.
In Ubuntu App Center, search for HoneyMesh Console (Snap name network-decode-console) and select the beta channel. Or install it in a terminal:
sudo snap install network-decode-console --betaThe service starts automatically. Check that it is running:
snap services network-decode-console
curl http://127.0.0.1:8787/healthThe Snap Store verifies and updates installed Snaps. A separate downloaded package or checksum file is not needed for this Store install.
Open http://127.0.0.1:8787 in a browser on the installed host. The Console listens on loopback only. In your own terminal, read the locally generated one-time setup token:
sudo python3 -c 'import json; print(json.load(open("/var/snap/network-decode-console/common/private/credentials.json"))["adminToken"])'Paste it into Create admin account and choose a unique password of at least 16 characters. After setup, sign in with that password. The setup token is not a software license or a HoneyMesh agent operator token. Keep it out of screenshots, support tickets, and public messages.
To allow host socket and interface snapshots, connect the Snap's observation interface:
sudo snap connect network-decode-console:network-observeStrict Snap confinement can limit which host /proc data is visible. Treat the displayed data as a bounded snapshot, not a complete inventory.
If you see Agent not linked or not_configured, the Console has no certificate pin for a local HoneyMesh Core agent. This does not mean the agent is stopped. The Snap does not install Core or discover it automatically. You can use local Console observations without linking it.
To show an existing agent's mode and health, first confirm systemctl is-active honeymesh.service reports active. On a host using the standard Core certificate path, run these commands in your own terminal. They read the installed agent's trusted local certificate, save only its public fingerprint in the Snap's private data, and restart the Console:
sudo sh -c 'set -eu
cert=/etc/honeymesh/certs/node/node.crt
target=/var/snap/network-decode-console/common/private/agent-public.json
fingerprint=$(openssl x509 -in "$cert" -noout -fingerprint -sha256 | cut -d= -f2)
test -n "$fingerprint"
printf "{\"url\":\"https://127.0.0.1:8443\",\"fingerprint_sha256\":\"%s\"}\n" "$fingerprint" > "$target"
chmod 600 "$target"'
sudo snap restart network-decode-consoleReload http://127.0.0.1:8787. A successful link shows Agent connected and the agent's current mode, such as TEST. If the agent certificate rotates, repeat the pin step using the new local certificate. Do not copy an unverified fingerprint from a network response. Linking gives the Console read-only agent status in this Snap; it does not enable host writes.
This toast in older betas can mean the Snap lacks permission to read Linux socket data. If the header says Agent connected and TEST, the Core agent is reachable; starting npm start is not the fix. Check the observation interface:
snap connections network-decode-consoleFind the network-observe row. If its Slot is -, connect it and reload the Console page:
sudo snap connect network-decode-console:network-observeThe Slot should then read :network-observe. If the old toast persists, refresh to the current beta and reload again:
sudo snap refresh network-decode-console --betaThis observation interface affects socket and interface snapshots; it is separate from the certificate-pinned Core agent connection. Current betas report a missing telemetry permission directly and keep agent status visible.
If the page does not load, check the service and its recent logs, then restart it if needed:
snap services network-decode-console
snap logs network-decode-console -n 50
sudo snap restart network-decode-consoleUse sudo snap remove --purge network-decode-console only when you want to remove the Snap and its local account data. For security reports, use security@network-decode.com; for other issues, use the public issue tracker without including tokens or private host data.
Console package: Snap Store listing. For actual host protection and trusted mesh setup, review the separate Core retrofit guide.