Differences between version 11 and predecessor to the previous major change of WooshWireless.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 11 | Last edited on Thursday, June 16, 2005 11:19:27 am | by TomHibbert | Revert |
| Older page: | version 10 | Last edited on Thursday, June 16, 2005 10:20:43 am | by CriggieCriggie | Revert |
@@ -14,11 +14,11 @@
tender for in the Project Probe broadband initiative when it became
obvious that they would be unable to fulfill the contract.
----
-!! How to configure a Woosh USB
Modem under Linux
+!! How to configure a Woosh Modem using the Ethernet cable
under Linux
-Use the ethernet connection, I don't know of a way to make the USB connection work.
These modems speak PPPoE. The following instructions are for Debian Woody.
+
These modems speak PPPoE. The following instructions are for Debian Woody.
<verbatim>
apt-get install pppoe
</verbatim>
@@ -53,8 +53,123 @@
</verbatim>
And you should be away.
+!! How to configure a Woosh modem using the USB cable under Linux
+For this to work you almost certainly need a recent 2.6 kernel with ipw either available as a module or compiled into the kernel. This works out of the box with Ubuntu Hoary, just plug it in and you will see in dmesg the ipw driver loaded. It'll allocate you a usb tty:
+<verbatim>
+Jun 16 10:34:49 localhost kernel: ohci_hcd 0000:00:02.1: wakeup
+Jun 16 10:34:49 localhost kernel: usb 2-3: new full speed USB device using ohci_hcd and address 5
+Jun 16 10:34:50 localhost kernel: usb 2-3: configuration #1 chosen from 2 choices
+Jun 16 10:34:50 localhost kernel: ipwtty 2-3:1.0: IPWireless converter converter detected
+Jun 16 10:34:50 localhost kernel: usb 2-3: IPWireless converter converter now attached to ttyUSB0
+</verbatim>
+
+Create a ppp peer for woosh, by creating the file /etc/ppp/peers/woosh:
+
+<verbatim>
+noipdefault
+/dev/ttyUSB0
+115200
+defaultroute
+usepeerdns
+lcp-echo-interval 60
+lcp-echo-failure 3
+connect "/usr/sbin/chat -v -f /etc/chatscripts/woosh"
+noauth
+persist
+mtu 1400
+user "username@woosh.co.nz"
+maxfail 0
+deflate 15
+</verbatim>
+
+Create the chat script /etc/chatscripts/woosh:
+<verbatim>
+TIMEOUT 30
+ABORT "NO CARRIER"
+ABORT "BUSY"
+ECHO ON
+SAY "Dialling w00sh...\n"
+"" \rAT
+"OK-+++\c-OK" ATH0
+OK ATZ
+OK AT+CGDCONT=1,"PPP","woosh.co.nz","username@woosh.co.nz,foobar",0,0
+OK ATD*99#
+SAY "Waiting up to 30 seconds for connection ... "
+CONNECT ""
+SAY "Connected..."
+</verbatim>
+
+Note the double handling of the username/password, both in the chat script and in chap. This is almost certainly unnescessary but seems to simulate the Windows ipw software configuring the modem. You can probably get away with putting garbage in the chat script.
+
+Make an entry to chap-secrets as above with your username and pass.
+<verbatim>
+username@woosh.co.nz * pass *
+</verbatim>
+Then use pon to initiate the connection
+<verbatim>
+pon woosh
+</verbatim>
+
+A successful session looks like this in /var/log/syslog:
+<verbatim>
+
+Jun 16 10:52:20 localhost udev[10423]: creating device node '/dev/ttyUSB0'
+Jun 16 10:53:02 localhost pppd[10435]: pppd 2.4.2 started by tom, uid 1000
+Jun 16 10:53:03 localhost chat[10436]: timeout set to 30 seconds
+Jun 16 10:53:03 localhost chat[10436]: abort on (NO CARRIER)
+Jun 16 10:53:03 localhost chat[10436]: abort on (BUSY)
+Jun 16 10:53:03 localhost chat[10436]: send (^MAT^M)
+Jun 16 10:53:03 localhost chat[10436]: expect (OK)
+Jun 16 10:53:03 localhost chat[10436]: ^MAT^M^M
+Jun 16 10:53:03 localhost chat[10436]: OK
+Jun 16 10:53:03 localhost chat[10436]: -- got it
+Jun 16 10:53:03 localhost chat[10436]: send (ATH0^M)
+Jun 16 10:53:03 localhost chat[10436]: expect (OK)
+Jun 16 10:53:03 localhost chat[10436]: ^M
+Jun 16 10:53:03 localhost chat[10436]: ATH0^M^M
+Jun 16 10:53:03 localhost chat[10436]: OK
+Jun 16 10:53:03 localhost chat[10436]: -- got it
+Jun 16 10:53:03 localhost chat[10436]: send (ATZ^M)
+Jun 16 10:53:03 localhost chat[10436]: expect (OK)
+Jun 16 10:53:03 localhost chat[10436]: ^M
+Jun 16 10:53:03 localhost chat[10436]: ATZ^M^M
+Jun 16 10:53:03 localhost chat[10436]: OK
+Jun 16 10:53:03 localhost chat[10436]: -- got it
+Jun 16 10:53:03 localhost chat[10436]: send (AT+CGDCONT=1,"PPP","woosh.co.nz","user@woosh.
+co.nz,pass",0,0^M)
+Jun 16 10:53:04 localhost chat[10436]: expect (OK)
+Jun 16 10:53:04 localhost chat[10436]: ^M
+Jun 16 10:53:04 localhost chat[10436]: AT+CGDCONT=1,"PPP","woosh.co.nz","user@woosh.co.nz,
+pass",0,0^M^M
+Jun 16 10:53:04 localhost chat[10436]: OK
+Jun 16 10:53:04 localhost chat[10436]: -- got it
+Jun 16 10:53:04 localhost chat[10436]: send (ATD*99#^M)
+Jun 16 10:53:04 localhost chat[10436]: expect (CONNECT)
+Jun 16 10:53:04 localhost chat[10436]: ^M
+Jun 16 10:53:06 localhost chat[10436]: ATD*99#^M^M
+Jun 16 10:53:06 localhost chat[10436]: CONNECT
+Jun 16 10:53:06 localhost chat[10436]: -- got it
+Jun 16 10:53:06 localhost chat[10436]: send (^M)
+Jun 16 10:53:06 localhost pppd[10435]: Serial connection established.
+Jun 16 10:53:06 localhost pppd[10435]: using channel 4
+Jun 16 10:53:06 localhost pppd[10435]: Using interface ppp0
+Jun 16 10:53:06 localhost pppd[10435]: Connect: ppp0 <--> /dev/ttyUSB0
+Jun 16 10:53:07 localhost pppd[10435]: rcvd [CHAP Challenge id=0x1 <dfac9b0a884ea280b09aaed7853
+dd40b>, name = "akl-sky-ipw-lns1"]
+Jun 16 10:53:07 localhost pppd[10435]: sent [CHAP Response id=0x1 <d71d0c18b00e8352036de556a3ca
+dd8a>, name = "username@woosh.co.nz"]
+Jun 16 10:53:07 localhost pppd[10435]: rcvd [CHAP Success id=0x1 ""]
+Jun 16 10:53:07 localhost pppd[10435]: CHAP authentication succeeded
+
+
+Jun 16 10:53:08 localhost pppd[10435]: Cannot determine ethernet address for proxy ARP
+Jun 16 10:53:08 localhost pppd[10435]: local IP address 202.74.221.225
+Jun 16 10:53:08 localhost pppd[10435]: remote IP address 202.74.206.7
+Jun 16 10:53:08 localhost pppd[10435]: primary DNS address 202.74.207.10
+Jun 16 10:53:08 localhost pppd[10435]: secondary DNS address 202.74.207.100
+</verbatim>
----
CategoryCompany
