The problem is that the card registers to network in a weird way and thus the mbim.sh script stops and doesn't continue attaching to network, ...
The problem has been detected on a Huawei EchoLife HG556a (version C) but seems a general problem.
Also, the problem was with a ID 12d1:1f16 Huawei Technologies Co., Ltd. K5150 LTE modem but I believe that it can happens on other mbim devices as well.
I believe the problem is more related to the fact that the SIM is from a virtual movile operator which is then using the network from the real operator: Orange, but we didn't test any other SIMs, so we don't know if this is more general, if needed we could try to get some other SIMs for testing.
The problem is that when we do the network registration with umbim it gives an error, so it stops there, so we tried to remove that check like this:
Network connection works ok like this and we can access Inet without any problem.
So... either umbim is not exiting with the right exit code, maybe because of that unknown status it says there, or if the exit code is ok, then we should somehow do farder tests and continue like we did, as the connection is good anyway.
This was also tested using latest available snapshot builds with the same results, we have gone back to stable (these logs are from 19.07.4) as the snapshot build was having trouble with the wifi on this router, but the umbim problem and the solution we applied worked the same on snapshot as it does on stable.
If you need any other info, just ask.
The text was updated successfully, but these errors were encountered:
As you can see on the log this virtual movile network registration is carried like if we were roaming, this is quite typical here in Spain with all virtual operators, movile phones often tell you you are roaming and if you don't allow roaming it won't let you connect.
Maybe all the issue is just because of the roaming thing, I don't know, but then it would also affect all other roaming scenarios.