Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • Connman is the default connection manager for some lightweight desktop environments like LXQt so it's not only for embedded devices. Commented Aug 17 at 17:25
  • @AugustKarlstrom as said, yes, it was definitely written for that, and the people maintaining it are from the embedded world. It doesn't preclude usage on a desktop distro, at all, but it's missing a lot of the dynamic reconfiguration and user interaction focus that the mainstream has, so yes, it's harder to configure for most mainstream use cases – as you are noticing yourself. This would have been two clicks (or a single nmcli invocation) on a NetworkManager system! Again, not criticising, just pointing out that you're using something not as easily convinced to work for your use case. Commented Aug 17 at 17:35
  • When the WiFi is re-enabled with Connman it connects to the default access point (see updated question). I have no idea why it cannot connect automatically on boot. Commented Aug 17 at 19:12
  • how precisely are you making sure it uses the right device? and what has device selection to do with the AP? Very confused here. Commented Aug 17 at 19:40
  • I have tried blacklisting the built-in interface wlan0 so that it doesn't show up in the list of available interfaces. The USB interface starts working after re-enabling it. Since wlan0 is now blacklisted I know that the USB interface is in use. The question is why I need to re-enable it. By the way, is there a command to just switch it from idle to accepting traffic. In idle state I see no list of access points. Commented Aug 17 at 20:02