Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Error "wifi: No carrier" only to connman (Jun Nie)
2. Re: Error "wifi: No carrier" only to connman (Daniel Wagner)
----------------------------------------------------------------------
Message: 1
Date: Tue, 12 Mar 2019 15:50:19 +0800
From: Jun Nie <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: connman <[email protected]>
Subject: Re: Error "wifi: No carrier" only to connman
Message-ID:
<CABymUCN8F8+dXfT3b6yjZZbfV=jl0xgqmcdwuf2h+7-ege5...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Daniel Wagner <[email protected]> ?2019?3?11??? ??4:53???
>
> > Both boards have QCA chip and share the same driver. Kernel version is
> > 4.14.103.
>
> So there is no surprise. They should behave the same.
>
> > There is some NXP patches based on 4.14.103 commit. But I do not think this
> > issue is due to kernel or driver issue because iwlist command works well
> > when connmanctl has issue.
>
> You can't compare iwlist with connmanctrl directly. iwlist works
> directly on the Kernel APIs. You see what the kernel reports to
> userland. ConnMan relies on wpa_supplicant to work correctly.
I compare connman to iwlist to make sure kernel/driver works well. So
that I can concentrate on user space.
>
> > I did not finish porting iwd to my yocto platform yet due to ell
> > version issue.
>
> I see you have Yocto fun as well :)
Per my experience, it takes more time to port a new app/lib to a
customized rootfs due to dependency issue without yocto.
>
> > But I just find that WiFi works OK on boot up if I
> > specify a settings file instead of depends on connman to generate it.
> > Do you have any idea?
>
> If you start with an fresh installation, all technologies are disabled
> by default (except ethernet).
>
> > +[global]
> > +OfflineMode=false
> > +
> > +[WiFi]
> > +Enable=true
> > +Tethering=false
> > +
> > +[Bluetooth]
> > +Enable=true
> > +Tethering=false
> > +
> > +[Wired]
> > +Enable=true
> > +Tethering=false
>
> This enables all technologies, which is the same as calling 'connmanctl
> enable wifi' after ConnMan has started.
You are right. Changing the setting file is not a reliable fix, the
bug may still appear after changing setting file.
For "tcpdump -i nlmon -w trace-file.pcap", the trace file size
increase for "connmanctl enable/disable wifi", but
does not increase for "connmanctl scan wifi" command. Can we confirm
connman does not send out any
message to network layer for scan command?
BTW: do you know how to read trace file? "iwmon -r trace-file.pcap"
does not emit any info.
Best Regards.
Jun
------------------------------
Message: 2
Date: Tue, 12 Mar 2019 12:18:10 +0100
From: Daniel Wagner <[email protected]>
To: Jun Nie <[email protected]>
Cc: connman <[email protected]>
Subject: Re: Error "wifi: No carrier" only to connman
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
> For "tcpdump -i nlmon -w trace-file.pcap", the trace file size
> increase for "connmanctl enable/disable wifi", but
> does not increase for "connmanctl scan wifi" command. Can we confirm
> connman does not send out any
> message to network layer for scan command?
Scanning is a difficult topic with wpa_supplicant. Generally speaking,
wpa_supplicant should do the job. But the behavior depends heavily on
the hardware/driver and wpa_supplicant. Normally, you should see the
D-Bus message from ConnMan to wpa_supplicant if you do a 'connmanctlscan
wifi'
> BTW: do you know how to read trace file? "iwmon -r trace-file.pcap"
> does not emit any info.
What API is wpa_supplicant using for stearing the driver? WEXT or
nlm8011? WEXT is not supported.
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 41, Issue 13
***************************************
