Hands-on steps to bring interfaces and daemons back without guesswork. 16.11.2025 | reading time: 2 min A network service restart is the quickest way to recover from a misconfigured interface or a hung network daemon; this page shows concrete commands to run, what to expect, and safer alternatives to avoid cutting your own SSH session. Quick recovery example Restart NetworkManager and check the interface with these commands and expected output. ```sudo systemctl restart NetworkManager $ ip addr show eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 inet 192.0.2.10/24 brd 192.0.2.255 scope global eth0``` Run the restart, then verify the address and state to confirm connectivity returned. Reload versus restart Prefer a reload when the daemon supports it to avoid tearing down active connections; for example try `sudo systemctl reload NetworkManager` first and fall back to `restart` if configuration changes require a full restart; when working over SSH, bring up an alternate console or schedule the restart with `at` to avoid locking yourself out. Other useful commands If systemd units are not present use legacy tools: `sudo ifdown eth0 && sudo ifup eth0` or manipulate the device directly with `sudo ip link set eth0 down` and `sudo ip link set eth0 up`; for NetworkManager use `nmcli` to bring connections up or down without restarting the entire daemon. Finish and learn more Practice these commands in a safe lab, simulate lost connectivity, and learn how each method affects routing and DHCP behavior; to build deeper competence consider formal certification and intensive exam preparation at bitsandbytes.academy. Join Bits & Bytes Academy First class LINUX exam preparation. network troubleshooting utilities
