How do I set a static IP in Ubuntu?

Question

I am a new with Linux, having years experience with Windows servers/desktops and am having issues setting a static IP. I am using a method used for previous versions of Ubuntu, which doesn't seem to work with 16.04

I have used the command sudo nano /etc/network/interface and added the following

iface enp0s25 inet static
address 10.10.8.2
netmask 255.255.0.0
gateway 10.10.1.1
dns-nameservers 8.8.8.8 8.8.4.4

I have rebooted the system and the Ethernet is pretty much dead, ping doesn't work at all. I have tried to modify /etc/NetworkManager/NetworkManager.conf and made the following changes

#dns=dnsmasq (comment out the dnsmasq)
[ifupdown]
managed=true (changed from false)

With this I can get Ethernet to work sporadically, however it eventually fails.

I have tried this configuration on two other machines plus a virtual machine as well and all have the same results. I can confirm these settings work fine when I install Windows on any of these machines. As well when I let DHCP auto configure, everything works fine no issues.

I figure I am missing something here, setting up a static IP should not be difficult at all.

the only thing I notice and it may have just been a typo here but I would change the Dns-nameservers to dns-nameservers probably not going to do anything to solve this issue but may stop other issues from happening — John Orion, May 02 '16 at 00:20
Dns-nameservers is acceptable syntax wise so it shouldn't be an issue. When it was working with DHCP, did you run an ifconfig to check the interface name or did you assume it was enp0s25? Also do you have an auto enp0s25 at the top of your config file? If you don't its possible that the interface is just not coming up on boot. — Andrew, May 02 '16 at 00:30
Please edit your question and post the exact content of your /etc/network/interfaces file. While editing your message, highlight the text of this file, then click on the {} code link on the top of the message editor so that it will properly format the text making it easier for us to read the content. Also do execute this command ip address and perform the same steps to {} (code format) that output. — L. D. James, May 02 '16 at 04:05

lewis4u · Accepted Answer · 2019-02-19T23:32:58.343

92

I had the same problem and this was my solution:

sudo nano /etc/network/interfaces

and paste (altering for your network) this under # The primary network interface:

auto enp0s25
iface enp0s25 inet static
address 192.168.0.16
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameservers 8.8.4.4 8.8.8.8

You can get correct interface name using Terminal command ifconfig -a on ubuntu 16.04 or ip address on 18.04+

Shutdown your Virtual Machine and then!!! Go to network settings and click on refresh MAC address button a few times :)

and start your VM and you should get internet!

UPDATE 20.02.2019

For ubuntu 18.04+ you need to edit this file

/etc/netplan/50-cloud-init.yaml

network:
    ethernets:
        enp0s3:
            addresses: [192.168.0.55/24]
            gateway4: 192.168.0.1
            dhcp4: no
            nameservers:
              addresses: [1.1.1.1,8.8.8.8]
            optional: true
    version: 2

edited Feb 19 '19 at 23:32

answered May 04 '16 at 20:20

lewis4u

4,866

2

Great thanks I appreciate it. It seems to work now, with no problems. It is very solid right now! – TeeStar May 07 '16 at 02:07
In addition to the dns-nameservers fix, I had to use this fix: http://askubuntu.com/questions/574569/apt-get-stuck-at-0-connecting-to-us-archive-ubuntu-com/575130#575130 My ISP is monkeybrains.net. – BSalita Aug 22 '16 at 23:38
does not work in my VMWare player with ubuntu16.04 – ZhaoGang Mar 08 '21 at 06:26
I suppose you didn't configure the network properly in VM-Ware Player.... but your bigger problem is: Why do you still use Ubuntu 16.04... The support is "end of life"... – lewis4u Mar 08 '21 at 07:33

score 64 · Answer 2 · answered Nov 15 '16 at 09:50

64

Setting the static IP address as above in the accepted answer here works, but one has to flush the old IP addr setting and then restart networking.service:

sudo ip addr flush enp0s25
sudo systemctl restart networking.service

Then verify it is correct:

ip add

answered Nov 15 '16 at 09:50

Grant

740

2

The flush was necessary to avoid the old address being present on the interface (based on ip addr). The systemctl restart works too, though ifdown and ifup on the interface will work more selectively. – RichVel Nov 28 '16 at 13:28
2

thx @Grant. adding flush made this work – Paweł Madej Feb 01 '17 at 13:19
3

In Ubuntu 16.04 and newer flush is necessary! – Diego Duarte May 02 '17 at 12:05

score 6 · Answer 3 · edited Nov 28 '17 at 17:32

6

# interfaces(5) file used by ifup(8) and ifdown(8)
# auto lo
# iface lo inet loopback
auto enp2s0 
iface enp2s0 inet static
    address 172.16.9.124
    netmask 255.255.240.0
    gateway 172.16.0.9
dns-nameservers 8.8.8.8

edited Nov 28 '17 at 17:32

David Foerster

36,264
56
94
147

answered May 12 '16 at 09:34

rajan

61

1

ifcace should be iface on line 5 – twoleggedhorse Jun 28 '17 at 14:33
@twoleggedhorse: Fixed the typo for the answer but I had to add a few # in the first line because you cannot have an edit without at least 6 changed characters that are not whitespace – Andrei Rînea Nov 28 '17 at 17:11

score 5 · Answer 4 · edited Oct 14 '16 at 23:18

5

sudo vim /etc/network/interfaces

    auto lo
    iface lo inet loopback
    auto eth0
    iface eth0 inet static
    address 192.168.1.10
    gateway 192.168.1.1
    netmask 255.255.255.0
    dns-nameservers 8.8.8.8

sudo ifdown eth0 && sudo ifup eth0

edited Oct 14 '16 at 23:18

Kevin Bowen

19,615
55
79
83

answered Oct 14 '16 at 01:41

lanni654321

151
1
1

10

Hi @lanni654321, maybe you should edit your answer and add a few word, briefly explaining what you are doing and why? i think that would make your answer even more helpful, what do you think? – Tshilidzi Mudau Oct 14 '16 at 06:58

score 3 · Answer 5 · answered Jul 18 '16 at 08:03

I had the same problem and the solution "was" simply... for me, at least.

auto ens160
iface ens160 inet static
address 172.31.0.164/22
netmask 255.255.252.0
gateway 172.31.0.2
network 172.31.0.0
broadcast 172.31.3.255
dns-nameservers 172.31.0.21 172.31.0.18

#Add internal route
up route add -net 172.16.168.0/21 gw 172.31.0.20 dev ens160

And, create an empty file with the name of the network interface in:

~$ touch /etc/network/interfaces.d/ens160

It works...

score 2 · Answer 6 · edited Oct 24 '17 at 10:42

2

I had the same problem and this was my solution: Remove all empty lines at the end of the file /etc/network/interface.

edited Oct 24 '17 at 10:42

Videonauth

33,355
17
105
120

answered Oct 24 '17 at 10:26

AkYu

21

score 1 · Answer 7 · edited Mar 29 '19 at 22:42

1

If your server is showing that old IP as well as new assigned IP, simply restart your server. It will automatically flush old IP and persist the new one.
And if you don't want to restart your server, use this command:

sudo ip addr flush <your-interface-here>

edited Mar 29 '19 at 22:42

Philippe Delteil

1,668

answered Mar 29 '19 at 17:04

Sunrays

11

score 1 · Answer 8 · answered Jul 16 '19 at 03:18

Run this simple commands to see if your network interface(s) are set to come up when the machine boots / restarts.

grep "auto" /etc/network/interfaces

If no lines are printed to standard output, then open /etc/network/interfaces with a text editor (vi, nano, sed) and hopefully you will see something similar to the image below below.

Obviously, if grep did not return any lines to the terminal window, the format of your /etc/network/interfaces cannot be very similar at all. :-) However, follow the format of the auto lines.

auto lo
(Loopback configuration follows)
.
.
.

auto enp0s3
(primary interface configuration follows)
.
.
.

====================

Now, on your machine.

auto yourInteraceNameHere
(your interface configuration follows)
.
.
.

Don't know which interface names are available? Run this command.

ifconfig -a

The following command will return just the names of the network interfaces.

ifconfig -a | grep encap | awk {'print $1'}

score 0 · Answer 9 · answered Feb 19 '19 at 23:41

0

I used to set static IPs on my Ubuntu machines and then I noticed that I can just assign the IP address using my router. This may be the simplest solution. Just log in to your router, find the attached devices, and assign the IP address there.

answered Feb 19 '19 at 23:41

Ole

1,487

How do I set a static IP in Ubuntu?

9 Answers9

UPDATE 20.02.2019

Linked

Related