OpenWrt/LEDE Project

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version Trunk
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by mantinan - 09.12.2020

FS#3500 - umbim: problem registering to network with Huawei K5150 and a virtual movile operator

Hi!

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:

— mbim.sh.orig 2020-12-04 15:11:47.000000000 +0100
+++ mbim.sh 2020-12-03 16:30:34.000000000 +0100
@@ -99,11 +99,7 @@

      tid=$((tid + 1))
      echo "mbim[$$]" "Register with network"

- umbim $DBG -n -t $tid -d $device registration || {
- echo “mbim[$$]” “Subscriber registration failed” - proto_notify_error “$interface” NO_REGISTRATION
- return 1
- }
+ umbim $DBG -n -t $tid -d $device registration

      tid=$((tid + 1))
      echo "mbim[$$]" "Attach to network"

So that it would continue no matter how the network registration felt, and it worked giving us this log:

Wed Dec 9 11:41:27 2020 daemon.notice netifd: wwan (1405): wwan[1405] Using proto:wwan device:/dev/cdc-wdm0 iface:wwan0 desc:Huawei K5150 composite
Wed Dec 9 11:41:27 2020 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): mbim[1405] Reading capabilities
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): devicetype: 0002 - removable
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): cellularclass: 0001
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): voiceclass: 0001 - no-voice
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): simclass: 0002
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): dataclass: 8000003F
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): smscaps: 0003
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): controlcaps: 0001
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): maxsessions: 0003
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): deviceid: 860112021925542
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): firmwareinfo: V8.1
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): hardwareinfo: CH1K5150M
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): mbim[1405] Checking pin
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): Pin Unlocked
Wed Dec 9 11:41:28 2020 daemon.notice netifd: wwan (1405): mbim[1405] Checking subscriber
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): readystate: 0001 - initialized
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): simiccid: 8934250220007795837F
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): subscriberid: 214035090779583
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): mbim[1405] Register with network
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): nwerror: 0000 - unknown
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): registerstate: 0004 - roaming
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): registermode: 0001 - automatic
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): availabledataclasses: 0020 - lte
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): currentcellularclass: 0001 - gsm
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): provider_id: 21403
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): provider_name: Orange
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): roamingtext: (null)
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): mbim[1405] Attach to network
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): nwerror: 0000 - unknown
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): packetservicestate: 0002 - attached
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): uplinkspeed: 0
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): downlinkspeed: 0
Wed Dec 9 11:41:29 2020 daemon.notice netifd: wwan (1405): mbim[1405] Connect to network
Wed Dec 9 11:41:30 2020 daemon.notice netifd: wwan (1405): sessionid: 0
Wed Dec 9 11:41:30 2020 daemon.notice netifd: wwan (1405): activationstate: 0001 - activated
Wed Dec 9 11:41:30 2020 daemon.notice netifd: wwan (1405): voicecallstate: 0000 - none
Wed Dec 9 11:41:30 2020 daemon.notice netifd: wwan (1405): nwerror: 0000 - unknown
Wed Dec 9 11:41:30 2020 daemon.notice netifd: wwan (1405): iptype: 0003 - ipv4v6
Wed Dec 9 11:41:30 2020 daemon.notice netifd: wwan (1405): mbim[1405] Connected, starting DHCP

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.

Regards.

mantinan commented on 09.12.2020 11:34

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.

Regards.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing