Cross open source collaboration: ConnMan connecting LibreElec and SailfishOS maintainers to get wider testing for the WireGuard changes. More info on https://forum.libreelec.tv/thread/29601-wireguard-experimental-support-for-connecting-via-fqdn-not-ip/

#LibreELEC #SailfishOS #ConnMan #WireGuard

Getting annoyed by my ArchLinux setup.
#ConnMan itself works fine. But as soon as I start the tailscaled service, it shits itself in the pants and can't resolve DNS queries (apparently, connman provides its own relaying DNS server) anymore. Probably because it tries to use tailscale0, which is not yet set up. And I can't set it up because logging in needs a DNS query.

I already added the tailscale interfaces to the blacklist, yet connman seems keen on using it anyway.

NetworkInterfaceBlacklist = vmnet,vboxnet,virbr,ifb,ve-,vb-,tailscale

Jan 30 12:27:59 archbook connmand[1827]: Failed to send DNS response to 32: Bad file descriptor
Jan 30 12:27:59 archbook connmand[1827]: Failed to send DNS response to 32: Bad file descriptor

The solution seems to be to hardcode quad9 or similar into /etc/resolv.conf.

If you're using #bluetooth on newer #raspberrypi or other #Linux systems that use #connman, note that connman takes over #rfkill management from systemd-rfkill. To enable bluetooth on your system, instead of rfkill unblock bluetooth you'll want to run:

I found a lot of people claiming "uninstall connman is the solution", but the real answer is that connman provides a replacement UI interface for this feature.

Hope this #tip helps! #tips #linuxtips

Okay, can anyone tell me how to automatically enable and auto connect to wifi using #connman? From what I can find in google, everyone is really into doing it manually every time and likes randomized macs.

I do not think I belong here. Sure, I sometimes want to set #NetworkManager on fire, but it does understand I really do want to use wifi.