Request: autoconnect of `network-setup-control` for network-manager snap

store
1

It looks like this one is not performed by default:

$ snap interfaces network-manager
Slot                     Plug
:firewall-control        network-manager,wifi-ap
:network-setup-observe   network-manager
:ppp                     network-manager
modem-manager:service    modem-manager:mmcli,network-manager:modem-manager
network-manager:service  network-manager:nmcli,wifi-ap:network-manager
-                        network-manager:network-setup-control
-                        network-manager:wpa
2

It has a snap declaration for ‘network-setup-observe’ already. My understanding was that netplan could hand off configuration to network-manager, but I was unaware that network-manager could configure netplan. I don’t see anything obvious in the network-manager sources on netplan support.

Can you provide more details on why network-manager needs to write netplan configuration?

3

network-manager needs to modify netplan files so it can set itself as the default renderer, otherwise netplan selects networkd as the default renderer for ethernet devices.

4

+1 for granting network-setup-control to the snap.

5

There aren’t enough votes to tally. @mvo, @sergiusens, @Wimpress, @ratliff, @natalia: ca n one/all of you vote on this?

6

+1

snap info network-manager
name:      network-manager
summary:   Network management based on NeworkManager
publisher: canonical
contact:   https://help.ubuntu.com/community/NetworkManager
license:   GPL-2.0
description: |
  Network management of wired ethernet, WiFi and mobile data connection based on
  NetworkManager and ModemManager
snap-id: RmBXKl6HO6YOC2DE4G2q1JzWImC04EUy
channels:                       
  stable:    1.2.2-15     (263) 5MB -
  candidate: 1.2.2-15     (263) 5MB -
  beta:      1.2.2-15     (263) 5MB -
  edge:      1.2.2-16-dev (271) 5MB -
7

+1 from me.

8

3 votes for, 0 against. Granting auto-connection. This is now live.

9

Awesome, thanks! +20 chars