Re: NetworkManager autoconnects to profiles in reverse order



Thanks for your reply, Beniamino.

Unfortunately no. I checked the Ubuntu backports for 14.04 (trusty), but there are no updated versions available. An upgrade to 16.04 LTS is not an option at this time.

I can report some progress in this matter though. I've just now made a small adjustment to the source code, and it seems to have fixed the issue. The last connected profile now autoconnects on boot. However, I am not a developer (my C knowledge is very limited) and what I've done might be extremely hacky and just plain wrong :) I could use someone with more insight into the network-manager source code to validate or tweak my simple fix. I made the change based on an educated guess, but I don't fully understand the inner workings of how the autoconnecting works. Any help in validating this is greatly appreciated.

This is the patch I made to nm-device.c:

--- nm-device.c 2016-08-10 13:45:09.000000000 +0200
+++ nm-device_patched.c 2016-08-10 13:46:30.408878875 +0200
@@ -1267,7 +1267,7 @@
                s_con = nm_connection_get_setting_connection (connection);
                g_assert (s_con);
                if (nm_setting_connection_get_autoconnect (s_con))
-                       available_conns = g_slist_prepend (available_conns, connection);
+                       available_conns = g_slist_append (available_conns, connection);
        }

        if (!available_conns)

Patch included as attachment also.

Best regards,
Simon Wydooghe



On Wed, Aug 10, 2016 at 11:23 AM, Beniamino Galvani <bgalvani redhat com> wrote:
On Mon, Aug 08, 2016 at 09:53:22PM +0200, Simon Wydooghe wrote:
> Fot his, we need to provide four NetworkManager profiles, one DHCP and
> three static. It seems I've stumbled onto a bug with
> NetworkManager 0.9.8.8. When I select a profile manually and reboot,
> NetworkManager connects to the profile that has the oldest timestamp. So
> it's not connecting to the last used profile, which is of course very
> troublesome.

This is probably a bug, but 0.9.8.8 is quite old; are there any newer
NetworkManager versions for your distribution that you can try?

Beniamino

Attachment: autoconnect.patch
Description: Text Data



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]