Date: Sat, 25 Sep 2010 21:35:29 +0200 From: Joachim Schipper <joac...@joachimschipper.nl> To: misc@openbsd.org Subject: Re: help configuring Huawei E182E Message-ID: <20100925193529.gb22...@polymnia.joachimschipper.nl> Mail-Followup-To: misc@openbsd.org References: <b678c347d7c941b7b12f5e90cf58e9bf....@mailroot2.namespro.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <b678c347d7c941b7b12f5e90cf58e9bf....@mailroot2.namespro.ca> X-GnuPG-key: 8D6B3BAC X-GnuPG-fingerprint: 262B 1966 E79E FC2A FEA2 9BD1 845E B82C 8D6B 3BAC User-Agent: Mutt/1.5.20 (2010-08-04)
On Sat, Sep 25, 2010 at 07:34:59AM -0500, Anony (chicken) Mous wrote: > I'm having difficulty [configuring] the Huawei E182E wireless dongle > (...) with Telus mobility in Canada, I'm using 4.8-current, I have > copied the verizon ppp.conf example from umsm(4) manpage only changing > phone, authname, authkey without any success? > > Technical specification: http://tinyurl.com/2g3hszd > > My ppp.conf and error message from dialing ppp: > http://pastebin.com/KvwcF48U > > Thank you all greatly for any help. Some hints: 1. You can use cu -l ttyU0 to communicate with the device, this is useful for debugging/trying what works. Note that the 'AT' stuff is called the Hayes command set and quite Googleable. 2. Find out how to see the messages from your device. If you use pppd(8), call chat with the -V option and look at /etc/ppp/connect-errors; I'm sure ppp(8), which you're using, has similar options. 3. The following configuration (somewhat) Works For Me with XS4ALL in the Netherlands, using a HUAWEI E180. (For anyone finding this via Google: This is *not* XS4ALL's mobile internet, which uses a more modern device; this is the temporary mobile internet they provide you when you request an ADSL connection.) You may be able to use it as a basis. If your device doesn't have a pin set, you may need to remove everything between AT+CPIN? and +CPIN\sREADY-AT+CPIN=0000-OK (inclusive). Joachim P.S. Please send all information inline next time - it's small, but makes it possible to answer your questions e.g. on the train. /etc/ppp/peers/xs4all: # Use USB device cuaU0 # Taken from the Windows settings 460800 # Leave hardware flow control and compression enabled #nocrtscts #noccp #nobsdcomp #novj # Connection settings noipdefault noauth defaultroute user xum28 # XS4ALL doesn't care about their own IP, but let them override our idea if # they ever begin caring. :192.168.255.1 ipcp-accept-remote # XXX -v seems useless? connect "chat -V -f /etc/ppp/chatscript-xs4all" /etc/ppp/chatscript-xs4all: # 10s timeout should be enough - it's directly connected! TIMEOUT 10 # Report if it works REPORT CONNECT # Abort on various errors ABORT BUSY ABORT 'NO CARRIER' ABORT ERROR # Initialize '' ATZ # Has the PIN been entered? OK AT+CPIN? # If the PIN has already been entered, we get '+CPIN: READY' and continue; if # not, we send the PIN (AT+CPIN=0000), wait for OK, and continue. # # The next part configures the device: 3 means "use whatever is available", # apparently. # # FInally, we wait a bit. If we don't, everything *appears* to work, but we get # NO CARRIER. It appears to be necessary to set TIMEOUT higher than the time we # wait (i.e. the number of \d sequences). +CPIN:\sREADY-AT+CPIN=0000-OK AT+cgdcont=3,"IP","umts.xs4all.nl" '' \d\d\d\d\d # Dial the standard code OK ATD*99# # Start connection and pass control back to pppd CONNECT \d\c
