Setting WiFi Static IP Address using Netplan with Network Manager

Bug #1905465 reported by Kyron Longwood
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Netplan
New
Undecided
Unassigned

Bug Description

OS info: Ubuntu 18.04.5 LTS (GNU/Linux 5.4.0-53-generic x86_64) Desktop

netplan version:

#apt-cache policy netplan.io
netplan.io:
  Installed: 0.99-0ubuntu3~18.04.3
  Candidate: 0.99-0ubuntu3~18.04.3
  Version table:
 *** 0.99-0ubuntu3~18.04.3 500
        500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     0.40.1~18.04.4 500
        500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
     0.36.1 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

The task to accomplish here is to establish a static ip address on the wifi interface using netplan rendered with Network Manager. Default netplan YAML file is defined shown below:

#01-network-manager-all.yaml
network:
version: 2
renderer: NetworkManager

Below is the following configurations are set and defined using sudo netplan apply for static ip address:

network:
  version: 2
  renderer: NetworkManager
  wifis:
    wlp1s0:
      addresses: [192.168.1.212/24]
      dhcp4: no
      dhcp6: no
      gateway4: 192.168.1.1
      nameservers:
        addresses: [192.168.1.1]
      access-points:
        accesspointename:
          password: passwordgoeshere

However after setting a static ip address, the device still has same ip4 address assigned before set by DHCP from router with no change. Also running the command nmcli con show, it lists a new connection:

netplan-wlp1s0-accesspointename 566d6c1e-3731-3b4a-9018-2f7b321324ce wifi --

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.