Hi,
On 04/20/2018 12:04 PM, stef204 wrote:
Daniel, please see my comments below--I have included links to the
log files.
19.04.2018, 01:01, "Daniel Wagner" <wagi(a)monom.org>:
>> Cannot create /var/run/connman/resolv.conf falling back to /etc/resolv.conf
>
> That might be a problem. Although then if ConnMan wouldn't not be able
> to setup the DNS resolver it would never work. Still check what happens
> with the resolv.conf. It is a global resource NetworkManager and also
> systemd-resolvd are trying to access. In the past ConnMan also just
> grapped the file. Just recently we teached ConnMan to behave more
> friendly and don't grab the file it all the time.
>
>
> If that all failes try to create a log with timestamps. Maybe we can see
> then what takes so long:
>
> connmand -d 2>&1 | ts '[%H:%M:%.S]' | tee connman.log
>
Here is the result of:
# journalctl -f
<
https://paste.xinu.at/zyt/>
I don't see any thing really strange in the log. The only thing I notice
the wpa_s calls. Are you sure that you didn't upgrade wpa_s along with
ConnMan. If possible try different version of it. It is a constant
source of troubles.
And here is the result of:
%dmesg -w
<
https://paste.xinu.at/AMGz1/>
(I have redacted some addresses out, hope it does not make it more difficult to read.)
That's okay.
I see one error besides the resolv.conf error above:
connmand[5630]: 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.
I don't know why it throws that error off and if it has any
importance/impact.
The hostname on my box is different than the one on the router but locally it seems set
normally, i can see it when checking:
% hostname
or
% hostnamectl status
Incidentally, I see these 2 lines in the log which are of concern:
wlp5s0 {add} route 212.227.81.55 gw 192.168.178.1 scope 0 <UNIVERSE>
Apr 20 11:18:14 somelinux connmand[15615]: wlp5s0 {del} route 212.227.81.55 gw
192.168.178.1 scope 0 <UNIVERSE>
What is 212.227.81.55? Is this related to the small check connman does when starting?
That's the online check. In the README should be some pointers on it.
And you can disable it if want.
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 tests.
Over wifi I presume. Well, check what wpa_s is doing and the drivers. It
sounds like some regression in the drivers.
This, of course, could be due to problems at my ISP. However, what
is weird is that when I do the same ping from another box (not running connman)
CONCURRENTLY, the stats at times, are much better. I mean ping stats at 1500ms on my box
and 25ms on the other box, pinging 4.2.2.2.
There could be something misconfigured on my box OR on my router and if so, it escapes me
at the moment. I do get a fix IP address assigned by my router and that should not and
has never run interference in anyway (I don't see why it would.)
Thanks for any feedback or suggestions you can provide.
Sorry can't really help. It sound really like a driver/wpa_s thingy for
me. Though I can be wrong. The only advice I can give is to try out
different combination the kernel, wpa_s and ConnMan because there is
anything really obvious wrong. BTW, you can also enable some more
logging on wpa_s.
Thanks,
Daniel