Hey,
Yes, it's like that, I'm calling --simple-disconnect and -d for the
modem before enabling the modem again and trying to register via
--3gpp-register-in-operator=xxx, then I check if I'm connected to the
correct operator by comparing the operator in mmcli -m 0 to the operator
I tried to connect to(can I verify like that that I'm connected to the
correct operator?)
If that is successfull, I use --simple-connect(do I even have to do that?)
So you see, I'm not doing a 3gpp scan explicitly, I'm just (simple)
disconnecting, disabling the modem, enabling again, trying to (3gpp)
register in operator, if successful I try to (simple) connect which is
always successful if register in operator was successful before
Do you have any advice for me what I could do right now?
Btw thank you for sending the patch to the lkml!
Am 23.10.2017 um 17:19 schrieb Aleksander Morgado:
Hey,
Thanks for the answer!
So short answers first:
Yes I do explicitly disconnect before registering in to the next one and
that does always succeed in my case.
Ok, so that makes some sense. You're therefore saying that if you're
connected and you issue a 3GPP Scan(), the modem is not being
disconnected properly and reconnected to the new operator?
I just didn't want to throw a complete log at you, but if it could help you,
I'll just attach the log from those warnings to this mail now.
I see that NDISDUP is being used, so you're not doing PPP, you're
really using the network interface, which is good.
And finally the output of lsusb -v -d vid:pid:
I sent a patch to the LKML to flag this device as WWAN explicitly.
_______________________________________________
ModemManager-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
