Issues setting static IP using netplan Ubuntu Server 18.04 LTS












0















Having some major issues with networking on Ubuntu 18.04 LTS. Fresh install. I set a static IP during install which worked for a couple days and remained set after multiple reboots. Now the interface shows no IP. It seems when I set that IP it did generate a netplan that appears correct however netplan apply does nothing.



This happened to me previously as well on the previous install. I had been messing with some DNS stuff so I figured I'd just reimage the machine and not touch any of the network utilities this time and I still am having the issue.



The issue occurs about a day and a half after install seemingly randomly. Was not using the machine when the issue began and the only thing I have done so far on this install is set up a couple docker containers with samba and SFTP.



Edit: I scrapped the default netplan and followed a tutorial to create this one still no cigar.



Contents of my 50-cloud-init.yaml



# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.0.32/24]
gateway4: 192.168.0.1
nameservers:
addresses: [1.1.1.1,8.8.8.8]


Terminal output from netplan --debug apply



** (generate:2227): DEBUG: 23:11:19.520: Processing input file /etc/netplan/50-cloud-init.yaml..
** (generate:2227): DEBUG: 23:11:19.520: starting new processing pass
** (generate:2227): DEBUG: 23:11:19.520: enp0s25: setting default backend to 1
** (generate:2227): DEBUG: 23:11:19.520: Generating output files..
** (generate:2227): DEBUG: 23:11:19.520: NetworkManager: definition enp0s25 is not for us (backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:enp0s25 not found in {}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
enp0s25:
addresses:
- 192.168.0.32/24
dhcp4: false
gateway4: 192.168.0.1
nameservers:
addresses:
- 1.1.1.1
- 8.8.8.8
vlans: {}
wifis: {}

DEBUG:Skipping non-physical interface: lo
DEBUG:Skipping non-physical interface: docker0
DEBUG:Skipping non-physical interface: br-98e8ea9c70cb
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp0s25
DEBUG:netplan triggering .link rules for docker0
DEBUG:netplan triggering .link rules for br-98e8ea9c70cb



my ifconfig after applying this netplan:



br-98e8ea9c70cb: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
ether 02:42:51:a6:a3:66 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:d5:d6:46:8e txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp0s25: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:24:7e:00:e0:30 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xfc500000-fc520000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 7926 bytes 592108 (592.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7926 bytes 592108 (592.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0











share|improve this question









New contributor




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





















  • Your .yaml file looks fine, other than the indents/spacing. netplan is very fussy about that. Change all of the indents to 2, instead of 4. Then sudo netplan --debug generate and sudo netplan apply, and then edit your question with the output from sudo lshw -C network and cat /etc/network/interfaces. Report back to @heynnema

    – heynnema
    5 hours ago













  • See docs.docker.com/network/network-tutorial-standalone for docker networking help.

    – heynnema
    5 hours ago











  • See digitalocean.com/community/tutorials/… for docker installation info.

    – heynnema
    5 hours ago











  • See howtoforge.com/tutorial/ubuntu-docker for usage info.

    – heynnema
    5 hours ago
















0















Having some major issues with networking on Ubuntu 18.04 LTS. Fresh install. I set a static IP during install which worked for a couple days and remained set after multiple reboots. Now the interface shows no IP. It seems when I set that IP it did generate a netplan that appears correct however netplan apply does nothing.



This happened to me previously as well on the previous install. I had been messing with some DNS stuff so I figured I'd just reimage the machine and not touch any of the network utilities this time and I still am having the issue.



The issue occurs about a day and a half after install seemingly randomly. Was not using the machine when the issue began and the only thing I have done so far on this install is set up a couple docker containers with samba and SFTP.



Edit: I scrapped the default netplan and followed a tutorial to create this one still no cigar.



Contents of my 50-cloud-init.yaml



# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.0.32/24]
gateway4: 192.168.0.1
nameservers:
addresses: [1.1.1.1,8.8.8.8]


Terminal output from netplan --debug apply



** (generate:2227): DEBUG: 23:11:19.520: Processing input file /etc/netplan/50-cloud-init.yaml..
** (generate:2227): DEBUG: 23:11:19.520: starting new processing pass
** (generate:2227): DEBUG: 23:11:19.520: enp0s25: setting default backend to 1
** (generate:2227): DEBUG: 23:11:19.520: Generating output files..
** (generate:2227): DEBUG: 23:11:19.520: NetworkManager: definition enp0s25 is not for us (backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:enp0s25 not found in {}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
enp0s25:
addresses:
- 192.168.0.32/24
dhcp4: false
gateway4: 192.168.0.1
nameservers:
addresses:
- 1.1.1.1
- 8.8.8.8
vlans: {}
wifis: {}

DEBUG:Skipping non-physical interface: lo
DEBUG:Skipping non-physical interface: docker0
DEBUG:Skipping non-physical interface: br-98e8ea9c70cb
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp0s25
DEBUG:netplan triggering .link rules for docker0
DEBUG:netplan triggering .link rules for br-98e8ea9c70cb



my ifconfig after applying this netplan:



br-98e8ea9c70cb: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
ether 02:42:51:a6:a3:66 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:d5:d6:46:8e txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp0s25: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:24:7e:00:e0:30 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xfc500000-fc520000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 7926 bytes 592108 (592.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7926 bytes 592108 (592.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0











share|improve this question









New contributor




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





















  • Your .yaml file looks fine, other than the indents/spacing. netplan is very fussy about that. Change all of the indents to 2, instead of 4. Then sudo netplan --debug generate and sudo netplan apply, and then edit your question with the output from sudo lshw -C network and cat /etc/network/interfaces. Report back to @heynnema

    – heynnema
    5 hours ago













  • See docs.docker.com/network/network-tutorial-standalone for docker networking help.

    – heynnema
    5 hours ago











  • See digitalocean.com/community/tutorials/… for docker installation info.

    – heynnema
    5 hours ago











  • See howtoforge.com/tutorial/ubuntu-docker for usage info.

    – heynnema
    5 hours ago














0












0








0








Having some major issues with networking on Ubuntu 18.04 LTS. Fresh install. I set a static IP during install which worked for a couple days and remained set after multiple reboots. Now the interface shows no IP. It seems when I set that IP it did generate a netplan that appears correct however netplan apply does nothing.



This happened to me previously as well on the previous install. I had been messing with some DNS stuff so I figured I'd just reimage the machine and not touch any of the network utilities this time and I still am having the issue.



The issue occurs about a day and a half after install seemingly randomly. Was not using the machine when the issue began and the only thing I have done so far on this install is set up a couple docker containers with samba and SFTP.



Edit: I scrapped the default netplan and followed a tutorial to create this one still no cigar.



Contents of my 50-cloud-init.yaml



# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.0.32/24]
gateway4: 192.168.0.1
nameservers:
addresses: [1.1.1.1,8.8.8.8]


Terminal output from netplan --debug apply



** (generate:2227): DEBUG: 23:11:19.520: Processing input file /etc/netplan/50-cloud-init.yaml..
** (generate:2227): DEBUG: 23:11:19.520: starting new processing pass
** (generate:2227): DEBUG: 23:11:19.520: enp0s25: setting default backend to 1
** (generate:2227): DEBUG: 23:11:19.520: Generating output files..
** (generate:2227): DEBUG: 23:11:19.520: NetworkManager: definition enp0s25 is not for us (backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:enp0s25 not found in {}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
enp0s25:
addresses:
- 192.168.0.32/24
dhcp4: false
gateway4: 192.168.0.1
nameservers:
addresses:
- 1.1.1.1
- 8.8.8.8
vlans: {}
wifis: {}

DEBUG:Skipping non-physical interface: lo
DEBUG:Skipping non-physical interface: docker0
DEBUG:Skipping non-physical interface: br-98e8ea9c70cb
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp0s25
DEBUG:netplan triggering .link rules for docker0
DEBUG:netplan triggering .link rules for br-98e8ea9c70cb



my ifconfig after applying this netplan:



br-98e8ea9c70cb: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
ether 02:42:51:a6:a3:66 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:d5:d6:46:8e txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp0s25: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:24:7e:00:e0:30 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xfc500000-fc520000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 7926 bytes 592108 (592.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7926 bytes 592108 (592.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0











share|improve this question









New contributor




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












Having some major issues with networking on Ubuntu 18.04 LTS. Fresh install. I set a static IP during install which worked for a couple days and remained set after multiple reboots. Now the interface shows no IP. It seems when I set that IP it did generate a netplan that appears correct however netplan apply does nothing.



This happened to me previously as well on the previous install. I had been messing with some DNS stuff so I figured I'd just reimage the machine and not touch any of the network utilities this time and I still am having the issue.



The issue occurs about a day and a half after install seemingly randomly. Was not using the machine when the issue began and the only thing I have done so far on this install is set up a couple docker containers with samba and SFTP.



Edit: I scrapped the default netplan and followed a tutorial to create this one still no cigar.



Contents of my 50-cloud-init.yaml



# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.0.32/24]
gateway4: 192.168.0.1
nameservers:
addresses: [1.1.1.1,8.8.8.8]


Terminal output from netplan --debug apply



** (generate:2227): DEBUG: 23:11:19.520: Processing input file /etc/netplan/50-cloud-init.yaml..
** (generate:2227): DEBUG: 23:11:19.520: starting new processing pass
** (generate:2227): DEBUG: 23:11:19.520: enp0s25: setting default backend to 1
** (generate:2227): DEBUG: 23:11:19.520: Generating output files..
** (generate:2227): DEBUG: 23:11:19.520: NetworkManager: definition enp0s25 is not for us (backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:enp0s25 not found in {}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
enp0s25:
addresses:
- 192.168.0.32/24
dhcp4: false
gateway4: 192.168.0.1
nameservers:
addresses:
- 1.1.1.1
- 8.8.8.8
vlans: {}
wifis: {}

DEBUG:Skipping non-physical interface: lo
DEBUG:Skipping non-physical interface: docker0
DEBUG:Skipping non-physical interface: br-98e8ea9c70cb
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp0s25
DEBUG:netplan triggering .link rules for docker0
DEBUG:netplan triggering .link rules for br-98e8ea9c70cb



my ifconfig after applying this netplan:



br-98e8ea9c70cb: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
ether 02:42:51:a6:a3:66 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:d5:d6:46:8e txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp0s25: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:24:7e:00:e0:30 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xfc500000-fc520000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 7926 bytes 592108 (592.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7926 bytes 592108 (592.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0








networking server 18.04 netplan systemd-networkd






share|improve this question









New contributor




CNorlander 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 question









New contributor




CNorlander 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 question




share|improve this question








edited 7 hours ago







CNorlander













New contributor




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









asked 7 hours ago









CNorlanderCNorlander

11




11




New contributor




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





New contributor





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






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













  • Your .yaml file looks fine, other than the indents/spacing. netplan is very fussy about that. Change all of the indents to 2, instead of 4. Then sudo netplan --debug generate and sudo netplan apply, and then edit your question with the output from sudo lshw -C network and cat /etc/network/interfaces. Report back to @heynnema

    – heynnema
    5 hours ago













  • See docs.docker.com/network/network-tutorial-standalone for docker networking help.

    – heynnema
    5 hours ago











  • See digitalocean.com/community/tutorials/… for docker installation info.

    – heynnema
    5 hours ago











  • See howtoforge.com/tutorial/ubuntu-docker for usage info.

    – heynnema
    5 hours ago



















  • Your .yaml file looks fine, other than the indents/spacing. netplan is very fussy about that. Change all of the indents to 2, instead of 4. Then sudo netplan --debug generate and sudo netplan apply, and then edit your question with the output from sudo lshw -C network and cat /etc/network/interfaces. Report back to @heynnema

    – heynnema
    5 hours ago













  • See docs.docker.com/network/network-tutorial-standalone for docker networking help.

    – heynnema
    5 hours ago











  • See digitalocean.com/community/tutorials/… for docker installation info.

    – heynnema
    5 hours ago











  • See howtoforge.com/tutorial/ubuntu-docker for usage info.

    – heynnema
    5 hours ago

















Your .yaml file looks fine, other than the indents/spacing. netplan is very fussy about that. Change all of the indents to 2, instead of 4. Then sudo netplan --debug generate and sudo netplan apply, and then edit your question with the output from sudo lshw -C network and cat /etc/network/interfaces. Report back to @heynnema

– heynnema
5 hours ago







Your .yaml file looks fine, other than the indents/spacing. netplan is very fussy about that. Change all of the indents to 2, instead of 4. Then sudo netplan --debug generate and sudo netplan apply, and then edit your question with the output from sudo lshw -C network and cat /etc/network/interfaces. Report back to @heynnema

– heynnema
5 hours ago















See docs.docker.com/network/network-tutorial-standalone for docker networking help.

– heynnema
5 hours ago





See docs.docker.com/network/network-tutorial-standalone for docker networking help.

– heynnema
5 hours ago













See digitalocean.com/community/tutorials/… for docker installation info.

– heynnema
5 hours ago





See digitalocean.com/community/tutorials/… for docker installation info.

– heynnema
5 hours ago













See howtoforge.com/tutorial/ubuntu-docker for usage info.

– heynnema
5 hours ago





See howtoforge.com/tutorial/ubuntu-docker for usage info.

– heynnema
5 hours ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});






CNorlander is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1118371%2fissues-setting-static-ip-using-netplan-ubuntu-server-18-04-lts%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








CNorlander is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















CNorlander is a new contributor. Be nice, and check out our Code of Conduct.













CNorlander is a new contributor. Be nice, and check out our Code of Conduct.












CNorlander is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1118371%2fissues-setting-static-ip-using-netplan-ubuntu-server-18-04-lts%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

數位音樂下載

When can things happen in Etherscan, such as the picture below?

格利澤436b