Return to Answer

You can prevent connman from configuring a network interface at all, by adding it to the comma-separated NetworkInterfaceBlacklist= list in the [General] section of /etc/connman/main.conf.

However, it would seem strange to me to do that – instead, I'd simply configure my connections to only use the wifi device of choice, not the one you don't want. You'd do that by (either using a connman configuration frontend, or) editing /var/lib/connman/wifi_{network id}/settings and setting the DeviceName= accordingly.

Note that ConnMan understands itself, to quote

ConnMan is a daemon for managing Internet connections within embedded device

I.e., for devices that aren't used as "computers", but as some other device class that integrates a Linux computer under the hood; quite for the opposite of what a macbook is! It certainly works for that, and the remaining ConnMan developers¹, but you're really doing a bit of a niche choice in infrastructure there – not a criticism, just so that you're aware that if things feel "hard to use", then that's because you picked the hard route.

¹ intel wrote ConnMan (so much for "anti-big compute" conspiracy theories that are usually used to discredit NetworkManager…), but drastically reduced involvement in the project around 2012; one could argue that they lost interest. These days, the project is still active, and the Jolla project (embedded connection manager for a tablet/phone operating system competing with Android) as well as a lot of deeply embedded companies (windriver, LG's home appliances, room lighting companies, …); the same people working on embedded bluetooth appliances in the linux kernel are also regular contributors. So, it's really an active Linux project, but I'd say that the people driving it have a different set of goals than the people driving end-user Linux distros, for actual humans sitting in front of a Linux laptop.

You can prevent connman from configuring a network interface at all, by adding it to the comma-separated NetworkInterfaceBlacklist= list in the [General] section of /etc/connman/main.conf.

However, it would seem strange to me to do that – instead, I'd simply configure my connections to only use the wifi device of choice, not the one you don't want. You'd do that by (either using a connman configuration frontend, or) editing /var/lib/connman/wifi_{network id}/settings and setting the DeviceName= accordingly.

Note that ConnMan understands itself, to quote

ConnMan is a daemon for managing Internet connections within embedded device

I.e., for devices that aren't used as "computers", but as some other device class that integrates a Linux computer under the hood; quite for the opposite of what a macbook is! It certainly works for that, and the remaining ConnMan developers¹, but you're really doing a bit of a niche choice in infrastructure there – not a criticism, just so that you're aware that if things feel "hard to use", then that's because you picked the hard route.

¹ intel wrote ConnMan (so much for "anti-big compute" conspiracy theories that are usually used to discredit NetworkManager…), but drastically reduced involvement in the project around 2012; one could argue that they lost interest. These days, the project is still active, and the Jolla project (embedded connection manager for a tablet/phone operating system competing with Android) as well as a lot of deeply embedded companies (windriver, LG's home appliances, room lighting companies, …) contribute heavily; the same people working on embedded bluetooth appliances in the linux kernel are also regular contributors. So, it's really an active Linux project, but I'd say that the people driving it have a different set of goals than the people driving end-user Linux distros, for actual humans sitting in front of a Linux laptop.

You can prevent connman from configuring a network interface at all, by adding it to the comma-separated NetworkInterfaceBlacklist= list in the [General] section of /etc/connman/main.conf.

However, it would seem strange to me to do that – instead, I'd simply configure my connections to only use the wifi device of choice, not the one you don't want. You'd do that by (either using a connman configuration frontend, or) editing /var/lib/connman/wifi_{network id}/settings and setting the DeviceName= accordingly.

Note that ConnMan understands itself, to quote

ConnMan is a daemon for managing Internet connections within embedded device

I.e., for devices that aren't used as "computers", but as some other device class that integrates a Linux computer under the hood; quite for the opposite of what a macbook is! It certainly works for that, and the remaining ConnMan developers (intel dropped the project 2012; one could argue that they lost interest), but you're really doing a bit of a niche choice in infrastructure there – not a criticism, just so that you're aware that if things feel "hard to use", then that's because you picked the hard route.

You can prevent connman from configuring a network interface at all, by adding it to the comma-separated NetworkInterfaceBlacklist= list in the [General] section of /etc/connman/main.conf.

However, it would seem strange to me to do that – instead, I'd simply configure my connections to only use the wifi device of choice, not the one you don't want. You'd do that by (either using a connman configuration frontend, or) editing /var/lib/connman/wifi_{network id}/settings and setting the DeviceName= accordingly.

Note that ConnMan understands itself, to quote

ConnMan is a daemon for managing Internet connections within embedded device

I.e., for devices that aren't used as "computers", but as some other device class that integrates a Linux computer under the hood; quite for the opposite of what a macbook is! It certainly works for that, and the remaining ConnMan developers¹, but you're really doing a bit of a niche choice in infrastructure there – not a criticism, just so that you're aware that if things feel "hard to use", then that's because you picked the hard route.

¹ intel wrote ConnMan (so much for "anti-big compute" conspiracy theories that are usually used to discredit NetworkManager…), but drastically reduced involvement in the project around 2012; one could argue that they lost interest. These days, the project is still active, and the Jolla project (embedded connection manager for a tablet/phone operating system competing with Android) as well as a lot of deeply embedded companies (windriver, LG's home appliances, room lighting companies, …); the same people working on embedded bluetooth appliances in the linux kernel are also regular contributors. So, it's really an active Linux project, but I'd say that the people driving it have a different set of goals than the people driving end-user Linux distros, for actual humans sitting in front of a Linux laptop.

You can prevent connman from configuring a network interface at all, by adding it to the comma-separated NetworkInterfaceBlacklist= list in the [General] section of /etc/connman/main.conf.

However, it would seem strange to me to do that – instead, I'd simply configure my connections to only use the wifi device of choice, not the one you don't want. You'd do that by (either using a connman configuration frontend, or) editing /var/lib/connman/wifi_{network id}/settings and setting the DeviceName= accordingly.

You can prevent connman from configuring a network interface at all, by adding it to the comma-separated NetworkInterfaceBlacklist= list in the [General] section of /etc/connman/main.conf.

However, it would seem strange to me to do that – instead, I'd simply configure my connections to only use the wifi device of choice, not the one you don't want. You'd do that by (either using a connman configuration frontend, or) editing /var/lib/connman/wifi_{network id}/settings and setting the DeviceName= accordingly.

Note that ConnMan understands itself, to quote

ConnMan is a daemon for managing Internet connections within embedded device

I.e., for devices that aren't used as "computers", but as some other device class that integrates a Linux computer under the hood; quite for the opposite of what a macbook is! It certainly works for that, and the remaining ConnMan developers (intel dropped the project 2012; one could argue that they lost interest), but you're really doing a bit of a niche choice in infrastructure there – not a criticism, just so that you're aware that if things feel "hard to use", then that's because you picked the hard route.