On Mon, Oct 27, 2014 at 3:39 PM, Dan Williams <d...@redhat.com> wrote: > On Fri, 2014-10-24 at 11:18 +0200, Andreas Müller wrote: >> On Fri, Oct 24, 2014 at 10:43 AM, Thomas Haller <thal...@redhat.com> wrote: >> > On Fri, 2014-10-24 at 10:19 +0200, Andreas Müller wrote: >> >> Hi, >> > >> >> Now my question: >> >> >> >> What does it need to start hotspot automatically after boot? If there >> >> is no setting available I could create a script/app using >> >> Networkmanager's dbus >> >> >> >> I would be very happy if somebody could help me because for me this is >> >> the last part of the puzzle and solving would make me run in happy >> >> mode :) >> > >> > >> > you certainly could use the DBUS interface. >> > But maybe it's easier to use "nmcli connection up"? >> > >> > >> > Thomas >> Thomas, you are my hero of the day - thanks a lot. > > If there are no other WiFi connections defined on the system (nmcli con > | grep wireless) and the AP connection is the only one, and set > autoconnect=true, then NM will always bring that connection up when > starting. If you do have other wifi connections that you periodically > use, you could set all of them autoconnect=no, and NM will ignore them > and always start the AP connection. > > Dan > Sorry for late response - but autoconnect=true did not work - that's why I asked here. Have a 'fresh' embedded system not connected to other access points before.
I am using networkmanager 0.9.8.10 - other (eth0 / wlan connections to other hotspots) autoconnections seem to work... Andreas _______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
