For users managing servers, routers, and self-hosted services. The core handles configurations, rules, and proxy connections, but doesn’t include the full GUI provided by the clients above. Most desktop and mobile users should choose a GUI client from their platform section.
Before deploying the core
Don’t choose a router download based on its brand alone. Check the CPU architecture, endianness, and floating-point support reported by its firmware. MIPS and MIPSel are different targets, and softfloat has specific runtime requirements. If you’re unsure, check the firmware documentation before adding an incompatible binary to a startup service.
.gz is a single-file compression format. After decompressing it, set the executable permission and prepare a configuration directory. Extract Windows ZIP files before running them. DEB is a package format; after installation, check the file locations and service instructions rather than assuming every package creates the same service automatically.
Before starting the core, validate the configuration syntax and check that its listening ports aren’t already in use. Bind the external controller to a loopback address where possible. If you need remote access, set up access controls separately; don’t expose the management interface directly to the public internet. For detailed troubleshooting, see the troubleshooting guide.
