From: Jouni Malinen (jkmaline_at_cc.hut.fi)
Date: 2002-07-15 18:04:48 UTC
On Mon, Jul 15, 2002 at 12:25:12PM +0200, R.Z.Slijp_at_kpn.com wrote:
> One is an embedded mode and the other is a normal environment. I've compiled
> my one kernel.
> Which I use in both modes. In the normal mode I can get the hostap driver
> too work. Even as part of
> a bridge, but i can't get it to work in the embedded mode.
Just to make sure I understood correctly.. Are you using the same kernel image on both modes?
> The module seems to load oke and my signal appears in NetStumbler with
> correct MAC and ESSID, but when I try to connect to the accespoint , I get a
> number of errors such as:
>
> * Trying to associate before authentication.
> * prism2_rx_80211: len(XXXX) > MAX(2304)
> * EXTRA DATA <XX><XX><XX>
Assuming you are using the driver-based AP management (i.e., have not defined PRISM2_HOSTAPD), there should not really by any difference on whether your user space stuff is from "normal" or "embedded" setup since this is performed fully in the kernel module.
> I use module hostap_pci.o for a DWL-520 (again it works fine in the normal
> mode) with the following line:
>
> I try to set up my network as follows (no errormessages here)
> modprobe hostap_pci channel=7 essid=RGE iwmode=3
Are you sure that the module was loaded successfully? Are you by any change using modprobe from busybox in the embedded setup, but from modutils in "normal" mode? I have noticed some problems when loading some modules with busybox versions of modutils--one of such modules has been hostap_cs.o.. I used PowerPC platform, but the same problem might be present on other platforms too. When the module gets somewhat corrupted, there will be _very_ weird looking problems..
-- Jouni Malinen PGP id EFC895FA