Skip to main content

Service and log command reference

Each page in the web interface is backed by one or more system services. When a feature misbehaves and the web interface does not say why, restarting the right service or reading its log directly is often the fastest way forward. This page is that lookup table. For the basics of the command line, see Command line and FAQ; for reading logs from the web interface, see Logs.

All commands run as root over SSH or the console.

Services by feature​

Feature (web interface)ServiceRestartFind it in the log
Firewall Rules, NAT, Zones & Policiesfirewall/etc/init.d/firewall reload (rules only) or restartthe zone name, or the log prefix set on the rule
DNS & DHCPdnsmasq/etc/init.d/dnsmasq restartdnsmasq-dhcp
Application control (DPI)netifyd, dpi/etc/init.d/netifyd restart, /etc/init.d/dpi restartnetifyd
Intrusion prevention (IPS/IDS)snort/etc/init.d/snort restartsnort
DNS filteringns-flashstart/etc/init.d/ns-flashstart restartns-flashstart
IP & geo blockingbanip/etc/init.d/banip restartbanIP
SD-WANmwan3/etc/init.d/mwan3 restartmwan3
Captive portaldedalo, dedalo_users_auth/etc/init.d/dedalo restartdedalo
OpenVPN (remote access, site-to-site)openvpn/etc/init.d/openvpn restartopenvpn
IPsec tunnelsipsec/etc/init.d/ipsec restartcharon
WireGuardmanaged as a network interfaceifdown <interface> then ifup <interface>wireguard
MAC bindingns-binding/etc/init.d/ns-binding restartns-binding
Port forwarding via NAT reflectionns-netmap/etc/init.d/ns-netmap restartns-netmap
Central management (controller connection)ns-plug/etc/init.d/ns-plug restartns-plug — see Controller registration troubleshooting
High availabilitykeepalived, managed via ns-ha-configdo not restart keepalived directly, use ns-ha-config, see High availabilitykeepalived
Web interfacens-ui/etc/init.d/ns-ui restartns-ui
System log forwardingrsyslog/etc/init.d/rsyslog restart—
MSP monitoring agentcheck_mk_agent/etc/init.d/check_mk_agent restartcheck_mk_agent

A restart interrupts the service briefly; a reload, where available, applies configuration without a full restart and is worth trying first on a production unit.

Diagnostic commands beyond restart and logread​

These read the live state of a service instead of, or in addition to, its log.

TaskCommand
SD-WAN link and policy statemwan3 status, mwan3 interfaces
IPsec tunnel stateipsec statusall
WireGuard peer state and handshakeswg show
IPS: service status, memory use, active rule counterssnort-mgr status
IPS: validate the rendered configuration without applying itsnort-mgr check
IPS: report on recent incidentssnort-mgr report, add -n 10 for only the ten most frequent
OpenVPN: list connected clients from the management socketopenvpn-status <path-to-socket> — find the socket first with find /var/run /var/etc -iname '*openvpn*.sock' 2>/dev/null
Controller connection stateubus call ns.plug status
High availability pair statens-ha-config status

Forcing DPI signature and rule updates​

The application control database and its license check run on their own schedule via cron. To force an update immediately instead of waiting:

/etc/init.d/dpi-data-update start # application signature database
/etc/init.d/dpi-license-update start # subscription license check

For the IPS ruleset, use snort-mgr update-rules instead of restarting a service; it downloads the ruleset and rewrites the configuration snort reads on its next start.

Reading a service's own configuration as UCI sees it​

Every service above is configured through /etc/config/<name>, usually with the same name as the UCI package (for example uci show dpi, uci show mwan3, uci show snort). Not all service and UCI package names match exactly — ns-flashstart and banip do — check ls /etc/config/ if a name from this table returns nothing. For what UCI is and how to use it beyond just reading it, see What is UCI, and why it matters.