josiahbryan

Group: Members
Posts: 11
Joined: Oct. 2006 |
 |
Posted: Oct. 04 2006,11:27 |
 |
No, i've nevre had DSL running in Ad-Hoc, so im not quite sure how to do it. However, with FC3 on an HP Tablet PC (TC 2000), I've ran ad hoc using just that command "iwconfig wlan0 mode Ad-Hoc", then set the essid with iwconfig as well. It would associate and communicate with win2k and winxp machines configured for ad-hoc as well ("computer-to-computer" in windows lingo.)
But back to the airdash - no, i havn't used it in ad-hoc, but i would assume the hardware would support it, it just sounds like a driver issue.
Is that error message from the driver or is it indicative of hardware rejection?
|