Re: zte mf691 connects but shows destination host unreachable



On Sun, 2012-09-09 at 02:21 +0800, ding dong wrote:
> Thanks. I patched the modemmanager source from ubuntu repo with
> default method as 
> MM_MODEM_IP_METHOD_DHCP and it works fine now.Below are the modem info
> if it helps. Its an unlocked one

Great.  I actually just bought a T-Mobile Rocket 2 as well, and I'll do
some more testing and then commit to a permanent solution.  I do not
recall what the situation was when I implemented this support over a
year ago, because I had to mail the device back to the owner right after
I got done.  But at the time, I don't believe the AT%IPDPADDR command
returned different results, and did *not* include the netmask
information.  That  meant static IP addressing with a /32 prefix, which
is currently hardcoded in NetworkManager because every Icera-based and
Option HSO device that used static addressing also used a /32 at that
time.

I see now that the Rocket 2 had a firmware update in March 2011, which
was 2 months after I returned the modem to its owner, so perhaps that
firmware update adds the DHCP support and extended AT%IPDPADDR command
information.

Based on your results, the device needs either:

1) DHCP, but we can't autodetect whether it's capable of DHCP or not,
hence the udev rules

2) static IP, but with the extended IPDPADDR info parsed, and possibly
using a non-/32 prefix

Dan

> 
> 
> ATI                                                                             
> MF691-3.0.0                                                                     
> Harrier_R1.2.5VCL328629                                                         
> TMO_USA_MF691V1.0.0B23                                                          
>                                                                                 
> MF691-3.0.0                                                                     
> Harrier_R1.2.5VCL328629                                                         
> TMO_USA_MF691V1.0.0B23 
> 
> 
> AT%
> IFWR                                                                         
> %IFWR: Modem        version   9.  1.  2.  5 number
> 328629                       
> %IFWR: Factory Test version   9.  1.  2.  5 number
> 328629                       
> %IFWR: Loader       version   9.  1.  2.  5 number
> 328629                       
> %IFWR: Mass Storage version   9.  1.  2.  5 number
> 328629                       
> %IFWR: ZeroCD Image - cannot read        
> 
> 
> 
> 
> 
> 
> It works fine with wvdial, because wvdial is using PPP.  This device
> is
> an Icera-based ZTE modem with an emulated ethernet port, which
> provides
> much higher speeds than PPP can.  Unfortunately, we need to handle
> these
> devices specially via some udev rules, like the K3805z, and it
> requires
> the latest version of ModemManager (either 0.6.0, or 0.5.4).
> 
> I'm not yet comfortable making the change upstream to have this modem
> use DHCP instead of static addressing, because when I added support
> for
> the MF691 (T-Mobile Rocket 2) long ago, I verified it was working with
> static IP addressing.  I'd like to figure out what changed between
> that
> version and the generic version, perhaps a firmware update or
> something.
> 
> In any case, the real fix here involves changes to both NM and
> ModemManager, but for the time being you can make things work if you
> have the latest ModemManager by modifying
> the /lib/udev/rules.d/77-mm-zte-port-types.rules file and adding your
> device near the bottom in a line like:
> 
> ATTRS{idProduct}=="1203", ENV{ID_MM_ZTE_ICERA_DHCP}="1"
> 
> 
> Dan
> 
> > uname -a 
> > Linux etuwa-pc 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23
> UTC
> > 2012 x86_64 x86_64 x86_64 GNU/Linux
> > 
> > lsb_release -a
> > 
> > No LSB modules are available.
> > Distributor ID:    Ubuntu
> > Description:    Ubuntu 12.04.1 LTS
> > Release:    12.04
> > Codename:    precise
> > 
> > 
> > lsusb
> > 
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate
> Matching
> > Hub
> > Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate
> Matching
> > Hub
> > Bus 001 Device 003: ID 138a:003c Validity Sensors, Inc. VFS471
> > Fingerprint Reader
> > Bus 002 Device 003: ID 0461:4dc7 Primax Electronics, Ltd 
> > Bus 002 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011
> > Bluetooth
> > Bus 002 Device 010: ID 19d2:1203 ZTE WCDMA Technologies MSM 
> > 
> > 
> > _______________________________________________
> > networkmanager-list mailing list
> > networkmanager-list gnome org
> > https://mail.gnome.org/mailman/listinfo/networkmanager-list




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]