[SOLVED] Sierra Wireless AirCard 313U

donalbane · 08-14-2012, 11:32 AM

I'm trying to get this card to work in Ubuntu 9.04, kernel version 2.6.28-19. I want to use it as a mobile broadband device, not a wireless access point. In Windows XP it is plug and play, so I know that the device works, and the account is set up.

don@ibmu:~$ lsusb

Code:

Bus 001 Device 008: ID 0f3d:68aa Airprime, Incorporated

don@ibmu:~$ dmesg | tail

Code:

[60640.566852] usb 1-4: APM supported, enabling autosuspend.
[60640.567044] usb 1-4: Sierra USB modem converter now attached to ttyUSB3
[60640.567086] sierra 1-4:1.4: Sierra USB modem converter detected
[60640.567892] usb 1-4: APM supported, enabling autosuspend.
[60640.569508] usb 1-4: Sierra USB modem converter now attached to ttyUSB4
[60640.569588] usbcore: registered new interface driver sierra
[60640.569596] sierra: sierra version: v.1.7.40
[60640.616869] usb0: register 'sierra_net' at usb-0000:00:1d.7-4, Sierra Wireless USB-Ethernet Modem, 9e:5c:05:2f:01:07
[60640.617469] usbcore: registered new interface driver sierra_net
[60645.713190] ADDRCONF(NETDEV_UP): usb0: link is not ready

don@ibmu:~$ ls -l /dev

Code:

lrwxrwxrwx  1 root   root   7 2012-08-14 11:01 USBModemAtt0 -> ttyUSB0
lrwxrwxrwx  1 root   root   7 2012-08-14 11:01 USBModemAtt1 -> ttyUSB1
lrwxrwxrwx  1 root   root   7 2012-08-14 11:01 USBModemAtt2 -> ttyUSB2
lrwxrwxrwx  1 root   root   7 2012-08-14 11:01 USBModemAtt3 -> ttyUSB3
lrwxrwxrwx  1 root   root   7 2012-08-14 11:01 USBModemAtt4 -> ttyUSB4

The status LEDs on the device keep oscillating between
POWER=flashing amber (modem initializing/searching for service)
DATA=OFF
and
POWER=solid blue (modem working normally)
DATA=flashing blue (detected a 3G network and ready to connect)
and sometimes
POWER=solid blue (modem working normally)
DATA=flashing green (detected an LTE network and ready to connect)
In Windows, the device just stays at
POWER=solid blue (modem working normally)
DATA=flashing green (detected an LTE network and ready to connect)
Something isn't working right here.

don@ibmu:~$ more /etc/ppp/peers/att

Code:

# This optionfile was generated by pppconfig 2.3.18. 
# 
#
hide-password 
noauth
connect "/usr/sbin/chat -v -f /etc/chatscripts/att"
debug
/dev/USBModemAtt3
115200
#defaultroute
noipdefault 
#user "none"
#remotename att
#ipparam att

#usepeerdns
unit 2
logfile /home/don/pppd_att.log

don@ibmu:~$ more /etc/chatscripts/att

Code:

# This chatfile was generated by pppconfig 2.3.18.
# Please do not delete any of the comments.  Pppconfig needs them.
# 
# ispauth PAP
# abortstring
#ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TO
NE' ABORT 'NO ANSWER' ABORT DELAYED
# modeminit
'' ATZ
#OK AT+CGDCONT=1,"IP","wap.cingular"
OK AT+CGDCONT=2,"IP","broadband"
# ispnumber
#OK-AT-OK "ATDT*99***1#"
OK ATD*99#
# ispconnect
#CONNECT \d\c
CONNECT ''
# prelogin

# ispname
# isppassword
# postlogin

# end of pppconfig stuff

don@ibmu:~$ more pppd_att.log

Code:

Script /usr/sbin/chat -v -f /etc/chatscripts/att finished (pid 26781), status = 0x0
Serial connection established.
using channel 4
Using interface ppp2
Connect: ppp2 <--> /dev/USBModemAtt3
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x4bd1ff2c> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth pap> <magic 0x97e990f8> <pcomp> <accomp>]
sent [LCP ConfAck id=0x0 <asyncmap 0x0> <auth pap> <magic 0x97e990f8> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x4bd1ff2c> <pcomp> <accomp>]
sent [LCP EchoReq id=0x0 magic=0x4bd1ff2c]
sent [PAP AuthReq id=0x1 user="ibmu" password=<hidden>]
rcvd [LCP DiscReq id=0x1 magic=0x97e990f8]
rcvd [LCP EchoRep id=0x0 magic=0x97e990f8 4b d1 ff 2c]
rcvd [PAP AuthAck id=0x1 ""]
PAP authentication succeeded
sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0>]
rcvd [LCP ProtRej id=0x2 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
Protocol-Reject for 'Compression Control Protocol' (0x80fd) received
rcvd [IPCP ConfNak id=0x1]
sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 0.0.0.0>]
Hangup (SIGHUP)
Modem hangup
Connection terminated.

It looks like the connection is being terminated by AT&T during the negotiation of the compression control protocol. However, if I add 'noccp' to /etc/ppp/peers/att, the Hangup still occurs in the same place, even though no compression control protocol negotiation occurs.

Can anyone offer suggestions as to how to get this modem working?

Thanks in advance,
Don

donalbane · 08-14-2012, 02:46 PM

I ended up changing the line in /etc/chatscripts/att from

OK ATD*99#

to

OK ATD*99***2#

to specify connecting to broadband instead of wap.

I also ended up editing /etc/ppp/options, commenting out 'modem', uncommenting '-vj', and changing lcp_echo_interval and lcp_echo_failure both to 0.

After that, I waited until the modem was in one of the periods where the LEDs were blue/blue-flashing, and then I executed 'pon' (If the modem was not in that LED cycle, it would not work). Once connected, even after disconnect, the modem's LEDs appear to stabilize and stay blue/green-flashing.

I will mark this thread as solved since I was able to connect, even though there is still a problem because the user needs to be able to see when the modem is in a cycle favorable for connection, which may not always be possible.

Don