I tried to use

sudo service networking restart


sudo /etc/init.d/network restart

but they both crash the window manager and I can no longer use my keyboard for input into X.

when I use the /etc/init.d/ method it complains saying that I should use the service utility

e.g. service networking restart

but it crashes just the same.

Is there a GUI method of restarting networking?

  • Note that you might reanimate your keyboard, if you unplug and replug it - and it is hot pluggable, i.e. USB. Dec 19 '12 at 20:02
  • I also faced similar issue on Gnome 3 on Ubuntu 13.03. Screen disorted as top bar gone. Short keys not worked. As no menu/Activies shown I get no way to operate the system. Luckily console was opened already. So reboot command can be typed. Jul 22 '13 at 10:48
  • 1
    if you are looking for GUI method just open dash, type "Network" and select that. now press "On/Off" button to turn off and again click to on. your networking is restarted now. Sep 1 '14 at 18:28

18 Answers 18


For Desktops


sudo service network-manager restart


Ubuntu uses network-manager instead of the traditional Linux networking model. so you should restart the network-manager service instead of the network service. Or use ifup/down.

For Servers

Check this answer.

  • 8
    hmm, strange that restarting just networking breaks the system. Does it happen to you too or is it just me?
    – waspinator
    Dec 19 '12 at 21:25
  • 5
    @waspinator - it happens to me too. (FYI.)
    – Josh M.
    Dec 29 '13 at 3:31
  • 1
    Autocomplete give networking, however , the right cmd is network-manager Feb 2 '16 at 4:58
  • 1
    I wish I had tried Jorge's answer first.
    – Jonathan
    May 2 '17 at 15:26
  • 9
    As of 18.04.2 the answer is: systemctl restart systemd-networkd
    – Ejoso
    Feb 22 '19 at 2:41

For Servers

Restarting networking on a desktop machine will cause dbus and a bunch of service to stop and never be started again, usually leading to the whole system being unusable.

As Ubuntu does event based network bring up, there quite simply isn't a way to undo it all and redo it all, so a restart just isn't plain possible. The recommended way instead is to use ifdown and ifup on the interfaces you actually want to reconfigure:

sudo ifdown --exclude=lo -a && sudo ifup --exclude=lo -a

You could try

ifconfig eth0 down && ifconfig eth0 up

(or whatever your network interface is called) to restart the network.

  • 2
    ... as far as I know, this doesn't update the interface's config according to /etc/network/interfaces ... which you might want
    – moritz
    Mar 22 '15 at 11:24
  • 1
    When using sudo: sudo ifconfig eth0 down && sudo ifconfig eth0 up. Otherwise if you are connected over ssh, you will have to reboot machine.
    – tarkeshwar
    Apr 23 '15 at 11:06
  • after trying ifup/ifdown and the reg service networking call, this finally worked for me
    – Jon B
    Nov 9 '15 at 4:15
  • I think it's better than the accepted answer because ifup doesn't handle bonded interfaces correctly, while ifconfig does Jun 5 '18 at 12:49

ubuntu CLI: to restart the network service either

sudo /etc/init.d/networking restart


ifdown eth0
ifup eth0
  • 1
    This used to work for older kernels. Now it seems that do not work indeed. Prefered ifconfig eth0 down & ifconfig eth0 up
    – josircg
    Apr 3 '17 at 12:00
  • 1
    Beware not to use this command when connecting on remote machine. Jun 26 '17 at 9:05

For ubuntu server 18.04, this works :

sudo systemctl restart systemd-networkd
  • 3
    To new LTS 20.04 the comand above work, thanks!
    – LandiLeite
    Jul 30 '20 at 3:43
  • I confirm! This works on 20.04! Thanks! Aug 26 at 19:18

These days the most direct way to restart network services is to use systemd controls, namely the commandline systemd control utility systemctl. This command will restart the NetworkManager:

sudo systemctl restart NetworkManager.service

More information can be found here.

  • 1
    Try "systemctl restart networking.service" on server 16.04. Oct 30 '16 at 5:45
  • Don't need the ".service" part at the end. Oct 24 '18 at 17:34

service network-manager restart doesn't work:

stop: Unknown job network-manager
start: Unknown job network-manager

The only thing that works is:

ifconfig eth0 down
ifconfig eth0 up
sudo service network-manager restart


sudo service networking restart

Doesn't work on Ubuntu server 14.04


sudo ifdown eth0:0
sudo ifup eth0:0

Works. Change eth0:0 to your interface.


Try using the indicator (top menu bar) to disable and then enable networking.


I've got the same issue. Its a known bug https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1102507

Using service network-manager restart works through

  • This is solution which works always on 16.04. In my experience Ubuntu 16.04 have issues to restart Wi-Fi after returning from hibernation.
    – danijelc
    Feb 4 '17 at 15:19

If you can restart the network using the applet of NetworkManager, you do not need to restart NetworkManager itself (at least, most of the time).

In that case to restart all the connections, use this code from a shell or in a script:

nmcli nm enable false
sleep 5
nmcli nm enable true 

Details can be found in the NetworkManagar command-line interface manual page.

Notice that these commands acts as the applet, so they do not need any additional privilege (no sudo or whatever).


In ubuntu 14.04 they have a new "feature" that makes it impossible to restart. Force the interface down and up works.

  sudo ip link set eth0 down
  sudo ip link set eth0 up
  • 1
    This does not restart the network services, that is, no retry for DHCP addresses etc.
    – Samveen
    Aug 1 '14 at 19:01

I do not really think there's GUI method - by default at least.

I'm also not sure what do You mean by 'restarting networking service', but I feel that the following could help.

Before Ubuntu 16.04

sudo killall NetworkManager 

It kills NetworkManger which automatically restarts after this. It doesn't break the system.

Ubuntu 16.04

sudo killall NetworkManager && sudo NetworkManager

Based on my personal experience, it seems that in Ubuntu 16.04 NetworkManager does not always restart by itself and it's better to start it manually.

  • How is this better than sudo service network-manager restart and why?
    – Underverse
    Feb 4 '17 at 11:33
  • @Underverse, I believe that sudo service network-manager restart just didn't work for me when posting this answer.
    – kcpr
    Feb 5 '17 at 19:27

if ubuntu 14.04 Desktop or Server, you can restart you network by:

sudo -i
( ifdown $(ifquery --list -X lo|xargs echo) && ifup $(ifquery --list -X lo|xargs echo) )&
  • I get a ifdown: interface eth0 not configured RTNETLINK answers: File exists Failed to bring up eth0.
    – wolfgang
    Sep 22 '15 at 15:58

This uses Ubuntu's network-manager to disable, then enable eth0:

nmcli nm enable false eth0 && nmcli nm enable true eth0

If your connection has a different name, use it. You can learn your connections name by using the command:

nmcli c status

rmano's answer is brilliant. Solves so many issues.

Remark to improve: In U15 I experience a different syntax for nmcli:

For analysis do:

nmcli networking connectivity

To stop service do:

nmcli networking off

and to restart do:

nmcli networking on

No sudo required. Thanks rmano!


An alternative approach for the server (as of Ubuntu 18.04):

  1. Install ifupdown2 package : apt install ifupdown2

  2. Use service networking restart command


I am able to restart the network service on ubuntu with command.

 sudo systemctl restart network-manager

Not the answer you're looking for? Browse other questions tagged or ask your own question.