From: SourceForge.net <no...@so...> - 2004-03-06 21:39:22
|
Bugs item #895630, was opened at 2004-02-12 03:07 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=543745&aid=895630&group_id=75380 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stefan Strigler (zeank) Assigned to: Nobody/Anonymous (nobody) Summary: start_net doesn't work with wep enabled Initial Comment: I'm using the latest start_net skript from cvs. Setting the wep key before ifconfig is done didn't work for me. Setting wep key after ifconfig configured the card did work. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-03-06 13:31 Message: Logged In: NO Using a driver build from current cvs-tree (as of march 3, 2004), I found some related misbehavior in debug output: 1.) acx100_interrupt is never called if WEP-key had been set before ifconfig had accessed the device. 2.) issuing "iwconfig wlan0 key off" does result in a call to acx100_issue_cmd cmd 0x2, which in turn is setting the old key once more instead of (somehow) cancelling it. 3.) if the accesspoint was offline before the WEP-key was set, the association is also not established, even if the ifconfig - related workaround was used. The difference is, that this time acx100_interrupt routine actually is getting called (with hw->state==0 (="started")) 4.) Switching the AP off and on again does *not* destroy the association, if it was established before. After my understanding, the wep-intitalisation vector should be different, but I do not see any related reaction in debug output (level was set to 0xffff). It would be nice to include at least at this website some documentation on the acx100 software interface. Starring at the sources does not really help, and changes between the versions are not documented. For example: somebody changed hw->irq_mask between pre6 and cvs-current from 0xdfb5 to 0xdbb5, without any comment why he thinks that this is useful! TI does not provide any detailed information, neither on acx-100 nor on TNET W1100B, which is the controller I have found in my dlink-650+ pcmcia card. And Maxim, who should have produced my Maxim 2880 radio chip, provides exactly zero related documentation on their website. The whole assembly seems to be classified information -- strange! Regards hm ---------------------------------------------------------------------- Comment By: Jochen Korb (jochenkorb) Date: 2004-02-26 10:28 Message: Logged In: YES user_id=102768 While using 0.2.0pre7 release i had the same fault, but i managed it using the wep key in start_net in a different syntax: 128 bit wep key: KEY="1234-1234-1234-1234-12" without the minus "-" it did not work! i do not use any ifconfig only iwconfig or the start_net script. ---------------------------------------------------------------------- Comment By: Andreas Mohr (andim2) Date: 2004-02-13 01:55 Message: Logged In: YES user_id=132674 Hmm, interesting. I'll have to check this. Maybe we're forgetting to do something properly in the driver (init issues). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=543745&aid=895630&group_id=75380 |