qmicli always getting transaction time out

Tue Oct 2 02:28:41 UTC 2018

Hi again,

Finally I got to work on Ubuntu server 16.04.
-Install Ubuntu 16.04
-sudo apt update && upgrade
-Update kernel version
-sudo add-apt-repository ppa:aleksander-m/modemmanager-xenial
- sudo apt install modemmanager
- sudo apt install network-manager
- sudo nmcli connection add type gsm con-name XXX autoconnect yes ifname
cdc-wdm0 apn XXXXX password XXXX user XXXX
- sudo nmcli connection up XXX

Now, I am trying to have it to work, using Ubuntu 18.04
-Install ubuntu server 18.04
- sudo apt update && upgrade
- sudo apt install modemmanager
- sudo apt install network manager
sudo nmcli connection add type gsm con-name XXX autoconnect yes ifname
cdc-wdm0 apn XXXXX password XXXX user XXXX
- sudo nmcli connection up XXX

Connection works perfectly when there is good LTE coverage, but, when only
umts access tech avaliable it doesnt work.

I have 3 devices. I have tried whith all 3 using Ubuntu 18.04 any no one
work.
Now I went back to Ubuntu 16 on one of them and it connects inmediatly (all
3 are in the same place, at the same time)

Do you have any idea?

Thanks in advance

El lun., 7 de may. de 2018 a la(s) 17:40, EMANUEL FERNANDO MONTOYA GOMEZ (
emanuel.montoya at udea.edu.co) escribió:

> Thanks
>
> 2018-04-26 1:41 GMT-05:00 Aleksander Morgado <aleksander at aleksander.es>:
>
>>
>>
>>>
>>>
>>> But I cant ping anywhere
>>>
>>> ico1 at ico1:~$ sudo traceroute www.google.com -i wwp0s21f0u4i12
>>> traceroute to www.google.com (172.217.10.164), 30 hops max, 60 byte
>>> packets
>>>  1  * * *
>>>  2  * * *
>>>  3  * * *
>>>  4  * * *
>>>  5  * * *
>>>  6  * * *
>>>  7  * * *
>>>  8  * * *
>>>  9  * * *
>>> 10  * * *
>>> 11  * * *
>>> 12  * * *
>>> 13  * * *
>>> 14  * * *
>>> 15  * * *
>>> 16  * * *
>>> 17  * * *
>>> 18  * * *
>>> 19  * * *
>>> 20  * * *
>>> 21  * * *
>>> 22  * * *
>>> 23  * * *
>>> 24  * * *
>>> 25  * * *
>>> 26  * * *
>>> 27  * * *
>>> 28  * * *
>>> 29  * * *
>>> 30  * * *
>>> ico1 at ico1:~$
>>>
>>> *I can see packets with tcpdump*
>>> ico1 at ico1:~$ sudo tcpdump -i wwp0s21f0u4i12
>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
>>> decode
>>> listening on wwp0s21f0u4i12, link-type EN10MB (Ethernet), capture size
>>> 262144 bytes
>>> 15:37:59.643116 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 47, length 64
>>> 15:37:59.806921 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 47, length 64
>>> 15:38:00.667111 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 48, length 64
>>> 15:38:00.837307 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 48, length 64
>>> 15:38:01.691147 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 49, length 64
>>> 15:38:01.856968 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 49, length 64
>>> 15:38:02.715135 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 50, length 64
>>> 15:38:02.887350 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 50, length 64
>>> 15:38:03.739411 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 51, length 64
>>> 15:38:03.907008 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 51, length 64
>>> 15:38:04.763243 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 52, length 64
>>> 15:38:04.926635 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 52, length 64
>>> 15:38:05.787104 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 53, length 64
>>> 15:38:05.958986 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 53, length 64
>>> 15:38:06.811143 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 54, length 64
>>> 15:38:06.976704 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 54, length 64
>>> 15:38:07.835141 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 55, length 64
>>> 15:38:07.997298 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 55, length 64
>>> 15:38:08.859145 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 56, length 64
>>> 15:38:09.026706 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 56, length 64
>>> 15:38:09.883127 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 57, length 64
>>> 15:38:10.047343 IP atl14s75-in-f4.1e100.net > 10.204.106.216: ICMP echo
>>> reply, id 4325, seq 57, length 64
>>> 15:38:10.907142 IP 10.204.106.216 > atl14s75-in-f4.1e100.net: ICMP echo
>>> request, id 4325, seq 58, length 64
>>> ^C
>>> 23 packets captured
>>> 24 packets received by filter
>>> 0 packets dropped by kernel
>>>
>>> *But ping seems not to complete*
>>> ico1 at ico1:~$ ping www.google.com -I wwp0s21f0u4i12
>>> PING www.google.com (172.217.10.164) from 10.204.106.216
>>> wwp0s21f0u4i12: 56(84) bytes of data.
>>> ^C
>>> --- www.google.com ping statistics ---
>>> 78 packets transmitted, 0 received, 100% packet loss, time 78842ms
>>> ico1 at ico1:~$
>>>
>>> When I try on Windows, it works perfectly (can ping www.google,com)
>>>
>>> Any suggestions on this?
>>>
>>>
>> If the wwan connection isn't your default route (doesn't look like it is
>> because you're running ping with -I) then you may need to disable rp_filter
>> in the network interface so that the kernel doesn't filter out the ICMP
>> replies.
>>
>>
>> --
>> Aleksander
>> https://aleksander.es
>>
>
>
>
> --
> *Emanuel Fernando Montoya Gómez*
> Msc Ingeniería de Telecomunicaciones
> emanuel.montoya at udea.edu.co
>
>

-- 
*Emanuel Fernando Montoya Gómez*
Msc Ingeniería de Telecomunicaciones
emanuel.montoya at udea.edu.co

-- 

"La información aquí contenida es para uso exclusivo de la persona o 
entidad de destino. Está estrictamente prohibida su utilización, copia, 
descarga, distribución, modificación y/o reproducción total o parcial, sin 
el permiso expreso de Universidad de Antioquia, pues su contenido puede ser 
de carácter confidencial y/o contener material privilegiado. Si usted 
recibió esta información por error, por favor contacte en forma inmediata a 
quien la envió y borre este material de su computador. Universidad de 
Antioquia no es responsable por la información contenida en esta 
comunicación, el directo responsable es quien la firma o el autor de la 
misma."

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20181001/c285bb10/attachment-0001.html>