On Sun, Dec 21, 2014 at 10:39 PM, Tore Anderson t...@fud.no wrote:
Hi Aleksander,
Are you suggesting that by default NM should try with IPv4 or IPv6 PDP
context types if both are enabled and IPV4V6 fails?
Yes, I think that would be the best solution.
In QMI modems it is ModemManager the
* Aleksander Morgado
MBIM allows to request IPv4v6 or separate IPv4 and IPv6; currently we
try one or the other, because the ModemManager API allows asking for
both cases. The fact that in QMI we default to separate IPv4 and IPv6
is because we can do so using different WDS clients on the same
Aleksander Morgado aleksan...@aleksander.es writes:
On Sun, Dec 21, 2014 at 10:39 PM, Tore Anderson t...@fud.no wrote:
Hi Aleksander,
Are you suggesting that by default NM should try with IPv4 or IPv6 PDP
context types if both are enabled and IPV4V6 fails?
Yes, I think that would be the
On 12/22/2014 10:49 AM, Tore Anderson wrote:
Anyway, I have no strong opinions on where the fallback should be
located and how it should work in detail, but I do think *something* is
needed if you want to avoid lots of bug reports complaining that their
WWAN connection profiles no longer work
* Balázs Pozsár
Speaking of theoretical cases, couldn't it be a problem if for example
the modem and the network both support IPV4V6, and the user expects it,
but somehow that connection fails on the first try (could happen due to
any temporary reason), and then NM/MM would fall back to
Are you suggesting that by default NM should try with IPv4 or IPv6 PDP
context types if both are enabled and IPV4V6 fails?
Yes, I think that would be the best solution.
In QMI modems it is ModemManager the one connecting separately IPv4
and IPv6 WDS sessions when IPv4v6 is requested.
Yep,
On Mon, 2014-12-22 at 21:46 +0100, Aleksander Morgado wrote:
Are you suggesting that by default NM should try with IPv4 or IPv6 PDP
context types if both are enabled and IPV4V6 fails?
Yes, I think that would be the best solution.
In QMI modems it is ModemManager the one connecting
