Re: M7354 IPv6 Problem
On Thu, 24 Sep 2015 15:19:39 -0500 Dan Williams wrote: > To follow up on this, I used a Huawei E397 to bring up dual-stack IPV4V6 > context successfully with ModemManager and NetworkManager. First, make > sure the APN you're using is known-good (otherwise you'll get CallFailed > errors) and that the profile in the modem that matches the APN is a V4V6 > context. What about the potential for a limitation here (for the original poster) with regard to the network operators themselves? For example, T-Mobile is supposed to be IPv6 ready throughout their entire network. However, does such IPv6 readiness also generally apply to the APNs of their MVNOs (subproviders, e.g., Net10, Ting, Simple Mobile)? If not, then even if the modem and the "parent" network owner supports IPv6, using an APN for a MVNO might restrict the connection to IPv4 only. Cheers, Mike Shell ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: ModemManager using QMI doesnt always work in the first attemp.
On Thu, 12 Nov 2015 13:15:16 +0100 José wrote: > ModemManager & > (wait for the modem to be detected) > mmcli -m 0 --simple-connect="apn=.." > > This somtimes works, but most of the time fails. My crystal ball says to wait 1-2 minutes for the modem's firmware to finish its boot sequence before trying to issue any commands to it. As a famous comedy line of a guy who dropped a pass goes, "I wasn't ready ..." IMHO, properly done firmware should report, "I'm not ready." Cheers, Mike Shell ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: Yet another EM7455 question
On Fri, 24 Jun 2016 12:57:35 +0200 Bjørn Mork 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: https://dnscrypt.org/ 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=[: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 ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
