Network starting error in Quectel EC25-J .
Mashkur Ahmad
mashkur14 at gmail.com
Fri Feb 8 01:12:08 UTC 2019
Hi Aleksaner,
Thank you very much for your support.
At first i want to share some more info it might help to understand the
issues.
I use raspberry pi : Linux raspberrypi 4.14.79-v7+ #1159 SMP Sun Nov 4
17:50:20 GMT 2018 armv7l GNU/Linux.
sudo qmicli -d /dev/cdc-wdm0 --wds-set-autoconnect-settings=disabled
[08 Feb 2019, 09:52:31] -Warning ** [/dev/cdc-wdm0] requested auto mode but
no MBIM QMUX support available
Autoconnect settings updated
sudo qmicli -d /dev/cdc-wdm0 --wds-start-network=apn='isp.docomoiot.net
',ip-type=4,autoconnect=yes
[08 Feb 2019, 09:52:49] -Warning ** [/dev/cdc-wdm0] requested auto mode but
no MBIM QMUX support available
[/dev/cdc-wdm0] Network started
Packet data handle: '2266172864'
I called above command and now i am able to start the network successfully
but i am not getting the ip in wwan0 interface.
i have also applied 'sudo dhclient -d -4 wwan0' command but not getting
ip,
By checking the status i am able to see the network ip
sudo qmicli -d /dev/cdc-wdm0 --wds-get-current-settings
[08 Feb 2019, 10:06:14] -Warning ** [/dev/cdc-wdm0] requested auto mode but
no MBIM QMUX support available
[/dev/cdc-wdm0] Current settings retrieved:
IP Family: IPv4
IPv4 address: 100.68.228.168
IPv4 subnet mask: 255.255.255.240
IPv4 gateway address: 100.68.228.169
IPv4 primary DNS: 220.159.212.200
IPv4 secondary DNS: 220.159.212.201
MTU: 1430
Domains: none
On Thu, Feb 7, 2019 at 11:51 PM Aleksander Morgado <aleksander at aleksander.es>
wrote:
> Hey,
>
> > qmi-network start is not working , i have check all qmicli ,everything
> seems good but even it is not working . if anyone can help me to get
> started qmi dial up,
> > I have tested other commands i am able to get status, network, scan etc
> > I use Raspberry pi. i have intalled ltest libqmi
> >
> > sudo qmi-network /dev/cdc-wdm0 start
> > Loading profile at /etc/qmi-network.conf...
> > APN: isp.docomoiot.net
> > APN user: unset
> > APN password: unset
> > qmi-proxy: yes
> > Checking data format with 'qmicli -d /dev/cdc-wdm0 --wda-get-data-format
> --device-open-proxy'...
> > [07 Feb 2019, 09:34:25] -Warning ** [/dev/cdc-wdm0] requested auto mode
> but no MBIM QMUX support available
> > Device link layer protocol retrieved: raw-ip
> > Getting expected data format with 'qmicli -d /dev/cdc-wdm0
> --get-expected-data-format'...
> > [07 Feb 2019, 09:34:25] -Warning ** [/dev/cdc-wdm0] requested auto mode
> but no MBIM QMUX support available
> > Expected link layer protocol retrieved: 802-3
> > Updating kernel link layer protocol with 'qmicli -d /dev/cdc-wdm0
> --set-expected-data-format=raw-ip'...
> > [07 Feb 2019, 09:34:25] -Warning ** [/dev/cdc-wdm0] requested auto mode
> but no MBIM QMUX support available
> > error: cannot set expected data format: Expected data format not updated
> properly to 'raw-ip': got '802-3' instead
> > Error updating kernel link layer protocol
>
> This is one issue here. The EC25 is configured to use raw-ip, and so
> we *try* to set the expected data format in the kernel to raw-ip, but
> we're failing to do so. This will only work in Linux >=4.5, where the
> raw-ip support was introduced in the kernel.
>
> > Starting network with 'qmicli -d /dev/cdc-wdm0 --wds-start-network=apn='
> isp.docomoiot.net' --client-no-release-cid --device-open-proxy'...
> > [07 Feb 2019, 09:34:25] -Warning ** [/dev/cdc-wdm0] requested auto mode
> but no MBIM QMUX support available
> > error: couldn't start network: QMI protocol error (26): 'NoEffect'
>
> Another issue here, although probably not a big deal. Looks like the
> module is set to autoconnect, so an attempt to reconnect manually with
> WDS Start Network will yield the "NoEffect" error. You can probably
> avoid this by reconfiguring the module not to autoconnect, e.g.
> "qmicli --wds-set-autoconnect-settings=disabled"
>
> --
> Aleksander
> https://aleksander.es
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20190208/29a4be5b/attachment.html>
More information about the libqmi-devel
mailing list