dare2dreamer

Group: Members
Posts: 113
Joined: Feb. 2005 |
 |
Posted: Feb. 27 2006,05:49 |
 |
No problem.
Here's what I'm using to connect to my 802.11b WEP'ed AP, sans my keycodes, essid, etc:
sudo iwconfig eth0 essid "youressid" key s:key1 [1] key s:key2 [2] key s:key3 [3] key s:key4 [4] mode managed ap APMACADDRESSHERE commit
And then a:
sudo pump
Should get you an ip address.
As I recall, most ap setups don't actually require all four keys to be specified. If that's the case with yours, just set the first key s:ASCIIKEY (or key HEXKEY) and leave off the bracketed numbers.
As a guess, it's probably the "commit" command that is tripping you up. A handful of cards require it, and the rest toss errors at you about it.
-------------- ----dare2dreamer.
|