Dropped frames (unauthorized port) in AP mode

Ben Greear greearb
Sun Jul 21 16:04:43 PDT 2013

On 07/20/2013 06:25 AM, Jouni Malinen wrote:
> On Mon, Jul 15, 2013 at 04:20:47AM +0200, Mihai Moldovan wrote:
>> Got it! After checking every single option I've been using against Ben's config,
>> turning features off and back on, I was able to isolate the WEP entries as the
>> troublemaker.
>> Right after commenting wep_default_key(=0) and wep_key0(=somekey), hostapd
>> started behaving normally, even without a monitor interface.
>> Is specifying both WPA and WEP options known to cause such problems? It did work
>> fine in the past, but now it doesn't.
> What do you mean with working fine? What did you try to do with that
> wep_key0 parameter if the network was configured for WPA? I don't think
> WPA with static WEP would be supported.
>> If it's intended behavior and not actually a bug, hostapd should check for both
>> options being turned on and reject the config file, instead of starting in such
>> an unusable state. Jouni?
> Yes, wep_key# parameters should probably be rejected if wpa != 0. I
> don't think that wep_default_key=0 would have any effect on the
> functionality in your case, though.
> That said, it could also be finally time to consider removing WEP
> support from hostapd completely or at least do that for the default
> build. I don't see any other use for WEP apart from being able to run
> some test cases for station functionality to allow interoperability with
> old networks..

Well, I like the ability to run these old test cases...  At the least, please
don't remove the code entirely..but if you want to change the default build
options that seems fine.



Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

More information about the Hostap mailing list