>> I see one error besides the resolv.conf error above:
>> connmand: Failed to set domainname to xxxx.box (this would be the domain
name of my router)
> You can disable this in the main config. ConnMan wants to set the
> hostname given by DHCP.
It's fixed as I mentioned in another reply:
For the record, I have fixed the above "secondary issue" by adding
CAP_SYS_ADMIN to the connman.service unit CapabilityBoundingSet line
I no longer get the " connmand: Failed to set domainname to xxxx.box "
it now works as expected. I will leave it alone (default is enabled I believe).
Good to hear it works now.
> That's the online check. In the README should be some
pointers on it.
> And you can disable it if want.
Yes, I figured as much. Before considering disabling it, what is the
value of this online check for me as a user?
This feature is used for portal detection.
What does it add that would
be removed if disabled?
No WISPr support .
I have read the docs but don't really see what
is vital or significant there; I do travel so have to connect from
different places and using different networks.
ConnMan can log in automatically into portals for you, if (and that is a
big if) the portal is sporting proper WISPr protocols.
>> Please let me know if you see anything odd or weird in the
logs. I don't.
>> The quality of my connection is also degrading as of late and when I check with
another box not running connman, it seems that my own box connects much slower--from ping
> Over wifi I presume. Well, check what wpa_s is doing and the drivers. It
> sounds like some regression in the drivers.
I think it may be due to a regression or bug in the kernel actually,
from some additional searched I've done. Will continue debugging and
post what I find out (if anything) here.
Yes please. It is useful to get such reports back.