Score:0

Server

Netplan - Error in network definition: Updated definition changes device type

Gimme the 411

4/30/23, 10:52 AM

I'm trying to set a static ip on Ubuntu.

ip a:

1: lo <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
   ...
2: epn2s0: <NO-CARRIER,BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
   link/ether ... brd ff:ff:ff:ff:ff:ff
3: wkp1s0: <BROADCAST,MULTICAST,UP_LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
   link/ether ... brd ff:ff:ff:ff:ff:ff
   inet 192.168.1.15/24 brd 192.168.1.255 scope global dynamic wkp1s0
      valid_lft 86000sec preferred_lft 86000sec
   inet6 ... scope link
      forever preferred_lft forever

ethtool -i wkp1s0:

driver: iwlwifi
version: ...
firmware-version: ...
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

ethtool -i epn2s0:

driver: r8169
version:
firmware-version: ...
expansion-rom-version:
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

default "/etc/netplan/00-installer-config.yaml":

# This is the network config written by 'subiquity'
network:
  ethernets:
    epn2s0:
      dhcp4: true
  version: 2

When I try to change the yaml file to this:

"/etc/netplan/00-installer-config.yaml":

# This is the network config written by 'subiquity'
network:
  version: 2
  ethernets:
    wkp1s0:
      addresses:
        [192.168.1.100/24]
      nameservers:
        addresses: [8.8.8.8,8.8.4.4]

it gives this error:

sudo netplan try

/etc/netplan/00-installer-config.yaml:5:5: Error in network definition: Updated definition 'wkp1s0' changes device type
    wkp1s0:
    ^

What am I doing wrong?

I know that my original yaml file is setting dhcp for the other adapter, epn2s0, but even though it's doing that, wkp1s0 is getting an ip.

When I change wkp1s0 -> epn2s0 in the yaml file to try to set static ip for epn2s0, I get this error:

sudo netplan try

An error occurred: Command '['systemctl], 'stop', 'systemd-networkd.service', 'netplan-wpa-*.service']' returned non-zero exit status 1.

What am I doing wrong?

UPDATE:

when I try this yaml file:

# This is the network config written by 'subiquity'
network:
  version: 2
  wifis:
    wkp1s0:
      addresses:
        [192.168.1.151/24]
      nameservers:
        addresses: [8.8.8.8,8.8.4.4]
  ethernets:
    epn2s0:
      dhcp4:
        true

netplan try:

An error occurred: Command '['systemctl', 'stop', 'systemd-networkd.service', 'netplan-wpa-*.service']' returned non-zero exit status 1.

After that, "ip a" now shows:

1: lo <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
   ...
2: epn2s0: <NO-CARRIER,BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
   link/ether ... brd ff:ff:ff:ff:ff:ff
3: wkp1s0: <BROADCAST,MULTICAST,UP_LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
   link/ether ... brd ff:ff:ff:ff:ff:ff
   inet 192.168.1.151/24 brd 192.168.1.255 scope global global wkp1s0
      valid_lft 86000sec preferred_lft 86000sec
   inet 192.168.1.44/24 brd 192.168.1.255 scope global secondary dynamic wkp1s0
      valid_lft 86000sec preferred_lft 86000sec
   inet6 ... scope link
      valid_lft forever preferred_lft forever

So now the wifi adapter seems to have 2 ip addresses, 1 of which is dynamic

Both of these ip addresses now work (I'm hosting an apache2 server on it), and one of them is static, so perhaps it's solved, but I don't want the dynamic IP, only the static one.

1021

0 + 0

ubuntu

static-ip

netplan

user10489

4/30/23, 12:51 PM

It would be necessary to see the wkps1s0 entry in your netplan and output from `ethtool -i wkp1s0` to figure this out. Likely the TYPE line doesn't match the device.

Gimme the 411

5/1/23, 8:06 AM

@user10489 I added more details

Score:1

Server

user10489

5/1/23, 2:14 PM

Your device wkp1s0 appears to be a wifi interface, not a ethernet interface. According to the netplan(5) man page, this needs to be in a wifis: section instead of a ethernets: section.

The man page also notes you will need wpasupplicant installed, and you may also need to add static configuration options to set up the connection to your wifi access point, such as password and access-point.

0 + 0

Gimme the 411

5/1/23, 2:40 PM

Yes, I'm trying to set a static ip for the wifi interface. The ethernet interface is not used. Even though my default yaml file doesn't mention the wifi interface at all, and sets the ethernet interface to use dhcp, ip a shows that the wifi interface obtains an ip by dhcp. And the wifi connects and works correctly, I just want to make it use a static ip. Can you suggest what my yaml file should look like? Because changing ethernets: to wifis: gives a general error.

user10489

5/1/23, 2:43 PM

Very possibly your existing yaml will work, but you need to put the wkp1s0 section in a wifis: section rather than an ethernets: section. If you have an ethernets: section at all, only epn2s0 should be in it.

Gimme the 411

5/1/23, 3:35 PM

I updated with the error that it gives when I change my yaml file like that

Gimme the 411

5/1/23, 3:41 PM

I also added the new result of "ip a", which shows that the wifi adapter now has 2 ip addresses, 1 of which seems to be dynamic.

user10489

5/1/23, 4:52 PM

Netplan doesn't seem to remove old configurations from interfaces, so getting two addresses happens. That should go away on some future boot or maybe when the dhcp lease expires; ignore it for now. Focus on fixing the netplan error. At a guess, there's something wrong with your wpasupplicant configuration, and you need to see what the errors are that are breaking netplan-wpa-*.service. (Probably it isn't configured at all and needs to be.) Possibly adding more directives in the netplan section (like password, access-points) would fix it.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Netplan - Error in network definition: Updated definition changes device type

TH: Netplan - ข้อผิดพลาดในข้อกำหนดเครือข่าย: ข้อกำหนดที่อัปเดตจะเปลี่ยนประเภทอุปกรณ์

RO: Netplan - Eroare în definirea rețelei: Definiția actualizată modifică tipul dispozitivului

RU: Netplan - Ошибка в определении сети: обновленное определение изменяет тип устройства

VI: Netplan - Lỗi trong định nghĩa mạng: Định nghĩa được cập nhật thay đổi loại thiết bị

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.