<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">So, no success on my end as well. Here's the report.<br><br>First of all, up until today, I had NetworkManager enabled. I've described the problems here (and I was using Arch's stock libmbim, libqmi and modemmanager at that point): <a href="https://bbs.archlinux.org/viewtopic.php?pid=1636411">https://bbs.archlinux.org/viewtopic.php?pid=1636411</a><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br>Today, I disabled the NetworkManager. I also compiled the latest state in "qmi-over-mbim" branches for all three libs locally (as already described here: <a href="http://pastie.org/private/jdrdgnmzlfvsn2fv8mva">http://pastie.org/private/jdrdgnmzlfvsn2fv8mva</a>). I thought since the AUR packages that Joshua is mentioning were last updated on April 16th that could make a difference (I've contacted the current AUR maintainer but didn't heard back). But despite the disabled NetworkManager, I couldn't start the ModemManager: <a href="http://pastie.org/private/cqaheh4qdftw9p1hlxjw">http://pastie.org/private/cqaheh4qdftw9p1hlxjw</a>. How do I "register" the service if I compile it locally?<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Then, I uninstalled (via `sudo make uninstall`) all three locally compiled libs, installed the AUR packages and Arch's stock modemmanager. Now I'm getting a "couldn't connect the bearer: 'GDBus.Error:org.freedesktop.libmbim.Error.Status.NotInitialized: NotInitialized'" error when I try to connect the bearer and the modem: <a href="http://pastie.org/private/7lbsbeiyde9th5yp2rnova">http://pastie.org/private/7lbsbeiyde9th5yp2rnova</a>.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Regards,<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Samo<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 24, 2016 at 11:21 PM, George Tepnadze <span dir="ltr"><<a href="mailto:george.tepnadze@gmail.com" target="_blank">george.tepnadze@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>Signal quality was 64 or 49 but still no ping or traffic.<br></div>Checked other traffic types (telnet, ssh, www and etc) but no RX traffic so it doesn't work for sure.<br></div>Also tried to connect with qmi-network with no success, no traffic.<br><br># /usr/bin/qmi-network /dev/cdc-wdm1 start<br>Loading profile at /etc/qmi-network.conf...<br> APN: <a href="http://3g.ge" target="_blank">3g.ge</a><br> APN user: unset<br> APN password: unset<br> qmi-proxy: yes<br> qmi-over-mbim: yes<br> fcc auth: yes<br> static ip: yes<br>error: couldn't set FCC authentication: QMI protocol error (26): 'NoEffect'<br>Starting network with 'qmicli -d /dev/cdc-wdm1 --wds-start-network=apn='<a href="http://3g.ge" target="_blank">3g.ge</a>' --client-no-release-cid --device-open-proxy --device-open-mbim'...<br>IP_FAMILY=IPV4<br>IPV4_ADDRESS=10.112.83.119<br>IPV4_CIDR=<a href="http://10.112.83.119/28" target="_blank">10.112.83.119/28</a><br>IPV4_SUBNET_MASK=255.255.255.240<br>IPV4_GATEWAY_ADDRESS=10.112.83.120<br>IPV4_PRIMARY_DNS=81.95.167.65<br>IPV4_SECONDARY_DNS=81.95.167.66<br>MTU=1500<br>IFACE=wwp0s20f0u2i12<br>Saving state at /tmp/qmi-network-state-cdc-wdm1... (IFACE: wwp0s20f0u2i12)<br>Saving state at /tmp/qmi-network-state-cdc-wdm1... (CID: 51)<br>Saving state at /tmp/qmi-network-state-cdc-wdm1... (PDH: 63249600)<br>Network started successfully<br><br># /usr/bin/qmi-network /dev/cdc-wdm1 status<br>Loading profile at /etc/qmi-network.conf...<br> APN: <a href="http://3g.ge" target="_blank">3g.ge</a><br> APN user: unset<br> APN password: unset<br> qmi-proxy: yes<br> qmi-over-mbim: yes<br> fcc auth: yes<br> static ip: yes<br>Loading previous state from /tmp/qmi-network-state-cdc-wdm1...<br> Previous CID: 51<br> Previous PDH: 63249600<br>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'...<br>Status: connected<div><div class="h5"><br><div> <br><div><div class="gmail_extra"><div class="gmail_quote">On Fri, Jun 24, 2016 at 11:55 PM, Michael Shell <span dir="ltr"><<a href="mailto:list1@michaelshell.org" target="_blank">list1@michaelshell.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>On Fri, 24 Jun 2016 12:57:35 +0200<br>
Bjørn Mork <<a href="mailto:bjorn@mork.no" target="_blank">bjorn@mork.no</a>> wrote:<br>
<br>
> This means that some operators filter the Google DNS servers.<br>
<br>
<br>
</span>In addition to using a VPN, one option to overcome such increasingly<br>
commonb and vile ISP behavior is DNSCrypt:<br>
<br>
<a href="https://dnscrypt.org/" rel="noreferrer" target="_blank">https://dnscrypt.org/</a><br>
<br>
The list of known encrypted DNS servers is stored in<br>
/usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv<br>
<br>
The DNS crypt daemon is started like:<br>
<br>
/usr/sbin/dnscrypt-proxy --daemonize -u dnscrypt --resolvers-list=/usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv --resolver-name=open<br>
dns<br>
<br>
To bypass ISP UDP traffic filters, you can add the --tcp-only option.<br>
There also is --resolver-address=<ip>[:port]<br>
<br>
See<br>
<br>
man dnscrypt-proxy<br>
<br>
for details.<br>
<br>
Just set your /etc/resolv.conf to contain:<br>
<br>
# the local DNSCrypt proxy<br>
nameserver 127.0.0.1<br>
<br>
and the system will use the DNSCrypt proxy connection for<br>
DNS lookups.<br>
<br>
BTW, many mobile ISPs, at least T-Mobile, are now using a web<br>
proxy to snoop on all open http (non-https) traffic.<br>
<br>
The days of any unencrypted web traffic are coming to an<br>
end and with good reason it seems.<br>
<br>
<br>
Cheers,<br>
<br>
Mike Shell<br>
<div><div>_______________________________________________<br>
ModemManager-devel mailing list<br>
<a href="mailto:ModemManager-devel@lists.freedesktop.org" target="_blank">ModemManager-devel@lists.freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel</a><br>
</div></div></blockquote></div><br></div></div></div></div></div></div>
<br>_______________________________________________<br>
ModemManager-devel mailing list<br>
<a href="mailto:ModemManager-devel@lists.freedesktop.org">ModemManager-devel@lists.freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel</a><br>
<br></blockquote></div><br></div></div>