On Thu, 2006-05-04 at 09:44 -0700, Jouni Malinen wrote:
> Yes. Currently, I'm just using a configuration file parameter for this,
> but this information should eventually be exported by the kernel code to
> allow wpa_supplicant to select which mode to use without requiring user
> configuration.
F
On Thu, May 04, 2006 at 11:00:28AM +0200, Jiri Benc wrote:
> Ok. So what about PRISM2_HOSTAPD_MGMT_IF ioctl that will add management
> interface (if not added yet) and return its ifindex? It would accept a
> boolean parameter (like PRISM2_PARAM_HOSTAPD) to add/remove that
> interface. If you agree
On Wed, 2006-05-03 at 09:44 -0700, Jouni Malinen wrote:
> But there is.. I committed changes to the wpa_supplicant devel branch
> for this yesterday. It seems to work fine with net/d80211 and bcm43xx
> with this small patch to d80211 to allow the functionality to be moved
> into user space.
Cool,
On Wed, 3 May 2006 11:35:24 -0700, Jouni Malinen wrote:
> I think it would be nice to get this in so that both client and AP modes
> can use the same mechanism (user space MLME); hostapd already needs this
> wmaster0ap interface. In other words, if we do not want to see that
> interface by default,
On Wed, May 03, 2006 at 08:10:59PM +0200, Jiri Benc wrote:
> If you really feel this is a necessary feature (although I think we
> should focus more on putting the stack to a form suitable for inclusion
> in the kernel than on adding new features now), what about making the
> wmaster0ap interface
On Wed, 3 May 2006 09:44:58 -0700, Jouni Malinen wrote:
> Why do you think that this would be too early now? I agree that the
> interface between kernel and user space MLME can be improved, but I see
> no point in making client MLME implementation wait for that to happen.
> Personally, I don't thin
On Wed, May 03, 2006 at 06:28:15PM +0200, Jiri Benc wrote:
> It is too early for this. We need to implement some better communication
> interface between kernel and hostapd (or what will implement userspace
> MLME) first. The current solution, where there is some special
> net_device interface (wm
On Tue, 2 May 2006 14:18:17 -0700, Jouni Malinen wrote:
> Add a configuration option for disabling client MLME in kernel
> code. This is used to enable user space MLME for client mode (e.g.,
> with wpa_supplicant). The kernel MLME implementation is unmodified,
> but it could be removed or at least
Add a configuration option for disabling client MLME in kernel
code. This is used to enable user space MLME for client mode (e.g.,
with wpa_supplicant). The kernel MLME implementation is unmodified,
but it could be removed or at least made optional in build
configuration in the future.
Signed-off-
