3G Modem MC8805:qmicli succesfuly connected but no IP after dhclient

belette · 2015-10-07 20:02:03

Hi,

I have an Arch installation with a mini PCIE Sierra Wireless MC8805.
Everything is discovered and I can see a wwp0s20u7c2i12 interface.

When I tried qmi-network (with an APN conf created before) to connect everything is ok :

qmi-network /dev/cdc-wdm0 start
Loading profile...
    APN: mmsbouygtel.com
Starting network with 'qmicli -d /dev/cdc-wdm0 --wds-start-network=mmsbouygtel.com  --client-no-release-cid'...
Saving state... (CID: 11)
Saving state... (PDH: 1205535944)
Network started successfully

but when I try

dhclient wwp0s20u7c2i12

no result.
It is like the network is almost up but still miss the data path or something like this.
I also noticed that after a minute or so the link being disconnected

Any ideas are very welcomed (I am frustrated as I am almost done but still something missed..)
many thanks

belette

ewaller · 2015-10-07 20:02:59

Anything interesting in the journal as a result of the dhclient command?

belette · 2015-10-07 21:07:23

Thanks for your reply.
No error message.
running dhclient under verbose :

dhclient wwp0s20u7c2i12 -v                                                                                                           :(
Internet Systems Consortium DHCP Client 4.3.2
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wwp0s20u7c2i12/fa:25:ba:2b:2d:73
Sending on   LPF/wwp0s20u7c2i12/fa:25:ba:2b:2d:73
Sending on   Socket/fallback
DHCPDISCOVER on wwp0s20u7c2i12 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wwp0s20u7c2i12 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wwp0s20u7c2i12 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wwp0s20u7c2i12 to 255.255.255.255 port 67 interval 7

double checked with tcpdump where I can see the packet sent

 tcpdump -i wwp0s20u7c2i12              
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wwp0s20u7c2i12, link-type EN10MB (Ethernet), capture size 262144 bytes
19:43:59.163438 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:25:ba:2b:2d:73 (oui Unknown), length 300
19:44:11.930295 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:25:ba:2b:2d:73 (oui Unknown), length 300
21:08:22.467700 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:25:ba:2b:2d:73 (oui Unknown), length 300
21:08:28.091995 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:25:ba:2b:2d:73 (oui Unknown), length 300

but I don't see anything on the packet stats

qmicli -d /dev/cdc-wdm0 --wds-get-packet-statistics                                                                           
[/dev/cdc-wdm0] Connection statistics:
	TX packets OK: 0
	RX packets OK: 0
	TX packets dropped: 0
	RX packets dropped: 0
	TX bytes OK: 0
	RX bytes OK: 0

I still don't know if it is enough to do it or I should start a ppp.

EDIT

It is like all commands works well, I am able to discover networks, see the signal strength, connect successfully but impossible to send / receive any data...
I tried the same card + the same SIM on a Windows laptop and it is working.
I still don't know if I should use the wwp0s20u7c2i12 interface (the one in ip link) or should I start a ppp connection on top of it?
All qmicli commands works properly and nothing special to declare when I ask for system information...

Trying old method with wvdial or netctl but no reply from /dev/ttyS3 for any command.. it is like I am unable to reach it from this way

I am very open to any idea!

Last edited by belette (2015-10-08 20:15:22)

belette · 2015-10-12 19:25:39

a little up to know if anyone has any idea?
I am lock into this

aleksander0m · 2015-10-19 06:42:04

Hey belette,

You may need to switch your modem to use 802.3 link layer protocol, instead of raw ip. You should do this before calling qmi-network, like this:

$ sudo qmicli -d /dev/cdc-wdm0 --wda-set-data-format=802-3

If that fails because WDA isn't supported, try:

$ sudo qmicli -d /dev/cdc-wdm0 --device-open-net="net-802-3|net-no-qos-header" --dms-noop

Then run qmi-network and the dhclient on the WWAN net interface.

Last edited by aleksander0m (2015-10-19 06:44:34)

belette · 2015-10-19 10:12:27

Hola Aleksander y gracias por tu ayudo!

I forgot to mention that I already tried to switch my modem into 802.3 mode but no success either
I also tried to do a

ip link set dev wwp0s20u7c2i12 arp on

as I saw my interface with NOARP flag but no change ...

I can see the request from dhclient but nether get any reply back and my stats (from qmicli -d /dev/cdc-wdm0 --wds-get-packet-statistics are always at 0)
I also checked the signal strengh and the dbm values are in range and as I mentioned the qmi-network script ends with a "Network started successfully"
I noticed that after a minute or so the status switch to disconnected automaticaly (perhaps because no traffic has been detected or no IP has been provided)

Please don't hesitate if you have any other idea to help me identify the root cause..

belette

Arch Linux

#1 2015-10-07 20:02:03

3G Modem MC8805:qmicli succesfuly connected but no IP after dhclient

#2 2015-10-07 20:02:59

Re: 3G Modem MC8805:qmicli succesfuly connected but no IP after dhclient

#3 2015-10-07 21:07:23

Re: 3G Modem MC8805:qmicli succesfuly connected but no IP after dhclient

#4 2015-10-12 19:25:39

Re: 3G Modem MC8805:qmicli succesfuly connected but no IP after dhclient

#5 2015-10-19 06:42:04

Re: 3G Modem MC8805:qmicli succesfuly connected but no IP after dhclient

#6 2015-10-19 10:12:27

Re: 3G Modem MC8805:qmicli succesfuly connected but no IP after dhclient

Board footer