NM 0.7: Huawei U620 keeps trying but fails to connect

Bug #270282 reported by csantiago
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Intrepid by Ricardo Jorge Maçãs

Bug Description

Binary package hint: network-manager

NM 0.7 keeps trying to connect my modem (Huawei U620) to my UMTS provider (PT KANGURU) but fails to connect.
Fortunately, it works using a command line configuration.

I am using Ubuntu 8.04 with Network Manager upgraded to version 0.7.

1) Provider info:
Name: Kanguru
Country: PT (Portugal)
Operator: P OPTIMUS
APN: myconnection
DNS: 62.169.67.172, 62.169.67.171
user: anything
password: anything

2) Huawei E620 (PCMCIA)
vendor=0x12d1
product=0x1001

2.1) chatscript (/etc/chatscripts/huawei_E620)
ABORT BUSY
ABORT VOICE
ABORT "NO CARRIER"
ABORT "NO DIALTONE"
ABORT "NO DIAL TONE"
"" ATZ
OK 'ATE1'
OK 'AT+COPS=0,0,"P OPTIMUS"'
OK 'AT+CGDCONT=1,"IP","myconnection","0.0.0.0",0,0'
OK 'AT+CGEQREQ=1,4,0,0,,,2,1500,"0E0","0E0",3,,0'
OK 'AT+CGEQMIN=1,4,0,0,0,0,2,1500,"0E0","0E0",3,0,0'
OK 'ATDT*99***1#'
CONNECT ""

2.2) PPPD Config (/etc/ppp/peers/kanguru_ttyUSB0)
connect "/usr/sbin/chat -v -f /etc/chatscripts/huawei_E620"
/dev/ttyUSB0
460800
noipdefault
usepeerdns
defaultroute
persist
noauth

2.3) AT&V
&C: 2; &D: 2; &F: 0; E: 1; L: 0; M: 0; Q: 0; V: 1; X: 0; Z: 0; S0: 0;
S3: 13; S4: 10; S5: 8; S6: 2; S7: 50; S8: 2; S9: 6; S10: 14; S11: 95;
+FCLASS: 0; +ICF: 3,3; +IFC: 2,2; +IPR: 115200; +DR: 0; +DS: 0,0,2048,6;
+WS46: 12; +CBST: 0,0,1;
+CRLP: (61,61,48,6,0),(61,61,48,6,1),(240,240,52,6,2);
+CV120: 1,1,1,0,0,0; +CHSN: 0,0,0,0; +CSSN: 0,0; +CREG: 0; +CGREG: 0;
+CFUN:; +CSCS: "IRA"; +CSTA: 129; +CR: 0; +CRC: 0; +CMEE: 0; +CGDCONT: (1,"IP","myconnection","",0,0)
; +CGDSCONT: ; +CGTFT: ;
+CGEQREQ: (1,4,0,0,0,0,2,1500,"0E0","0E0",3,0,0);
+CGEQMIN: (1,4,0,0,0,0,2,1500,"0E0","0E0",3,0,0); +CGQREQ: ; +CGQMIN: ; ;
+CGEREP: 0,0; +CGCLASS: "A"; +CGSMS: 3; +CSMS: 0; +CMGF: 0;
+CSCA: "+35193121314",145; +CSMP: ,,0,0; +CSDH: 0; +CSCB: 0,"","";
+FDD: 0; +FAR: 0; +FCL: 0; +FIT: 0,0; +ES: ,,; +ESA: 0,,,,0,0,255,;
+CMOD: 0; +CVHU: 1; ; +CPIN: ,; +CMEC: 0,0,0; +CKPD: 1,1; +CGATT: 1;
+CGACT: 0; +CPBS: "SM"; +CPMS: "SM","SM","SM"; +CNMI: 0,0,0,0,0;
+CMMS: 2; +FTS: 0; +FRS: 0; +FTH: 3; +FRH: 3; +FTM: 96; +FRM: 96;
+CCUG: 0,0,0; +COPS: 0,2,""; +CUSD: 0; +CAOC: 1; +CCWA: 0; +CLVL: 2;
+CMUT: 0; +CPOL: 0,2,""; +CTZR: 0; +CLIP: 0; +COLP: 0; ^PORTSEL: 0;
^CPIN: ,; ^ATRECORD: 0

Revision history for this message
csantiago (santiago-carlos) wrote :
Revision history for this message
csantiago (santiago-carlos) wrote :
Revision history for this message
csantiago (santiago-carlos) wrote :
Revision history for this message
Alexander Sack (asac) wrote :

Please reproduce and attach your complete /var/log/syslog after that

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Alexander Sack (asac) wrote :

also for missing provider info please file a new bug against the mobile-broadband-provider-info package

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in network-manager:
status: Incomplete → Invalid
Revision history for this message
Thomas Hood (jdthood) wrote :

This modem isn't listed at either

    https://wiki.ubuntu.com/NetworkManager/Hardware/3G/

or

    https://live.gnome.org/NetworkManager/MobileBroadband

as a supported model. Please file a request upstream at

    https://bugzilla.gnome.org/browse.cgi?product=NetworkManager

asking for support to be added.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.