Open your terminal and navigate to the directory containing the ncontrol.deb file. Run the following command to view its metadata:
dpkg --info ncontrol.deb
Pay close attention to the output:
| Symptom | Quick Fix |
|---------|-----------|
| Daemon fails to start | Run journalctl -u ncontrol -b to view logs. Common cause: missing libpcap version; reinstall with apt-get install --reinstall libpcap0.8. |
| Traffic shaping not applied | Verify that the interface name matches (eth0 vs ens33). Use ncontrolctl show shaping to confirm the policy is loaded. |
| REST API returns 403 | Check the token you are using. Regenerate a fresh token with ncontrolctl token generate. |
| High CPU usage | Enable the cpu_limit option in the config (global.cpu_limit: 0.7) or upgrade to a kernel with eBPF offload (v5.10+). |
| Logs fill up the disk | Adjust logrotate config in /etc/logrotate.d/ncontrol (e.g., keep 7 days, compress). | ncontrol deb
ncontrol --mem-offset +800
[Unit] Description=ncontrol daemon After=network.target
[Service] Type=simple ExecStart=/usr/bin/ncontrol --daemon Restart=on-failure Open your terminal and navigate to the directory
[Install] WantedBy=multi-user.target
If you want, I can:
If you're looking for information on how to control or manage network services or packages, particularly on a Debian-based system, here are some general insights:
sudo dpkg --purge package-name
or
sudo apt purge package-name
Cause: The ncontrol deb installed the binary but not the service file, or the service file has a different name. Solution:
The naive approach (dpkg -i) often fails due to missing dependencies. Here is the robust, two-step method for installing the ncontrol deb. Pay close attention to the output: | Symptom