Timeline for connman: Permanently disable built-in WiFi interface
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 18 at 20:20 | comment | added | August Karlstrom | Yes, maybe it's best to ask a new question as I apparently fell into the XY problem trap. :-) | |
| Aug 18 at 20:16 | comment | added | Marcus Müller | ok, is that still the question you're asking in your question post here? Or does this warrant opening a new question? (honestly, I can't follow your terminology there, so I couldn't help you here.) | |
| Aug 18 at 20:15 | comment | added | August Karlstrom | I was a bit imprecise in my last comment. What I meant was that I have blacklisted the driver b43 for the built-in WiFi. The USB WiFi has a stable name which is wlx98ba5fa6d7f8. To summarize the current situation: When the computer is started the state of the interface is idle. My workaround for the moment is to disable the WiFi and then enable it. This makes the interface connect to the previously saved access point. The question is why the interface is idle at first. | |
| Aug 18 at 10:13 | comment | added | Marcus Müller | ah, that does not suffice, because "wlan0" is a name that gets assigned to the first wlan device that shows up. You need to use a stable interface name – something like wlp6s0 – so that you can use the device name for blacklisting. Assigning stable names is, iirc, however, the default setting for debian's udev setup though, and I think it's explicitly recommended by the old (offline) connman documentation? So, I'm not sure why your system isn't using stable device names there, you might need to look into that. | |
| Aug 17 at 20:02 | comment | added | August Karlstrom | 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. | |
| Aug 17 at 19:40 | comment | added | Marcus Müller | how precisely are you making sure it uses the right device? and what has device selection to do with the AP? Very confused here. | |
| Aug 17 at 19:12 | comment | added | August Karlstrom | 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. | |
| Aug 17 at 17:35 | comment | added | Marcus Müller |
@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.
|
|
| Aug 17 at 17:25 | comment | added | August Karlstrom | Connman is the default connection manager for some lightweight desktop environments like LXQt so it's not only for embedded devices. | |
| Aug 17 at 13:58 | history | edited | Marcus Müller | CC BY-SA 4.0 |
added 19 characters in body
|
| Aug 17 at 13:46 | history | edited | Marcus Müller | CC BY-SA 4.0 |
added 719 characters in body
|
| Aug 17 at 13:38 | history | edited | Marcus Müller | CC BY-SA 4.0 |
added 719 characters in body
|
| Aug 17 at 13:30 | history | answered | Marcus Müller | CC BY-SA 4.0 |