AW: MC7455 not working

[Thomas Lang]

Hi,
I put IPv6 on Ignore, but still same behaviour. I think the problem is somewhere else not IPv6. 
First what is strange I need to start PC with enabled ModemManger Service otherwise starting ModemManager manualy the Simcard will fail.
Second when I start the PC with  ModemManager as a service first attempt to connect will fail see log below. What wonders me is that now the nm sees a cdc-wdm1 device.  If I restart ModemManager manualy. I can connect but this time nm sees a cdc-wdm0 device.
Thomas


-----Ursprüngliche Nachricht-----
Von: Bjørn Mork [mailto:bjorn at mork.no] 
Gesendet: Freitag, 17. Juni 2016 19:45
An: Aleksander Morgado <aleksander at aleksander.es>
Cc: Thomas Lang <thomas.lang at tactilo.eu>; modemmanager-devel at lists.freedesktop.org
Betreff: Re: MC7455 not working

Aleksander Morgado <aleksander at aleksander.es> writes:

> On Fri, Jun 17, 2016 at 5:56 PM, Thomas Lang <thomas.lang at tactilo.eu> wrote:
>> ModemManager[835]: <info>  QMI IPv4 Settings:
>> ModemManager[835]: <info>      Address: 100.76.202.73/30
>> ModemManager[835]: <info>      Gateway: 100.76.202.74
>> ModemManager[835]: <info>      DNS #1: 139.7.30.126
>> ModemManager[835]: <info>      DNS #2: 139.7.30.125
>> ModemManager[835]: <info>         MTU: 1500
>> ModemManager[835]: [/dev/cdc-wdm1] Allocating new client ID...
>> ModemManager[835]: [/dev/cdc-wdm1] Registered 'wds' (version 1.67) client with ID '36'
>> ModemManager[835]: <info>  error: couldn't start network: QMI protocol error (14): 'CallFailed'
>> ModemManager[835]: <info>  call end reason (1): 'generic-unspecified'
>> ModemManager[835]: <info>  verbose call end reason (2,210): 
>> [internal] pdn-ipv6-call-disallowed
>> ModemManager[835]: <info>  Modem 
>> /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> 
>> connected)
>
> Are you requesting both IPv4 and IPv6 explictly in the NM config?
> Looks like IPv6 is failing here.

Yes, looks like it is denied by the network.  FWIW, I'm currently in exact the same situation - as embarrassing as that might be.  But I don't see any failures due to this, only the expected pdn-ipv6-call-disallowed 'CallFailed' message.  The IPv4 session still works fine for me.



Bjørn