ZTE CDMA2000 Data Terminal Model AC2787 does not working

[VINAY Kr. SHARMA]

I'm facing some critical issue with my data terminal. I'm using ZTE AC2787 Model and this is not working in Ubuntu 12.10 and 13.04.

I tried many time to connect to my "MTS MBlaze connection" by selecting from Network Indicator. It get connected but does not provides internet. After connecting when I visits some website then browser reports "Unable to connect".

But in some different condition it works well. How?

See the steps here, what I found:

1. Connect to some available WiFi internet network.
2. Then Also Connect to Mobile broadband network connection (In my condition MTS MBlaze Connection)
3. Then disconnect to connected WiFi network.
4. That's all (It is working...)

Above issue was in 12.10. And see what I found in 13.04:

When I tried to connect to mobile broad band then during the period of connecting it shows "Empty Label" instead Device registered name (MTS MBlaze).

And also in 13.04 does not works the above tric I found.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: network-manager 0.9.8.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux 3.8.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Wed Apr 10 16:19:18 2013
EcryptfsInUse: Yes
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-10-27 (164 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
IpRoute:
 default via 192.168.1.2 dev eth1 proto static
 169.254.0.0/16 dev eth1 scope link metric 1000
 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.32 metric 9
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to raring on 2013-04-09 (0 days ago)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1
 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.0 connected enabled enabled enabled enabled disabled

[VINAY Kr. SHARMA (vinaykrsharma)]

Syslog for network-manager using command:

grep -i networkmanager /var/log/syslog > network-manager.log

[Mathieu Trudel-Lapierre (cyphermox)]

Quickly, from the NetworkManager logs, I'd tentatively say that the modem can't find signal; but there's too little information to be able to know for sure.

Can you please provide debugging logs for ModemManager, see http://wiki.ubuntu.com/DebuggingNetworkManager for how you can get these logs.

Reassigning to modemmanager since that's what seems to be the culprit.

[VINAY Kr. SHARMA (vinaykrsharma)]

@Mathieu,

Attached log files as guided http://wiki.ubuntu.com/DebuggingNetworkManager.

[VINAY Kr. SHARMA (vinaykrsharma)]

Also see here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063687

and read comment #5

[Mathieu Trudel-Lapierre (cyphermox)]

The modem manager log 3 post actually seems to contain pretty much the information that we need, but it's not done with the debugging on.

Apr 30 01:24:47 vinay-Studio-1558 modem-manager[1798]: <info> Modem /org/freedesktop/ModemManager/Modems/3: state changed (enabling -> enabled)
Apr 30 01:24:47 vinay-Studio-1558 modem-manager[1798]: <info> Modem /org/freedesktop/ModemManager/Modems/3: state changed (enabled -> registered)
Apr 30 01:24:47 vinay-Studio-1558 modem-manager[1798]: <info> Modem /org/freedesktop/ModemManager/Modems/3: state changed (registered -> connecting)
Apr 30 01:24:48 vinay-Studio-1558 modem-manager[1798]: <info> Modem /org/freedesktop/ModemManager/Modems/3: state changed (connecting -> connected)
Apr 30 01:25:08 vinay-Studio-1558 modem-manager[1798]: <info> Modem /org/freedesktop/ModemManager/Modems/3: state changed (connected -> disconnecting)
Apr 30 01:25:09 vinay-Studio-1558 modem-manager[1798]: <info> Modem /org/freedesktop/ModemManager/Modems/3: state changed (disconnecting -> registered)
Apr 30 01:25:11 vinay-Studio-1558 modem-manager[1798]: <info> Modem /org/freedesktop/ModemManager/Modems/3: state changed (registered -> connecting)

Something's not working right in the connecting phase, but without debug information it's impossible for me to say what. Can you please re-do the same thing but make sure you have debugging enabled, just like in "log file 2"? Please follow the details at the wiki page I mentioned.

[VINAY Kr. SHARMA (vinaykrsharma)]

@Mathieu

I've attached all required log files as suggested on wiki page.

[VINAY Kr. SHARMA (vinaykrsharma)]

Modem Manager log

[VINAY Kr. SHARMA (vinaykrsharma)]

Syslog

[VINAY Kr. SHARMA (vinaykrsharma)]

ifconfig output was:
-----------------------------

eth0 Link encap:Ethernet HWaddr b8:ac:6f:56:72:45
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth2 Link encap:Ethernet HWaddr f0:7b:cb:28:7c:27
          inet6 addr: fe80::f27b:cbff:fe28:7c27/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:17
          TX packets:0 errors:20 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:17

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:1831 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1831 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:229952 (229.9 KB) TX bytes:229952 (229.9 KB)

[v2vpan (v2vpan)]

I also faced same problem
and I tried to ping router but It doesn't reply

[Launchpad Janitor (janitor)]

[Expired for modemmanager (Ubuntu) because there has been no activity for 60 days.]