##Background I'm using Ubuntu 18.04 server (on a laptop, for development) and am trying to get my wifi configured to work with an WPA-EAP network. - To enable Wifi I followed the guide [Wifi on Ubuntu 18 server](https://gist.github.com/austinjp/9b968c75c3e54004be7cd7a134881d85) - I looked at the [Netplan Examples](https://netplan.io/examples) (none with WPA-EAP ) - I've read the [Netplan Full Documentation](https://github.com/CanonicalLtd/netplan/blob/master/doc/netplan.md) . I've got netplan to work with an an open network, even with a password protected network, but haven't been able to get it to work with WPA-EAP where both an identity and password are required. ##Attempted Configuration I've tried this in my /etc/netplan/config.yaml file: network: wifis: wlp1s0: dhcp4: yes access-points: "My-Enterprise-Network": auth: key-management: eap identity: johndoe1 password: pass1234 But when I run netplan apply I get: Error in network definition /etc/netplan/config.yaml: unknown key auth ##From the Documentation From the [online netplan documentation](https://github.com/CanonicalLtd/netplan/blob/master/doc/netplan.md) : The `auth` block supports the following properties: `key-management` (scalar) : The supported key management modes are `none` (no key management); `psk (WPA with pre-shared key, common for home wifi); eap` (WPA with EAP, common for enterprise wifi); and `802.1x` (used primarily for wired Ethernet connections). `password` (scalar) : The password string for EAP, or the pre-shared key for WPA-PSK. The following properties can be used if `key-management is eap` or `802.1x`: `method` (scalar) : The EAP method to use. The supported EAP methods are `tls` (TLS), `peap (Protected EAP), and ttls` (Tunneled TLS). `identity` (scalar) : The identity to use for EAP. ## From man netplan access-points (mapping) This provides pre-configured connections to NetworkManager. Note that users can of course select other access points/SSIDs. The keys of the mapping are the SSIDs, and the values are mappings with the following supported properties: password (scalar) Enable WPA2 authentication and set the passphrase for it. If not given, the network is assumed to be open. **Other authentication modes are not currently supported.** Note the last line: Other authentication modes are not currently supported. ###Questions 1. What's the right way to use netplan with WPA-EAP? 1. Does Ubuntu 18.04 ship with an outdated version of netplan? ( netplan --version is not supported ) Hence perhaps why the online documentation has options that the man version does not? 1. If so, can I upgrade netplan to a more cutting edge release? 1. Or does netplan need to be used with something like a wpa_supplicant.conf to specify additional parameters?

I've seen a couple of other posts about the 'gateway4 has been deprecated' warning that some get when entering sudo netplan apply. My problem is slightly different: I get that warning even though there is no 'gateway4' line in my .yaml config file. Running Ubuntu 22.04.1 on a headless server. Here's the .yaml file: network: version: 2 renderer: networkd ethernets: enp0s31f6: addresses: - [ipv4 address]/32 - [ipv6 address]/64 routes: - to: default via: [gateway ipv4 address here] metric: 100 on-link: true - to: ::/0 via: fe80::1 nameservers: addresses: - 1.1.1.1 - 2606:4700:4700::1111 - 1.0.0.1 - 2606:4700:4700::1001 Why might I be getting warnings about gateway4 having been deprecated?

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. 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

br-98e8ea9c70cb: flags=4099  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  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  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  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10
        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

I am learning about Linux networking on my Kubuntu 18.04 workstation, and I see there that both NetworkManager and networkd-dispatcher are running: oleg@eclectic:~$ sudo ps -ef | grep -i net root 56 2 0 Oct11 ? 00:00:00 [netns] root 1097 1 0 Oct11 ? 00:00:02 /usr/sbin/NetworkManager --no-daemon root 1098 1 0 Oct11 ? 00:00:00 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers root 1250 1 0 Oct11 ? 00:00:02 /usr/sbin/inetd root 1593 1097 0 Oct11 ? 00:00:00 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper... NetworkManager seems to be configured to handle "everything" by netplan: oleg@eclectic:~$ cat /etc/netplan/01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager I believe that netplan would hand everything off to networkd if NetworkManager was not installed. There are also a bunch of files in /etc/network/, and I am not sure what is handling those. A lot of packages seem to use this directory: oleg@eclectic:~$ dpkg -S /etc/network avahi-daemon, ifupdown2, wpasupplicant, openvpn, postfix, netbase, avahi-autoipd, wireless-tools, clamav-freshclam: /etc/network My initial thoughts after some Googling are that NetworkManager and networkd are both running, but netplan generates configuration such that only one is actually doing something. But I do not know how I would verify this, figure out the chain of operations, or configure it to suit my nefarious plans for dummy0. **Question:** How exactly are NetworkManager, networkd, and netplan working together? In other words, as the computer boots up, which processes hand what of to what other processes? How do tools from packages like net-tools, ifupdown2, and iproute2 and directories like /etc/network/ fit into all this? And finally, how can I figure this out myself and learn the details using the command line? **Update:** I am not looking for a high-level overview. Rather, I want to know how these components are interacting, conflicting, or avoiding conflict on the kernel level or similar.

First off, let me say that to me, networking is a black art, practiced by strange men in hooded cloaks, chanting strange incantations. I can 'do' **basic** networking. The background is that I have created VMs using KVM on my Ubuntu Desktop running Ubuntu Desktop 24.04 for a number of years. I have a Netplan YAML file for bridging that took me a long time to get right and that has served me well to enable the VM to talk to the internet and the host machine. This worked fine and my needs were simple. I have now created a VM on my Ubuntu Server (no GUI) and am able to configure using the VM Manager on my Ubuntu Desktop. I now want me VM to talk to the internet, and my local network physical machines, and for those machines to talk to the VM. At one point the VM would talk with everything, but not vice versa. I think I have now screwed everything up and it will not talk with anything - don't know why! My Ubuntu server is called MERLIN, with IP address 192.168.1.10. My Ubuntu Desktop is called CAMELOT, with IP address 192.168.1.11. My VM is called MORDRED (residing on MERLIN) and I want it to have a static IP adress of 192.168.1.18. MORDRED should be able to talk to CAMELOT and MERLIN. I don't think this is a big ask, is it? The Netplan YAML file on the server (MERLIN) is as follows: network: version: 2 #renderer: NetworkManager renderer: networkd ethernets: enp3s0: dhcp4: false dhcp6: false addresses: - 192.168.1.10/24 routes: - to: default via: 192.168.1.1 metric: 100 on-link: true mtu: 1500 nameservers: addresses: [8.8.8.8] bridges: br0: interfaces: [enp3s0] dhcp4: false dhcp6: false addresses: - 192.168.1.3/24 routes: - to: default via: 192.168.1.1 # metric: 100 on-link: true mtu: 1500 nameservers: addresses: [8.8.8.8] parameters: stp: true forward-delay: 4 Also in the Netplan folder on the server is an XML file as follows (not really sure what this is for, I put it there a few years ago. It worked so I left it alone): host-bridge The YAML file on the VM is as follows: network: version: 2 # renderer: NetworkManager renderer: networkd ethernets: enp1s0: dhcp4: false dhcp6: false addresses: - 192.168.1.18/24 routes: - to: default via: 192.168.1.1 metric: 100 on-link: true mtu: 1500 nameservers: addresses: [8.8.8.8, 8.8.4.4] The Virtual Network Interface in the VM Manager is set as follows: Network Source: Bridge Device... Device Name: br0 Device Model: virtio When I issue ifconfig on the server, I get the following: br0: flags=4163 mtu 1500 inet 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 2a0a:ef40:60:1801:6828:2dff:fee0:ae68 prefixlen 64 scopeid 0x0 inet6 fe80::6828:2dff:fee0:ae68 prefixlen 64 scopeid 0x20 ether 6a:28:2d:e0:ae:68 txqueuelen 1000 (Ethernet) RX packets 14531 bytes 1269556 (1.2 MB) RX errors 0 dropped 216 overruns 0 frame 0 TX packets 8082 bytes 15347032 (15.3 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp3s0: flags=4163 mtu 1500 inet 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255 ether e0:d5:5e:d1:d2:f2 txqueuelen 1000 (Ethernet) RX packets 15694 bytes 1543343 (1.5 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 17907 bytes 15946048 (15.9 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 5238 bytes 4812865 (4.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5238 bytes 4812865 (4.8 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099 mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:4e:3b:6e 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 vnet0: flags=4163 mtu 1500 inet6 fe80::fc54:ff:fea6:8243 prefixlen 64 scopeid 0x20 ether fe:54:00:a6:82:43 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1 bytes 90 (90.0 B) TX errors 0 dropped 2927 overruns 0 carrier 0 collisions 0 I don't know where the virbr0 and vnet0 come from. Probably not important! But on the VM, I am now only getting: lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 12965 bytes 922705 (922.7 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12965 bytes 922705 (922.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I was getting a lot more, but with my messing about I think I have totally screwed it up and can't get back to it. The annoying thing is that I did momentarily have everything as I wanted it, and decided to reboot everything to ensure that it all persisted - it didn't, and I am now in the situation I am in at the moment. So, if there are any strange men who normally wear hooded cloaks would like to whisper some strange incantations in my directions I would VERY much appreciate it. Regards, StuartM

Here is my YAML file:

network:
  ethernets:
    ens160:
      addresses:
      - 10.200.2.148/22
      gateway4: 10.200.0.1
      nameservers:
        addresses:
        - 1.1.1.1
        - 2.2.2.2
        - 3.3.3.3
        - 4.4.4.4
        search:
        - our.domain

I must replace all DNS addresses under ens160 with two specific addresses. I tried using this:

yq write -i /etc/netplan/00-installer-config.yaml  '.network.ethernets.ens160.nameservers.addresses' ['10.10.10.53','10.10.10.54']

... but all that did was shift all the list items in one like this:

network:
  ethernets:
    ens160:
      addresses:
        - 10.200.2.148/22
      gateway4: 10.200.0.1
      nameservers:
        addresses:
          - 1.1.1.1
          - 2.2.2.2
          - 3.3.3.3
          - 4.4.4.4
        search:
          - our.domain

I don't want that. I need the output to look like this:

network:
  ethernets:
    ens160:
      addresses:
      - 10.200.2.148/22
      gateway4: 10.200.0.1
      nameservers:
        addresses:
        - 10.10.10.53
        - 10.10.10.54
        search:
        - our.domain

It's not very clear how I can do this with yq. How can I accomplish this?

I've got a new server with a fresh Ubuntu 20.04 LTS install. I've got one interface connected to our main corporate network with a static IP address, and now need to connect a second interface to a separate backline network using a static IP address. 172.10.1.0/24 [eno1np0:172.1.1.10] [eno2np1:192.168.1.10] 192.168.1.0/24 public-router server_NIC_1 server_NIC_2 backline-router I've been doing network config with /etc/network/interfaces and ifconfig for years, and am stumped by netplan configs. I'm reading docs, and looking at examples and doing trial and error with no success. Here are the contents of /etc/netplan/00-installer-config.yaml: # This is the network config written by 'subiquity' network: ethernets: eno1np0: addresses: - 172.10.1.10/24 gateway4: 172.10.1.1 nameservers: addresses: - 172.10.1.32 - 172.10.1.33 search: - mycompany.com eno2np1: addresses: - 192.168.1.10/24 gateway4: 192.168.1.1 version: 2 Any thoughts on what I'm doing wrong? - John

So I've been learning how to set up my private server. I'm using netplan. According to some docs I found at https://netplan.readthedocs.io/en/stable/examples/# and a lengthy argument with Chatgpt on the right way to configure my yaml file, this is what I came up with.

network:
  version: 2
  renderer: networkd
  ethernets:
    enp2s0: 
      addresses:
        - 192.168.0.2/24
      gateway4: 192.168.0.1
      nameservers:
        addresses:
          - 8.8.8.8
          - 1.1.1.1

I get the "gateway4 is deprecated" error and I've found a wealth of knowledge on how to set up routes with via and to, but I have not found on the internet *why* gateway4 is deprecated. Is it merely syntactical or is it for some other reason? Please be aware I am **NOT ASKING A DUPLICATE QUESTION**. I am asking the specific difference between the deprecated way and the newer way and *why*.

I have been trying to turn my old laptop into a server so that I can try hosting few projects to showcase, so I have installed Ubuntu server and experimenting with it and I have connected to the server using the ssh connection using the ssh-key pairs and its was successful, and I have also set the IP address to be static on the Wi-Fi interface to which internet is connected. The problem is if I try connecting to the same server after being away from the server (terminated ssh client) say for 15 mins or so I am not able to connect to the server again until I restart the Network Manager on the server directly. I have tried everything like turning power saving mode on wifi in case its disabling the interface while idle and also assigned static IP address in the file 00-installer-wifi-config.yaml file in netplan and the static IP address is assigned as well. One interesting thing to note is that when I check the server connection using the ifconfig command if everything is running properly while my client is not able to connect to server everything seems fine on server perfect pinging google.com works on server, static IP available, ssh service running properly but still I need to restart Network Manager every time to connect and once I restart the Network Manager the client connects flawlessly. Here is the relevant configuration for problem this is present in /etc/netplan/00-installer-wifi-config.yaml : network: version: 2 renderer: NetworkManager wifis: wlp1so: dhcp4: false addresses: - 192.168.1.***/24 nameservers: addresses: [8.8.8.8, 8.8.4.4] routes: - to: default via: 192.***.*.* access-points: "Parker": password: "**********" Note: the above configuration is only for the static address, and I was the facing the same issue even before using the above config where I had dhcp4 to be true. I changed to static just in hope to resolve the issue, but I had no luck. Network Manager logs:

Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7582] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7598] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7632] manager: (FC:D4:36:07:EF:87): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/4)
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7637] device (FC:D4:36:07:EF:87): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7657] manager: (FC:DE:90:24:40:1A): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/5)
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7666] device (FC:DE:90:24:40:1A): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7677] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7680] device (FC:D4:36:07:EF:87): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7683] device (FC:DE:90:24:40:1A): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7687] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7695] device (lo): Activation: successful, device activated.
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.7707] modem-manager: ModemManager available
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.8773] device (wlp1s0): supplicant interface state: internal-starting -> disconnected
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.8779] Wi-Fi P2P device controlled by interface wlp1s0 created
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.8797] manager: (p2p-dev-wlp1s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/6)
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.8812] device (p2p-dev-wlp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.8838] device (wlp1s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Dec 13 23:51:59 my-ubuntu-server NetworkManager:   [1734133919.8869] device (p2p-dev-wlp1s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9342] policy: auto-activating connection 'CSS Parker' (7eabc9ff-3833-48b6-aca0-243230b32503)
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9349] device (wlp1s0): Activation: starting connection 'CSS Parker' (7eabc9ff-3833-48b6-aca0-243230b32503)
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9350] device (wlp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9354] manager: NetworkManager state is now CONNECTING
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9361] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9366] device (wlp1s0): Activation: (wifi) access point 'CSS Parker' has security, but secrets are required.
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9366] device (wlp1s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9379] device (wlp1s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9382] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9386] device (wlp1s0): Activation: (wifi) connection 'CSS Parker' has security, and secrets exist.  No new secrets needed.
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9386] Config: added 'ssid' value 'CSS Parker'
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9386] Config: added 'scan_ssid' value '1'
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9387] Config: added 'bgscan' value 'simple:30:-65:300'
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9387] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9387] Config: added 'auth_alg' value 'OPEN'
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9387] Config: added 'psk' value ''
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9588] device (wlp1s0): supplicant interface state: disconnected -> authenticating
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9588] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> authenticating
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9624] device (wlp1s0): supplicant interface state: authenticating -> associating
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9624] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9709] device (wlp1s0): supplicant interface state: associating -> associated
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9709] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> associated
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9967] device (wlp1s0): supplicant interface state: associated -> completed
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9967] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "CSS Parker"
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9967] device (p2p-dev-wlp1s0): supplicant management interface state: associated -> completed
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9969] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 13 23:52:02 my-ubuntu-server NetworkManager:   [1734133922.9976] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Dec 13 23:52:03 my-ubuntu-server NetworkManager:   [1734133923.0046] dhcp4 (wlp1s0): state changed new lease, address=192.168.1.106, acd pending
Dec 13 23:52:03 my-ubuntu-server NetworkManager:   [1734133923.1472] dhcp4 (wlp1s0): state changed new lease, address=192.168.1.106
Dec 13 23:52:03 my-ubuntu-server NetworkManager:   [1734133923.1494] policy: set 'CSS Parker' (wlp1s0) as default for IPv4 routing and DNS
Dec 13 23:52:03 my-ubuntu-server NetworkManager:   [1734133923.2524] device (wlp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dec 13 23:52:03 my-ubuntu-server NetworkManager:   [1734133923.2572] device (wlp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dec 13 23:52:03 my-ubuntu-server NetworkManager:   [1734133923.2577] device (wlp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dec 13 23:52:03 my-ubuntu-server NetworkManager:   [1734133923.2586] manager: NetworkManager state is now CONNECTED_SITE
Dec 13 23:52:03 my-ubuntu-server NetworkManager:   [1734133923.2600] device (wlp1s0): Activation: successful, device activated.
Dec 13 23:52:03 my-ubuntu-server NetworkManager:   [1734133923.2613] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec 13 23:52:05 my-ubuntu-server NetworkManager:   [1734133925.5534] manager: startup complete

I'm having trouble setting up 2 IP address so that if one fails it will use the secondary IP address. I've setup netplan as shown in the picture. I can connect via ssh using both IP address, I test which IP address is the main one by using speedtest-cli, using the server control panel I disable the IP address that was used by speedtest-cli. However, when I try to use speedtest-cli again it doesn't work, I expected it to automatically switch to the IP that is still available. I tried pinging known IP address but it doesn't work. Does anyone know why this isn't working as I expect it to and how I can get it working? 

I have a requirement and this was working (up to 2020) without issue. As my installs were outdated and I didn't care to actually UPGRADE, I decided to blitz the lot and begin with fresh installs using Ubuntu 23.04 for servers and 24.04 for my desktop. I am creating this via Virtualbox setup and have two host-only networks: 192.168.110.x and 192.168.120.x. Any server installs will be in either 110 or 120. The desktop has 3 NICs: * enp0s3=NAT (10.0.2.15) * enp0s8=192.168.110.3 * enp0s9=192.168.120.3. I have set IP forwarding on the desktop to route 110 and 120 through enp0s3 using IP tables. All this was working when gateway was a valid declaration in netplan. However, now the setup is different, I have been looking at the netplan examples provided via a different question and can find nothing which might match MY needs. I am finding it a bit confusing to work out the routing declarations for each network. As an aside, rather than declaring nameservers twice, can I somehow just specify it once for all ethernets? 1 # Let NetworkManager manage all devices on this system 2 network: 3 version: 2 4 renderer: NetworkManager 5 ethernets: 6 enp0s8: #Edit this line according to your network interface name. 7 dhcp4: no 8 addresses: 9 - 192.168.110.3/24 10 routes: 11 - to: default 12 via: 192.168.110.1 13 nameservers: 14 addresses: 15 - 8.8.8.8 16 - 8.8.4.4 17 enp0s9: #Edit this line according to your network interface name. 18 dhcp4: no 19 addresses: 20 - 192.168.120.3/24 21 routes: 22 - to: default 23 via: 192.168.120.1 24 nameservers: 25 addresses: 26 - 8.8.8.8 27 - 8.8.4.4 28 The error I am getting is: > Problem encountered while validating default route consistency.Please > set up multiple routing tables and use routing-policy instead. > > Error: Conflicting default route declarations for IPv4 (table: main, > metric: default), first declared in enp0s8 but also in enp0s9

When using netplan generate I kept on getting an error message: > gateway4 has been deprecated, use default routes instead. For static IP address assignments in netplan, I've always used the structure:

network:
  version: 2
  renderer: networkd
  ethernets:
    eno1:
      dhcp4: false
      dhcp6: false
      addresses:
      - 192.168.10.10/24
      gateway4: 192.168.10.1
      nameservers:
      addresses: [192.168.10.1]

Obviously gateway4 is referencing gateway4: 192.168.10.1, but how do we fix it?

I have a Ubuntu 20.04.6 LTS using dhcp. Everytime I reboot the ip-address gets changed but not DNS. I'd like to keep the same ip-address. I have changed my /etc/netplan/01-netcfg.yaml as : network: version: 2 renderer: networkd ethernets: enp6s0: dhcp4: true critical: true # dhcp4: no addresses: [10.3.XXX.XXX/24] nameservers: search: [mydomain.org] addresses: [10.3.XXX.XXX,130.221.XXX.XXX] I have not run the "netplan apply" since I am not confident of my changes. Any help would be great. Thanks in advance.

I am attempting to install netplan on Rocky 9.3 which has no direct internet connection. So I am trying to install packages via rpm and if see a failed dependency find it and scp it to the PC (Intel PC running Rocky 9.3).

[user@localhost ~]$ rpm -i netplan-0.105-3.el9.x86_64.rpm 
warning: netplan-0.105-3.el9.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 3228467c: NOKEY
error: Failed dependencies:
	netplan-default-backend is needed by netplan-0.105-3.el9.x86_64
	netplan-libs(x86-64) = 0.105-3.el9 is needed by netplan-0.105-3.el9.x86_64

So I then try to install netplan-libs:

[user@localhost ~]$ sudo rpm -i netplan-libs-0.105-3.el9.x86_64.rpm
warning: netplan-libs-0.105-3.el9.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 3228467c: NOKEY
	package netplan-libs-0.105-4.el8.x86_64 (which is newer than netplan-libs-0.105-3.el9.x86_64) is already installed
        file /usr/lib64/libnetplan.so.0.0 from install of netplan-libs-0.105-3.el9.x86_64 conflicts with file from package netplan-libs-0.105-4.el8.x86_64

Then I try to remove what I thought was the wrong netplan-libs as in:

[user@localhost ~]$ sudo rpm -e netplan-libs-0.105-4.el8.x86_64.rpm 
error: package netplan-libs-0.105-4.el8.x86_64.rpm is not installed

Then I try to verify netplan:

[user@localhost ~]$ sudo rpm -V netplan-0.105-3.el9.x86_64.rpm 
[sudo] password for user: 
warning: netplan-0.105-3.el9.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 3228467c: NOKEY
Unsatisfied dependencies for netplan-0.105-3.el9.x86_64:
	netplan-default-backend is needed by netplan-0.105-3.el9.x86_64
	netplan-libs(x86-64) = 0.105-3.el9 is needed by netplan-0.105-3.el9.x86_64
missing   a /usr/lib/.build-id/a0/424de64ac60e79c18b7576b8e659fbef189232
missing   a /usr/lib/.build-id/ea/c29b62d5d3489d3841c17fa80c2f9ee68d3180
missing     /usr/lib/netplan
missing     /usr/lib/netplan/generate
missing     /usr/lib/netplan/netplan-dbus
missing     /usr/lib/systemd/system-generators/netplan
missing     /usr/sbin/netplan
missing     /usr/share/bash-completion/completions/netplan
missing     /usr/share/dbus-1/system-services/io.netplan.Netplan.service
missing     /usr/share/dbus-1/system.d/io.netplan.Netplan.conf
missing     /usr/share/doc/netplan
missing     /usr/share/doc/netplan/examples
missing   d /usr/share/doc/netplan/examples/bonding.yaml
missing   d /usr/share/doc/netplan/examples/bonding_router.yaml
missing   d /usr/share/doc/netplan/examples/bridge.yaml
missing   d /usr/share/doc/netplan/examples/bridge_vlan.yaml
missing   d /usr/share/doc/netplan/examples/dhcp.yaml
missing   d /usr/share/doc/netplan/examples/dhcp_wired8021x.yaml
missing   d /usr/share/doc/netplan/examples/direct_connect_gateway.yaml
missing   d /usr/share/doc/netplan/examples/direct_connect_gateway_ipv6.yaml
missing   d /usr/share/doc/netplan/examples/infiniband.yaml
missing   d /usr/share/doc/netplan/examples/ipv6_tunnel.yaml
missing   d /usr/share/doc/netplan/examples/loopback_interface.yaml
missing   d /usr/share/doc/netplan/examples/modem.yaml
missing   d /usr/share/doc/netplan/examples/network_manager.yaml
missing   d /usr/share/doc/netplan/examples/offload.yaml
missing   d /usr/share/doc/netplan/examples/openvswitch.yaml
missing   d /usr/share/doc/netplan/examples/route_metric.yaml
missing   d /usr/share/doc/netplan/examples/source_routing.yaml
missing   d /usr/share/doc/netplan/examples/sriov.yaml
missing   d /usr/share/doc/netplan/examples/sriov_vlan.yaml
missing   d /usr/share/doc/netplan/examples/static.yaml
missing   d /usr/share/doc/netplan/examples/static_multiaddress.yaml
missing   d /usr/share/doc/netplan/examples/static_singlenic_multiip_multigateway.yaml
missing   d /usr/share/doc/netplan/examples/vlan.yaml
missing   d /usr/share/doc/netplan/examples/vrf.yaml
missing   d /usr/share/doc/netplan/examples/vxlan.yaml
missing   d /usr/share/doc/netplan/examples/windows_dhcp_server.yaml
missing   d /usr/share/doc/netplan/examples/wireguard.yaml
missing   d /usr/share/doc/netplan/examples/wireless.yaml
missing   d /usr/share/doc/netplan/examples/wpa_enterprise.yaml
missing   d /usr/share/doc/netplan/netplan.html
missing     /usr/share/licenses/netplan
missing   l /usr/share/licenses/netplan/COPYING
missing   d /usr/share/man/man5/netplan.5.gz
missing   d /usr/share/man/man8/netplan-apply.8.gz
missing   d /usr/share/man/man8/netplan-dbus.8.gz
missing   d /usr/share/man/man8/netplan-generate.8.gz
missing   d /usr/share/man/man8/netplan-get.8.gz
missing   d /usr/share/man/man8/netplan-set.8.gz
missing   d /usr/share/man/man8/netplan-try.8.gz
missing     /usr/share/netplan/netplan.script
missing     /usr/share/netplan/netplan/__init__.py
missing     /usr/share/netplan/netplan/_features.py
missing     /usr/share/netplan/netplan/cli/__init__.py
missing     /usr/share/netplan/netplan/cli/commands/__init__.py
missing     /usr/share/netplan/netplan/cli/commands/apply.py
missing     /usr/share/netplan/netplan/cli/commands/generate.py
missing     /usr/share/netplan/netplan/cli/commands/get.py
missing     /usr/share/netplan/netplan/cli/commands/info.py
missing     /usr/share/netplan/netplan/cli/commands/ip.py
missing     /usr/share/netplan/netplan/cli/commands/migrate.py
missing     /usr/share/netplan/netplan/cli/commands/set.py
missing     /usr/share/netplan/netplan/cli/commands/sriov_rebind.py
missing     /usr/share/netplan/netplan/cli/commands/try_command.py
missing     /usr/share/netplan/netplan/cli/core.py
missing     /usr/share/netplan/netplan/cli/ovs.py
missing     /usr/share/netplan/netplan/cli/sriov.py
missing     /usr/share/netplan/netplan/cli/utils.py
missing     /usr/share/netplan/netplan/configmanager.py
missing     /usr/share/netplan/netplan/libnetplan.py
missing     /usr/share/netplan/netplan/terminal.py

How do I reliably install netplan. I have downloaded what seem to be all the dependent files:

ls -l
-rwxr--r--. 1 user user  123581 Jun 24 14:39 netplan-0.105-3.el9.x86_64.rpm
-rwxr--r--. 1 user user    8221 Jun 24 15:21 netplan-default-backend-networkd-0.105-3.el9.noarch.rpm
-rwxr--r--. 1 user user    8273 Jun 24 15:35 netplan-default-backend-NetworkManager-0.105-3.el9.noarch.rpm
-rwxr--r--. 1 user user    8636 Jun 24 15:10 netplan-default-backend-NetworkManager-0.105-4.el8.noarch.rpm
-rwxr--r--. 1 user user  126265 Jun 24 15:40 netplan-libs-0.105-3.el9.x86_64.rpm
-rwxr--r--. 1 user user  123788 Jun 24 15:05 netplan-libs-0.105-4.el8.x86_64.rpm
-rwxr--r--. 1 user user   20996 Jun 24 15:13 NetworkManager-config-server-1.46.0-8.el9_4.noarch.rpm
-rwxr--r--. 1 user user   23050 Jun 24 15:15 python3-netifaces-0.10.6-15.el9.x86_64.rpm
-rwxr--r--. 1 user user  195078 Jun 24 15:18 python3-pyyaml-5.4.1-6.el9.x86_64.rpm

The most immediate problem I have is that I can't install netplan-libs-0.105-3.el9.x86_64.rpm because I get:

[user@localhost ~]$ sudo rpm -i netplan-libs-0.105-3.el9.x86_64.rpm 
[sudo] password for user: 
warning: netplan-libs-0.105-3.el9.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 3228467c: NOKEY
	package netplan-libs-0.105-4.el8.x86_64 (which is newer than netplan-libs-0.105-3.el9.x86_64) is already installed
	file /usr/lib64/libnetplan.so.0.0 from install of netplan-libs-0.105-3.el9.x86_64 conflicts with file from package netplan-libs-0.105-4.el8.x86_64

So I try to remove netplan-libs-0.105-4.el8.x86_64 like this:

[user@localhost ~]$ sudo rpm -e netplan-libs-0.105-4.el8.x86_64.rpm 
error: package netplan-libs-0.105-4.el8.x86_64.rpm is not installed

Can I manually remove /usr/lib64/libnetplan.so.0.0 ? Or will that cause more problems? What is the best way to fix this?

I have an existing 01-netcfg.yaml file from documentation which is supposed to have worked previously.

network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      dhcp4: no
      dhcp6: no
      addresses: []212.80.140.1/32]
      gateway4: 62.210.0.1
      nameservers:
        addresses: [62.210.16.6, 62.210.16.7]
      routes:
      - to: 62.210.0.1/32
        via: 212.80.140.1
        scope: link

This config is for a secondary or failover IP4 in a Virtual Machine inside a hypervisor (Proxmox PVE) on the Scaleway network . I cannot any longer use the Gateway4 field in Netplan on Ubuntu 22.04. Running netplan apply fails with the error:

gateway4 has been deprecated, use default routes instead

I believe I must update the syntax to use the routes field instead of gateway4 but I cannot get the syntax right. The default gateway is outside of the subnet of the main address so it needs additional configuration. Maybe onlink, source routing, routing tables etc. I don't know. http://people.ubuntu.com/~slyon/netplan-docs/examples/#reaching-a-directly-connected-gateway Can anyone convert the given config to use routes etc. instead of gateway4?

After running a PURGE on the system, NETPLAN is no longer present on the HD. So from terminal invoking the command netplan apply I get netplan: command not found. Naturally the network functionality is gone and obviously I can no longer use apt install netplan, or other such remedies. Is there any way, maybe with a minimal cd, without having to reinstall the software from scratch?

Using netplan / networkd for wifi and I'd like to do the following network: version: 2 wifis: wlx1cbfceac3e27: match: macaddress: 01:d2:f3:c4:95:96 set-name: wlan0 dhcp4: no addresses: - 192.168.10.2/24 access-points: "Linux is the best": password: "yobeach" However, netplan interjects networkd backend does not support wifi with match:, only by interface name Since set-name requires a match, is there another way in the netplan syntax to change the name to wlan0 (not using udev)

I have Ubuntu 20.04 running on Raspberry Pi4 and have a 5G HAT to get it connected to the internet. I have a wwan0 network interface with the IP. Now I'd like to make this network available as an access point to other devices. I tried to use a netplan, but it seems to work only with eth0 interface. Is there any way to make it work?

I am switching from Ubuntu to Debian, but - as I can only access the VM via ssh - I very much miss the netplan try feature. Whenever I mess up the /etc/network/interfaces, I am out and need help from the hoster. Installing netplan on Debian Buster is simple enough (apt install netplan.io), but whatever I then do to the /etc/netplan/*.yaml file, it seems to have no effect. When I try the new configuration (via netplan try) it says that the new configuration would be in effect, but ip address says that it is not. So my question is: How do I actually switch control over the network interfaces over from networking to netplan?

I have this server that loses its network config on reboots, it's running Ubuntu Server 18.04, I tried the netplan commands but none generated a thing, maybe it's because the interface isn't even there until I run dhclient, only then the system brings the interface up and DHCP assigns it its static address. On boot, only the loopback interface is brought up automatically. Instead of going crazy trying to decipher netplan--which most likely I'm not going to use much since I loathe Ubuntu for some reason--I'd like to go around it and just automatically run dhclient upon boot. Would something like a cron job work? Do I need to assign special permissions somewhere or have special permissions? Thanks for your help!