#connman — Public Fediverse posts

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

@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?

What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?

[2/2]

@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?

What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?

[2/2]

@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?

What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?

[2/2]

@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?

What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?

[2/2]

@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?

What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?

[2/2]

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:

connmanctl enable bluetooth

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

#BeagleBoard I'm now playing mix and match between guides to see what works with #connman. My ethernet and wifi will both a.) connect on restart/boot and b.) retain their mac addresses or I will get NetworkManager on here somehow.

Note to #connman: my network is MAC filtered and IP reserved. No, you can't get in unless the MAC is recognized. For God's sake who hurt you?

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.

I throw in the towel. Not going to waste any more time with #connman and #antix. I'm so mad that I'm considering now to install #astra linux - the special edition. But then, I probably should first learn the Russian language...
http://www.astralinux.ru/en/

After all the #command_line training I've had lately I thought that taming #antiX #Linux would be easy, but I probably underestimated the thing...
I''ll try to read the docs for #ConnMan(!?) a little while longer.