Sierra modem stopped working

[Bjørn Mork]

Bernd Eggink <monoped at sudrala.de> writes:
> On 14.06.2015 00:22, Aleksander Morgado wrote:
>
>> May be a network issue? Although you said it works under other OS, so not sure.
>
> Certainly not a network issue. As I said, it works under Windows. I
> also tried 3 other Linux live systems (all of which use ModemManager),
> and it failed under each of them in the same way.
> This is rather unsatisfying. Could it be a kernel issue? Do you know
> of any other modem software I could try?

Are you sure you are using the same settings on Windows and Linux?  I
noticed from your log that the modem has a provisioned context which is
different from the one you try to connect to:

ModemManager[2687]: <debug> [1434208007.511793] [mm-bearer-mbim.c:529] provisioned_contexts_query_ready(): Provisioned contexts found (1):
ModemManager[2687]: <debug> [1434208007.511856] [mm-bearer-mbim.c:535] provisioned_contexts_query_ready(): [1] context type: internet
ModemManager[2687]: <debug> [1434208007.511887] [mm-bearer-mbim.c:536] provisioned_contexts_query_ready():              uuid: 7e5e2a7e-4e6f-7272-736b-656e7e5e2a7e
ModemManager[2687]: <debug> [1434208007.511914] [mm-bearer-mbim.c:537] provisioned_contexts_query_ready():     access string: internet.telekom
ModemManager[2687]: <debug> [1434208007.511940] [mm-bearer-mbim.c:538] provisioned_contexts_query_ready():          username: tmobile
ModemManager[2687]: <debug> [1434208007.511965] [mm-bearer-mbim.c:539] provisioned_contexts_query_ready():          password: 
ModemManager[2687]: <debug> [1434208007.511996] [mm-bearer-mbim.c:540] provisioned_contexts_query_ready():       compression: none
ModemManager[2687]: <debug> [1434208007.512030] [mm-bearer-mbim.c:541] provisioned_contexts_query_ready():              auth: pap
ModemManager[2687]: <debug> [1434208007.512078] [mm-bearer-mbim.c:741] connect_context_step(): No specific IP family requested, defaulting to ipv4
ModemManager[2687]: <debug> [1434208007.512104] [mm-bearer-mbim.c:772] connect_context_step(): Launching connection with APN 'internet.t-mobile'...


I'm not saying this necessarily is wrong.  I don't know which APN is
correct for you.  But it might explain your problems.  Please verify
that 'ipv4' (selected by default) is correct as well.  Some operators
have started provisioning ipv6 only contexts.

The rest of the log shows that both communication between host and modem,
and between modem and network really works perfect.  Based on that, I
don't think this can be a software issue.  But I've been wrong before...


Bjørn