On Tue, 2016-11-15 at 18:50 +0100, poma wrote:
On 15.11.2016 16:29, Thomas Haller wrote:On Tue, 2016-11-15 at 10:35 +0100, poma wrote:The applet offers "Auto Ethernet" despite that this feature is explicitly disabled in the configuration. A bug, or a feature?Hi, These two things are not the same.Did you mean the correlation in terms of interaction?
1) "default-wired-connection" is in the server, which is related to the configuration parameter "no-auto-default" in NetworkManger.conf 2) the UI field "Auto Ethernet" in nm-applet They are not the same thing. 2) is not implemented in terms of 1). 1) is a server-only thing 2) is a nm-applet thing -- To realize this, nm-applet of course talks to the server too. But large parts of the logic happen in nm-applet.
In the server, "auto default connections" are there so that you can boot a machine without any connections and NetworkManager will create a (default) connection automatically. "no-auto-default" in NetworkManager.conf disables this.What exactly does mean -server- in "In the server"?
NetworkManager is a server/daemon to configure networking. "in the server" means something that happens in the NetworkManager process. Sometimes things happen in the server as result of command from a client via D-Bus. Not in case of 1). No client interaction is involved there.
The "Auto Ethernet" in nm-applet, creates a new connection from client side, and activates it.Did you mean, NetworkManager via the applet offers "Ad hoc" Ethernet connection, and user can eventually consume it?
Clicking 2), cause - nm-applet to constuct a new connection (client-side) - send the new connection via D-Bus to NetworkManager (server-side) - server stores the new connection - server activates the new connection. does that make any sense? Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part