On Mon, 2015-07-27 at 22:22 +0200, Jean-Christian de Rivaz wrote: > Le 27. 07. 15 19:32, Dan Williams a écrit : > > On Mon, 2015-07-27 at 19:24 +0200, Jean-Christian de Rivaz wrote: > >> Le 27. 07. 15 16:36, Dan Williams a écrit : > >>> On Mon, 2015-07-27 at 13:30 +0200, Jean-Christian de Rivaz wrote: > >>>> In this observation NetworkManager still think that eth0 is disconnected > >>>> while he correctly logged the message 'link connected': > >>> Just to make sure, the ethernet connection being used is > >>> autoconnect=true, right? > >>> > >>> nmcli con show "<the connection name>" | grep autoconnect > >>> > >>> will tell you. > >> nmcli con show "Wired connection 1" | grep autoconnect > > Wow, seriously what's the point to create a such complicated name when > everything from the kernel to probably virtually all applications use > 'eth0' ?
Because a 'connection' is not the same thing as a network device. It's a collection of configuration that can be applied to the device. It's fine to have more than one, for example a static config and a DHCP config for the same interface. They cannot both be named the same thing as they must be individually configurable and applicable to the interface. > # nmcli con show "Wired connection 1" | grep autoconnect > connection.autoconnect: yes > > I hope that 'true' and 'yes' are equal in this context, so I think this > is not the cause of the observed problem. Correct, it's not the cause. But something we need to rule out. So now, getting a debug log from NetworkManager is the next thing. You can use "nmcli g log level debug" and then attempt to reproduce the problem, and then lets see what the log say. Dan _______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
