qmicli always getting transaction time out

Aleksander Morgado aleksander at aleksander.es
Thu Apr 26 06:41:48 UTC 2018


>
>
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20180426/13d6753c/attachment-0001.html>


More information about the libqmi-devel mailing list