<div dir="ltr"><div><div>Signal quality was 64 or 49 but still no ping or traffic. </div>Checked other traffic types (telnet, ssh, www and etc) but no RX traffic so it doesn't work for sure. </div>Also tried to connect with qmi-network with no success, no traffic. # /usr/bin/qmi-network /dev/cdc-wdm1 start Loading profile at /etc/qmi-network.conf... APN: <a href="http://3g.ge">3g.ge</a> APN user: unset APN password: unset qmi-proxy: yes qmi-over-mbim: yes fcc auth: yes static ip: yes error: couldn't set FCC authentication: QMI protocol error (26): 'NoEffect' Starting network with 'qmicli -d /dev/cdc-wdm1 --wds-start-network=apn='<a href="http://3g.ge">3g.ge</a>' --client-no-release-cid --device-open-proxy --device-open-mbim'... IP_FAMILY=IPV4 IPV4_ADDRESS=10.112.83.119 IPV4_CIDR=<a href="http://10.112.83.119/28">10.112.83.119/28</a> IPV4_SUBNET_MASK=255.255.255.240 IPV4_GATEWAY_ADDRESS=10.112.83.120 IPV4_PRIMARY_DNS=81.95.167.65 IPV4_SECONDARY_DNS=81.95.167.66 MTU=1500 IFACE=wwp0s20f0u2i12 Saving state at /tmp/qmi-network-state-cdc-wdm1... (IFACE: wwp0s20f0u2i12) Saving state at /tmp/qmi-network-state-cdc-wdm1... (CID: 51) Saving state at /tmp/qmi-network-state-cdc-wdm1... (PDH: 63249600) Network started successfully # /usr/bin/qmi-network /dev/cdc-wdm1 status Loading profile at /etc/qmi-network.conf... APN: <a href="http://3g.ge">3g.ge</a> APN user: unset APN password: unset qmi-proxy: yes qmi-over-mbim: yes fcc auth: yes static ip: yes Loading previous state from /tmp/qmi-network-state-cdc-wdm1... Previous CID: 51 Previous PDH: 63249600 Getting status with 'qmicli -d /dev/cdc-wdm1 --wds-get-packet-service-status --client-cid=51 --client-no-release-cid --device-open-proxy --device-open-mbim'... Status: connected <div> <div><div class="gmail_extra"><div class="gmail_quote">On Fri, Jun 24, 2016 at 11:55 PM, Michael Shell <<a href="mailto:list1@michaelshell.org" target="_blank">list1@michaelshell.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 24 Jun 2016 12:57:35 +0200 Bjørn Mork <<a href="mailto:bjorn@mork.no">bjorn@mork.no</a>> wrote: > This means that some operators filter the Google DNS servers. In addition to using a VPN, one option to overcome such increasingly commonb and vile ISP behavior is DNSCrypt: <a href="https://dnscrypt.org/" rel="noreferrer" target="_blank">https://dnscrypt.org/</a> The list of known encrypted DNS servers is stored in /usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv The DNS crypt daemon is started like: /usr/sbin/dnscrypt-proxy --daemonize -u dnscrypt --resolvers-list=/usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv --resolver-name=open dns To bypass ISP UDP traffic filters, you can add the --tcp-only option. There also is --resolver-address=<ip>[:port] See man dnscrypt-proxy for details. Just set your /etc/resolv.conf to contain: # the local DNSCrypt proxy nameserver 127.0.0.1 and the system will use the DNSCrypt proxy connection for DNS lookups. BTW, many mobile ISPs, at least T-Mobile, are now using a web proxy to snoop on all open http (non-https) traffic. The days of any unencrypted web traffic are coming to an end and with good reason it seems. Cheers, Mike Shell <div class=""><div class="h5">_______________________________________________ ModemManager-devel mailing list <a href="mailto:ModemManager-devel@lists.freedesktop.org">ModemManager-devel@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel</a> </div></div></blockquote></div> </div></div></div></div>