Existing infrastructure
Protect a server you already run.
HoneyMesh can add local defense to a compatible Linux host without replacing its hardware or applications. The first step is checking the host and proving recovery, then enabling one narrow control at a time.
Available now
Core 2.3.6 RC6 pilot for noncritical Ubuntu 24.04 AMD64
Download the Debian package and its matching checksum file. Run sha256sum -c SHA256SUMS in their directory, then follow the release notes. Start in TEST with no protected interface or sharing, and keep provider-console access. General production and broader host support remain unqualified.
SHA-256: fc3699945f5ea2904bffa22dd8ff5bbc074ba7b4fc9a3e8b9245c8ffd748dbf6
Check the fit before installing
Host support
Record the distribution, CPU architecture, kernel, network namespace, and ingress interface. The Core service requires Linux kernel 5.8 or newer; current package evidence centers on Ubuntu 24.04 AMD64. Treat other combinations as source builds requiring their own test.
Recovery access
Keep a provider console or another out-of-band route. Save the current firewall and interface configuration before installing or attaching XDP.
Local identity
Create this installation's admin credentials and certificates locally. Keep its private key, admin token, and runtime state on the host.
TEST first
Start with sharing off and no unreviewed public interface attached. Check health, expected traffic, and source attribution before any enforcement change.
An older server with an unsupported kernel is not a qualified Core host. If it runs a compatible persistent Node.js application, Node Guard can provide process-local controls without XDP. Otherwise, keep its existing protections while a supported deployment path is tested.
A safe retrofit sequence
- 1 / 5
Inventory
Choose one noncritical existing host. Record its kernel, interface, management path, and normal service traffic.
- 2 / 5
Download and verify
For noncritical Ubuntu 24.04 AMD64, get the Core pilot package and SHA256SUMS from the same release. Verify the hash and read the version-matched notes before installing.
- 3 / 5
Observe locally
Create unique local credentials, start in TEST, select only the intended interface, and confirm the control source stays reachable.
- 4 / 5
Run a bounded canary
With an operator present, test one known source, short expiry, manual release, and rollback. Return to TEST after the exercise.
- 5 / 5
Connect trusted peers
Only after local checks, configure explicit TLS trust and a cluster identity or enroll into your own Exchange. Begin with observation sharing.
What is available today
Core, Node, Node Guard, Exchange, and Firewall Console source are public and free. The Core pilot above is installable on its stated noncritical host profile; a general installer and broad older-system support matrix remain in progress. Network Decode keeps its website and operational records separately from the public source.