Ubuntu – Netplan error, error on nameserver

17.10netplannetworkingserver

I'm trying to setup a Ubuntu server and running in to a problem setting up a static IP.

My OS is as below:

Distributor ID: Ubuntu
Description:    Ubuntu 17.10
Release:        17.10
Codename:       artful

My 01-netcfg.yaml is below:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp5s0f0:
      dhcp4: no
      addresses: [192.168.0.109/24]
      gateway4: 192.168.0.1
      nameservers:
        adresses: [8.8.8.8,8.8.4.4]

When running sudo netplan apply I get the below error. Same error when running debug.

Error in network definition //etc/netplan/01-netcfg.yaml line 9 column 8: unknown key adresses

All my google attempts for a correct .yaml file says this should work.
What am I doing wrong?

Best Answer

I believe it is telling you that it doesn't understand adresses. Please try:

addresses: [8.8.8.8,8.8.4.4]

Follow with:

sudo netplan apply

Any improvement?

Related Solutions

Ubuntu – Ubuntu 18.04 Network card with two IP addresses

There are often issues with having multiple gateways set for interfaces. Routing packets over to one and then the other may lead to confusion on the network, so you're often best served by having a single default gateway unless you really know what you are doing.

In short, you usually want only one

gateway4: xx.xx.xx.xx

line in your config.

If you must have multiple routes for the individual IPs of the interface, you can control exactly how they will behave by writing static routes (and setting the metric based on the priority of the addresses), like so:

network:
  version: 2
  renderer: NetworkManager
  ethernets:
     enp0s3:
        dhcp4: no
        dhcp6: no
        addresses: [ 192.168.0.2/32, 172.16.0.2/16 ]
        nameservers:
              search: [usp.br]
              addresses: [ 192.168.0.100, 192.168.0.102 ]
        routes:
          - to: 0.0.0.0/0
            via: 192.168.0.1
          - to: 0.0.0.0/0
            via: 172.168.0.1

You also don't need optional: true: it only stops delaying boot if the interface isn't coming up fast enough, which shouldn't be an issue given that you specific static addresses. Adding optional: true also has the side effect of not blocking for some targets in systemd, which might mean a server will not start all the services it should right away if these services need the network.

Ubuntu – Netplan error in network definition expected mapping

removing dhcp4 setting fixed the issue...who knows!

maybe because if you enable the dhcp you have to set it to "true" and if you disable you have to set to "no"? I really hope not!!

debug info completely useless

Best Answer

Related Solutions

Ubuntu – Ubuntu 18.04 Network card with two IP addresses

Ubuntu – Netplan error in network definition expected mapping

Related Question