Mdthbs

How can I describe being temporarily stupid?

How do I intentionally fragment a SQL Server Index?

Gofer work in exchange for Letter of Recommendation

Can a Beast Master ranger choose a swarm as an animal companion?

Changing a TGV booking

How can I pack my food so it doesn't smell?

Can others monetize my project with GPLv3?

Have only girls been born for a long time in this village?

Is "stainless" a bulk or a surface property of stainless steel?

Interaction between Ethereal Absolution versus Edgar Markov with Captivating Vampire

What animal has fat with the highest energy density?

Why is su world executable?

Is a butterfly one or two animals?

Are there any OR challenges that are similar to kaggle's competitions?

Are there categories whose internal hom is somewhat 'exotic'?

Convert HTML color to OLE

Land Registry Clause

How do slats reduce stall speed?

Unity: transform.LookAt(target) not "looking at" target?

Moons that can't see each other

Metal that glows when near pieces of itself

Does the Symbiotic Entity damage apply to a creature hit by the secondary damage of Green Flame Blade?

Are there any legal requirements concerning airline pilots and their watches?

Default camera device to show screen instead of physical camera

problem with interface with ip static in ubuntu 18.04

Ubuntu 15.10 Network Interfaces NameSetting Static IP with Predictable network interfaceIncrease wireless interface link speedHow can I forward traffic across two Ethernet cards?How do I set additional IP addresses on an existing interface in Debian 9?Problem upgrading Ubuntu to version 18.04QEMU Deb9 guest graphical install fails to get DHCP reply during installSSID of hostapd is not visibleWeird DNS problem with Ubuntu 18.04Can you assign different DNS servers to different network interfaces?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

2

On ubuntu 16.04, I had the interfaces file with the following information:

sudo nano /etc/network/interfaces



# interfaces(5) file used by ifup(8) and ifdown(8)

auto lo

iface lo inet loopback



# Public Interface (Static IP)

auto enp2s0

iface enp2s0 inet static

   address 192.168.88.13

   gateway 192.168.88.1 

   netmask 255.255.255.0

   broadcast 192.168.88.255

   dns-nameservers 8.8.8.8 8.8.4.4

   dns-search 8.8.8.8 8.8.4.4

   dns-domain 8.8.8.8 8.8.4.4



# Local Network Interface (Static IP)

auto enp2s1

iface enp2s1 inet static

   address 192.168.0.10

   netmask 255.255.255.0

   broadcast 192.168.0.255

   network 192.168.0.0

And work fine. Now update Ubuntu 18.04 and doesn't work enp2s0 (first interface public)

ifconfig



enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.88.13  netmask 255.255.255.0  broadcast 192.168.88.255

        ether 94:18:82:0c:00:01  txqueuelen 1000  (Ethernet)

        RX packets 570  bytes 53571 (53.5 KB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 79  bytes 11201 (11.2 KB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 16  

Only work in dhcp:

auto enp2s0

iface enp2s0 inet dhcp

What changed with the new version that does not accept the previous configuration? Thanks

ubuntu network-interface

share|improve this question

edited May 25 '18 at 16:43

ajcg

asked May 25 '18 at 16:35

ajcgajcg

27944 silver badges1717 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Ubuntu 18.04 does not use the legacy /etc/network/interfaces. See "How to configure static IP address on Ubuntu 18.04" for a brief tutorial.
  
  – AlexP
  May 25 '18 at 16:56
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  sorry, but in "How to configure static IP address on Ubuntu 18.04" they explain that you can still use. And the enp2s1 interface works. Also, hide the procedure described (sudo ip a flush enp0s3 && sudo systemctl restart networking.service) and it works at the moment. Stop working when restarting
  
  – ajcg
  May 25 '18 at 20:21
  
  
  

  
  
  
  

add a comment | 

2

On ubuntu 16.04, I had the interfaces file with the following information:

sudo nano /etc/network/interfaces



# interfaces(5) file used by ifup(8) and ifdown(8)

auto lo

iface lo inet loopback



# Public Interface (Static IP)

auto enp2s0

iface enp2s0 inet static

   address 192.168.88.13

   gateway 192.168.88.1 

   netmask 255.255.255.0

   broadcast 192.168.88.255

   dns-nameservers 8.8.8.8 8.8.4.4

   dns-search 8.8.8.8 8.8.4.4

   dns-domain 8.8.8.8 8.8.4.4



# Local Network Interface (Static IP)

auto enp2s1

iface enp2s1 inet static

   address 192.168.0.10

   netmask 255.255.255.0

   broadcast 192.168.0.255

   network 192.168.0.0

And work fine. Now update Ubuntu 18.04 and doesn't work enp2s0 (first interface public)

ifconfig



enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.88.13  netmask 255.255.255.0  broadcast 192.168.88.255

        ether 94:18:82:0c:00:01  txqueuelen 1000  (Ethernet)

        RX packets 570  bytes 53571 (53.5 KB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 79  bytes 11201 (11.2 KB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 16  

Only work in dhcp:

auto enp2s0

iface enp2s0 inet dhcp

What changed with the new version that does not accept the previous configuration? Thanks

ubuntu network-interface

share|improve this question

edited May 25 '18 at 16:43

ajcg

asked May 25 '18 at 16:35

ajcgajcg

27944 silver badges1717 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Ubuntu 18.04 does not use the legacy /etc/network/interfaces. See "How to configure static IP address on Ubuntu 18.04" for a brief tutorial.
  
  – AlexP
  May 25 '18 at 16:56
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  sorry, but in "How to configure static IP address on Ubuntu 18.04" they explain that you can still use. And the enp2s1 interface works. Also, hide the procedure described (sudo ip a flush enp0s3 && sudo systemctl restart networking.service) and it works at the moment. Stop working when restarting
  
  – ajcg
  May 25 '18 at 20:21
  
  
  

  
  
  
  

add a comment | 

On ubuntu 16.04, I had the interfaces file with the following information:

sudo nano /etc/network/interfaces



# interfaces(5) file used by ifup(8) and ifdown(8)

auto lo

iface lo inet loopback



# Public Interface (Static IP)

auto enp2s0

iface enp2s0 inet static

   address 192.168.88.13

   gateway 192.168.88.1 

   netmask 255.255.255.0

   broadcast 192.168.88.255

   dns-nameservers 8.8.8.8 8.8.4.4

   dns-search 8.8.8.8 8.8.4.4

   dns-domain 8.8.8.8 8.8.4.4



# Local Network Interface (Static IP)

auto enp2s1

iface enp2s1 inet static

   address 192.168.0.10

   netmask 255.255.255.0

   broadcast 192.168.0.255

   network 192.168.0.0

And work fine. Now update Ubuntu 18.04 and doesn't work enp2s0 (first interface public)

ifconfig



enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.88.13  netmask 255.255.255.0  broadcast 192.168.88.255

        ether 94:18:82:0c:00:01  txqueuelen 1000  (Ethernet)

        RX packets 570  bytes 53571 (53.5 KB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 79  bytes 11201 (11.2 KB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 16  

Only work in dhcp:

auto enp2s0

iface enp2s0 inet dhcp

What changed with the new version that does not accept the previous configuration? Thanks

ubuntu network-interface

share|improve this question

edited May 25 '18 at 16:43

ajcg

asked May 25 '18 at 16:35

ajcgajcg

27944 silver badges1717 bronze badges

sudo nano /etc/network/interfaces



# interfaces(5) file used by ifup(8) and ifdown(8)

auto lo

iface lo inet loopback



# Public Interface (Static IP)

auto enp2s0

iface enp2s0 inet static

   address 192.168.88.13

   gateway 192.168.88.1 

   netmask 255.255.255.0

   broadcast 192.168.88.255

   dns-nameservers 8.8.8.8 8.8.4.4

   dns-search 8.8.8.8 8.8.4.4

   dns-domain 8.8.8.8 8.8.4.4



# Local Network Interface (Static IP)

auto enp2s1

iface enp2s1 inet static

   address 192.168.0.10

   netmask 255.255.255.0

   broadcast 192.168.0.255

   network 192.168.0.0

ifconfig



enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.88.13  netmask 255.255.255.0  broadcast 192.168.88.255

        ether 94:18:82:0c:00:01  txqueuelen 1000  (Ethernet)

        RX packets 570  bytes 53571 (53.5 KB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 79  bytes 11201 (11.2 KB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 16  

auto enp2s0

iface enp2s0 inet dhcp

share|improve this question

edited May 25 '18 at 16:43

ajcg

asked May 25 '18 at 16:35

ajcgajcg

27944 silver badges1717 bronze badges

share|improve this question

edited May 25 '18 at 16:43

ajcg

asked May 25 '18 at 16:35

ajcgajcg

27944 silver badges1717 bronze badges

asked May 25 '18 at 16:35

ajcgajcg

27944 silver badges1717 bronze badges

asked May 25 '18 at 16:35

ajcgajcg

27944 silver badges1717 bronze badges

2 Answers
2

active

oldest

votes

-1

Ubuntu 18.04 does not use the legacy configuration file /etc/network/interfaces. Instead of the old ifupdown mechanism, Ubuntu 18.04 uses Netplan, as documented in the Release Notes. See "How to configure static IP address on Ubuntu 18.04" for a brief tutorial:

• 
  

  For Ubuntu 18.04 Desktop, use the graphical Settings tool:

  
  
  
  
  

  • Go to Network;

  
  

  • Press the gear button;

  
  

  • Select Manual configuration.

  
  
  
  


• 
  

  For Ubuntu 18.04 Server, edit the netplan configuration in /etc/netplan.

  
  
  
  
  

  • Most likely the configuration file is called 01-netcfg.yaml for Ubuntu Server and 01-network-manager-all.yaml for Ubuntu Desktop.

  
  

  • Netplan configuration files are written in YAML; take care not to insert any tabs.

  
  
  
  

share|improve this answer

edited May 25 '18 at 20:37

answered May 25 '18 at 17:47

AlexPAlexP

7,5531313 silver badges2929 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  your explanation is logical (and the post clarifies in part) but does not solve the problem raised in my question, since it only affects the interface enp2s0 and works well in the local interface enp2s1. If this configuration could no longer be used in /etc/network/interfaces then none should work. By the way, the file is called 01-network-manager-all.yaml
  
  – ajcg
  May 25 '18 at 20:05
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @user4839775: /etc/netplan/01-network-manager-all.yaml is for desktop systems. On desktop systems you have a nice GUI.
  
  – AlexP
  May 25 '18 at 20:33
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Servers sometimes have a desktop (Gnome, Mate, etc) and, normally, no GUI is used to configure the interfaces
  
  – ajcg
  May 26 '18 at 0:02
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  netplan is only used on fresh installations. Upgraded installations continue to use ifupdown or similar packages with /etc/network/interfaces. However, this appears to be not very well tested as I had an upgrade go "wrong" in that the ifupdown package got removed and I was left with a system that could not bring up the interfaces. Booting into a Ubuntu 18.04 CD and then chrooting into the actual system enabled me to install ifupdown which resolved the issue. This makes your answer wrong because the inquirer indicated that the system was upgraded from 16.04.
  
  – 0xC0000022L
  Nov 2 '18 at 15:05
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This will never be the solution. On a computer with four Ethernet interfaces, the processes you recommend are insufficient. The specified applications may not work on the new installed system. My cards are automatically closed at each system startup (except for the cards with DHCP enabled). I've had similar problems in almost all versions of Ubuntu, and I was able to remove the network manager to resolve it. @0xC0000022L comments is TRUE
  
  – dsgdfg
  Jan 16 at 10:33
  

  
  
  
  

add a comment | 

1

On a new installation of Ubuntu 18 server, you can use the same network configuration that you used on Ubuntu 16 server in /etc/network/interfaces, and it works, only you must:

1. sudo apt install ifupdown


2. edit the file /etc/network/interfaces


3. 
   cd /etc/netplan/ and then mv 50-cloud-init.yaml 50-cloud-init.yaml.old
   

I guess it will also work on an update from Ubuntu 16 server to Ubuntu 18 server.

share|improve this answer

edited Aug 16 at 22:17

Jeff Schaller♦

49.1k1111 gold badges7272 silver badges163163 bronze badges

answered Aug 16 at 20:48

Gustavo ParedesGustavo Paredes

1111 bronze badge

New contributor

Gustavo Paredes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446039%2fproblem-with-interface-with-ip-static-in-ubuntu-18-04%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

-1

Ubuntu 18.04 does not use the legacy configuration file /etc/network/interfaces. Instead of the old ifupdown mechanism, Ubuntu 18.04 uses Netplan, as documented in the Release Notes. See "How to configure static IP address on Ubuntu 18.04" for a brief tutorial:

• 
  

  For Ubuntu 18.04 Desktop, use the graphical Settings tool:

  
  
  
  
  

  • Go to Network;

  
  

  • Press the gear button;

  
  

  • Select Manual configuration.

  
  
  
  


• 
  

  For Ubuntu 18.04 Server, edit the netplan configuration in /etc/netplan.

  
  
  
  
  

  • Most likely the configuration file is called 01-netcfg.yaml for Ubuntu Server and 01-network-manager-all.yaml for Ubuntu Desktop.

  
  

  • Netplan configuration files are written in YAML; take care not to insert any tabs.

  
  
  
  

share|improve this answer

edited May 25 '18 at 20:37

answered May 25 '18 at 17:47

AlexPAlexP

7,5531313 silver badges2929 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  your explanation is logical (and the post clarifies in part) but does not solve the problem raised in my question, since it only affects the interface enp2s0 and works well in the local interface enp2s1. If this configuration could no longer be used in /etc/network/interfaces then none should work. By the way, the file is called 01-network-manager-all.yaml
  
  – ajcg
  May 25 '18 at 20:05
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @user4839775: /etc/netplan/01-network-manager-all.yaml is for desktop systems. On desktop systems you have a nice GUI.
  
  – AlexP
  May 25 '18 at 20:33
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Servers sometimes have a desktop (Gnome, Mate, etc) and, normally, no GUI is used to configure the interfaces
  
  – ajcg
  May 26 '18 at 0:02
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  netplan is only used on fresh installations. Upgraded installations continue to use ifupdown or similar packages with /etc/network/interfaces. However, this appears to be not very well tested as I had an upgrade go "wrong" in that the ifupdown package got removed and I was left with a system that could not bring up the interfaces. Booting into a Ubuntu 18.04 CD and then chrooting into the actual system enabled me to install ifupdown which resolved the issue. This makes your answer wrong because the inquirer indicated that the system was upgraded from 16.04.
  
  – 0xC0000022L
  Nov 2 '18 at 15:05
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This will never be the solution. On a computer with four Ethernet interfaces, the processes you recommend are insufficient. The specified applications may not work on the new installed system. My cards are automatically closed at each system startup (except for the cards with DHCP enabled). I've had similar problems in almost all versions of Ubuntu, and I was able to remove the network manager to resolve it. @0xC0000022L comments is TRUE
  
  – dsgdfg
  Jan 16 at 10:33
  

  
  
  
  

add a comment | 

-1

Ubuntu 18.04 does not use the legacy configuration file /etc/network/interfaces. Instead of the old ifupdown mechanism, Ubuntu 18.04 uses Netplan, as documented in the Release Notes. See "How to configure static IP address on Ubuntu 18.04" for a brief tutorial:

• 
  

  For Ubuntu 18.04 Desktop, use the graphical Settings tool:

  
  
  
  
  

  • Go to Network;

  
  

  • Press the gear button;

  
  

  • Select Manual configuration.

  
  
  
  


• 
  

  For Ubuntu 18.04 Server, edit the netplan configuration in /etc/netplan.

  
  
  
  
  

  • Most likely the configuration file is called 01-netcfg.yaml for Ubuntu Server and 01-network-manager-all.yaml for Ubuntu Desktop.

  
  

  • Netplan configuration files are written in YAML; take care not to insert any tabs.

  
  
  
  

share|improve this answer

edited May 25 '18 at 20:37

answered May 25 '18 at 17:47

AlexPAlexP

7,5531313 silver badges2929 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  your explanation is logical (and the post clarifies in part) but does not solve the problem raised in my question, since it only affects the interface enp2s0 and works well in the local interface enp2s1. If this configuration could no longer be used in /etc/network/interfaces then none should work. By the way, the file is called 01-network-manager-all.yaml
  
  – ajcg
  May 25 '18 at 20:05
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @user4839775: /etc/netplan/01-network-manager-all.yaml is for desktop systems. On desktop systems you have a nice GUI.
  
  – AlexP
  May 25 '18 at 20:33
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Servers sometimes have a desktop (Gnome, Mate, etc) and, normally, no GUI is used to configure the interfaces
  
  – ajcg
  May 26 '18 at 0:02
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  netplan is only used on fresh installations. Upgraded installations continue to use ifupdown or similar packages with /etc/network/interfaces. However, this appears to be not very well tested as I had an upgrade go "wrong" in that the ifupdown package got removed and I was left with a system that could not bring up the interfaces. Booting into a Ubuntu 18.04 CD and then chrooting into the actual system enabled me to install ifupdown which resolved the issue. This makes your answer wrong because the inquirer indicated that the system was upgraded from 16.04.
  
  – 0xC0000022L
  Nov 2 '18 at 15:05
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This will never be the solution. On a computer with four Ethernet interfaces, the processes you recommend are insufficient. The specified applications may not work on the new installed system. My cards are automatically closed at each system startup (except for the cards with DHCP enabled). I've had similar problems in almost all versions of Ubuntu, and I was able to remove the network manager to resolve it. @0xC0000022L comments is TRUE
  
  – dsgdfg
  Jan 16 at 10:33
  

  
  
  
  

add a comment | 

Ubuntu 18.04 does not use the legacy configuration file /etc/network/interfaces. Instead of the old ifupdown mechanism, Ubuntu 18.04 uses Netplan, as documented in the Release Notes. See "How to configure static IP address on Ubuntu 18.04" for a brief tutorial:

• 
  

  For Ubuntu 18.04 Desktop, use the graphical Settings tool:

  
  
  
  
  

  • Go to Network;

  
  

  • Press the gear button;

  
  

  • Select Manual configuration.

  
  
  
  


• 
  

  For Ubuntu 18.04 Server, edit the netplan configuration in /etc/netplan.

  
  
  
  
  

  • Most likely the configuration file is called 01-netcfg.yaml for Ubuntu Server and 01-network-manager-all.yaml for Ubuntu Desktop.

  
  

  • Netplan configuration files are written in YAML; take care not to insert any tabs.

  
  
  
  

share|improve this answer

edited May 25 '18 at 20:37

answered May 25 '18 at 17:47

AlexPAlexP

7,5531313 silver badges2929 bronze badges

share|improve this answer

edited May 25 '18 at 20:37

answered May 25 '18 at 17:47

AlexPAlexP

7,5531313 silver badges2929 bronze badges

answered May 25 '18 at 17:47

AlexPAlexP

7,5531313 silver badges2929 bronze badges

answered May 25 '18 at 17:47

AlexPAlexP

7,5531313 silver badges2929 bronze badges

1

On a new installation of Ubuntu 18 server, you can use the same network configuration that you used on Ubuntu 16 server in /etc/network/interfaces, and it works, only you must:

1. sudo apt install ifupdown


2. edit the file /etc/network/interfaces


3. 
   cd /etc/netplan/ and then mv 50-cloud-init.yaml 50-cloud-init.yaml.old
   

I guess it will also work on an update from Ubuntu 16 server to Ubuntu 18 server.

share|improve this answer

edited Aug 16 at 22:17

Jeff Schaller♦

49.1k1111 gold badges7272 silver badges163163 bronze badges

answered Aug 16 at 20:48

Gustavo ParedesGustavo Paredes

1111 bronze badge

New contributor

Gustavo Paredes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

1

On a new installation of Ubuntu 18 server, you can use the same network configuration that you used on Ubuntu 16 server in /etc/network/interfaces, and it works, only you must:

1. sudo apt install ifupdown


2. edit the file /etc/network/interfaces


3. 
   cd /etc/netplan/ and then mv 50-cloud-init.yaml 50-cloud-init.yaml.old
   

I guess it will also work on an update from Ubuntu 16 server to Ubuntu 18 server.

share|improve this answer

edited Aug 16 at 22:17

Jeff Schaller♦

49.1k1111 gold badges7272 silver badges163163 bronze badges

answered Aug 16 at 20:48

Gustavo ParedesGustavo Paredes

1111 bronze badge

New contributor

Gustavo Paredes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

On a new installation of Ubuntu 18 server, you can use the same network configuration that you used on Ubuntu 16 server in /etc/network/interfaces, and it works, only you must:

1. sudo apt install ifupdown


2. edit the file /etc/network/interfaces


3. 
   cd /etc/netplan/ and then mv 50-cloud-init.yaml 50-cloud-init.yaml.old
   

I guess it will also work on an update from Ubuntu 16 server to Ubuntu 18 server.

share|improve this answer

edited Aug 16 at 22:17

Jeff Schaller♦

49.1k1111 gold badges7272 silver badges163163 bronze badges

answered Aug 16 at 20:48

Gustavo ParedesGustavo Paredes

1111 bronze badge

New contributor

Gustavo Paredes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this answer

edited Aug 16 at 22:17

Jeff Schaller♦

49.1k1111 gold badges7272 silver badges163163 bronze badges

answered Aug 16 at 20:48

Gustavo ParedesGustavo Paredes

1111 bronze badge

New contributor

Gustavo Paredes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

edited Aug 16 at 22:17

Jeff Schaller♦

49.1k1111 gold badges7272 silver badges163163 bronze badges

edited Aug 16 at 22:17

Jeff Schaller♦

49.1k1111 gold badges7272 silver badges163163 bronze badges

answered Aug 16 at 20:48

Gustavo ParedesGustavo Paredes

1111 bronze badge

New contributor

Gustavo Paredes is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

answered Aug 16 at 20:48

Gustavo ParedesGustavo Paredes

1111 bronze badge