ok, this is a linux and tech bLog-entry today. more or less a
reminder for if i will ever be in a situation like i was several
hours ago, and to help people to shorten the time wasted on de-
bugging and fixing. for all those that are neither interested
in a) technical stuff, b) being a ONE customer using umts, or
c) linux shell-stuff i apologise, but good news for you: you can
actually skip the rest of this article.
still reading? yippah, let's get on...
today i got to test a umts card by phone-/internet-service-pro-
vider ONE. i got the novatel wireless inc. merlin U630 card.
the first (though unfortunately not working) setup was made as
described to this site. most values do not work for a correct ONE
setup, so they had to be adjusted. additionally i could not find
any site that gave me a running config, so here is the guide
which made this card work for me:
at first make sure you have those tools installed (package-names
are for a debian-system):
+ - requirements::begin ---------------------------------------
ppp: /usr/bin/pon
ppp: /usr/sbin/chat
minicom: /usr/bin/minicom
netkit-ping: /bin/ping
- - requirements::end -----------------------------------------
remark: ping and minicom are optional and for debugging purpose.
secondly check if the card was found and initialised correctly
by the kernel (make sure module "serial_cs" is loaded...)
here's a minicom session done initially for debugging purposes:
+ - minicom-session::begin ------------------------------------
ati
Manufacturer: Novatel Wireless Incorporated
Model: Merlin U630 (HW REV Rev 2)
Revision: 14.0-14.0 [2005-05-18 15:39:38]
IMEI: 123456789012345
+GCAP: +CGSM,+DS
OK
- - minicom-session::end --------------------------------------
the first script involved is called /etc/ppp/umts.chat:
+ - umts.chat::begin ------------------------------------------
ABORT BUSY
ABORT 'NO CARRIER'
ABORT ERROR
REPORT CONNECT
TIMEOUT 10
"" "AT+CPIN?" READY-AT+CPIN=\042<PIN>042- "\c" OK "\c"
TIMEOUT 120
"" "AT&F"
OK "ATZ"
OK "ATE0V1&D2&C1S0=0+IFC=2,2"
OK "ATE1"
OK "ATDT*98#"
CONNECT c
- - umts.chat::end --------------------------------------------
"<PIN>" is the pin as provided by ONE. the second script, "umts"
contains these fine lines:
+ - peers/umts::begin -----------------------------------------
lock
connect "/usr/sbin/chat -f /etc/ppp/umts.chat"
defaultroute
/dev/ttyXX
460800
crtscts
modem
usepeerdns
novj
noauth
idle 300
persist
demand
noipdefault
- - peers/umts::end -------------------------------------------
"ttyXX" is the device the card gets assigned to. check dmesg(8)
for more infos. and to put all the pieces together, finally my
script combining all this stuff:
+ - one_umts.sh::begin ----------------------------------------
#!/bin/sh
echo "initialising umts-card and enabling umts..."
/usr/bin/pon umts
echo "dialing..."
/usr/sbin/chat -f /etc/ppp/umts.chat >/dev/null 2>&1
while [ "${?}" != 0 ]
do
echo "not connected..."
/bin/ping -c 1 nostromo.joeh.org >/dev/null 2>&1
done
echo "connected!"
- - one_umts.sh::end ------------------------------------------
and here is some output by the script...
+ - running one_umts.sh::begin --------------------------------
root@nostromo:/etc/ppp/ ./umts_one.sh
initialising umts-card...
enabling umts...
dialing...
not connected...
not connected...
not connected...
not connected...
not connected...
connected!
root@nostromo:/etc/ppp/ ping -q -c 1 nostromo.joeh.org
PING nostromo.joeh.org (193.170.32.26): 56 data bytes
--- nostromo.joeh.org ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 682.4/682.4/682.4 ms
root@nostromo:/etc/ppp/ poff umts
- - running one_umts.sh::end ----------------------------------
yeah, online! ;)
writebacks...
trackback
TrackBack ping me at: http://nostromo.joeh.org/cgi-bin/blog.cgi/blog_200605041909_one-umts.trackback
comment...