#932: madwifi 0.9.2 wep in ad-hoc
-----------------------------+----------------------------------------------
Reporter: ksc | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: madwifi: driver | Version: v0.9.2
Keywords: | Patch_attached: 0
-----------------------------+----------------------------------------------
I'm not sure if this is being mentioned before, but I'm having some
problems with madwifi WEP keys in ad-hoc when I run a script to enable the
WEP key.
Problem:
Using 2 debian systems, I define my ath0 in /etc/network/interfaces to run
in Ad-Hoc mode. I run a script somewhere in the middle that says "up
startwep -i ath0" this will grab a predefined wep key and run the command
"iwconfig ath0 key xxxxxxxxxx". Running "iwconfig ath0" I can see that the
"Encryption key" field with the key that was defined and the "Link
quality" shows some number, and the "Cell" shows that it is connected to
my other Ad-Hoc system with the same set of commands (but with a different
ip).
But when I try to ping the other system, nothing comes up. Once I issue
"iwconfig ath0 key off" on both systems, the ping resumes.
I then replaced the line "up startwep -i ath0" with this "up iwconfig ath0
key xxxxxxxxxx" and it works! I have no clue as to why this is happening.
Anyone has a similar encounter?
--
Ticket URL: <http://madwifi.org/ticket/932>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
