Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jochen Voss <voss@seehuhn.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: which hostapd version for which wireless driver
Date: Tue, 28 Aug 2007 10:54:35 +0200	[thread overview]
Message-ID: <1188291275.7837.72.camel@johannes.berg> (raw)
In-Reply-To: <20070827223833.GA15515@seehuhn.de>

[-- Attachment #1: Type: text/plain, Size: 3186 bytes --]

On Mon, 2007-08-27 at 23:38 +0100, Jochen Voss wrote:
> Hello,
> 
> I am trying to get hostapd up and running on my Soekris net4521 board,
> until now without much success.  One of the problems might be that I
> am completely at a loss which version of hostapd is supposed to work
> together with which driver.
> 
> Any help about which combinations of hostapd and device driver have at
> least a chance of working together would be more than welcome.

Both git trees (wireless-dev and hostapd) work fine together :)

> *** LinkSys WRT54GL (broadcom 4318) ***
> 
> I tried the following drivers:
> 
> 1) CONFIG_B43 in current wireless-dev

That's the one you want.

> 2) CONFIG_BCM43XX in current wireless-dev
> 3) CONFIG_BCM43XX in 2.6.23-rc3
> 4) CONFIG_BCM43XX in 2.6.22.5

No chance of getting these working.

> I can succesfully use wpa_supplicant with this card, e.g. with driver
> 1) above, but there are some error messages.  On the console:
> 
>     ioctl[SIOCSIWAUTH]: Operation not supported
>     WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
>     WEXT auth param 5 value 0x1 - Internet Systems Consortium DHCP Client V3.0.4
>     Copyright 2004-2006 Internet Systems Consortium.
>     All rights reserved.
>     For info, please visit http://www.isc.org/sw/dhcp/

That's expected, ignore it.

>     pccard: CardBus card inserted into slot 1
>     PCI: Enabling device 0000:05:00.0 (0000 -> 0002)
>     PCI: Setting latency timer of device 0000:05:00.0 to 64
>     b43-phy7: Broadcom 4318 WLAN found
>     wmaster0: Selected rate control algorithm 'simple'
>     ssb: Sonics Silicon Backplane found on PCI device 0000:05:00.0
>     b43-phy7 ERROR: bbatt(11) >= size of LO array

Also known and can be ignored.

> *** Netgear WG511 (prism54) ***
> 
> I tried the following drivers:
> 
> 5) CONFIG_P54_PCI in the latest wireless-dev

I don't think that supports AP mode.

> 6) PRISM54 in the lates wireless-dev
> 7) PRISM54 in 2.6.23-rc3
> 8) PRISM54 in 2.6.22.5

Nor do those, HOSTAP driver is the one you'd want here, along with the
hostap hostapd driver.

> Example: combination 1c (CONFIG_B43 in wireless-dev, current
> http://w1.fi/hostap.git) gives
> 
>     root@funk [~] iwconfig wlan1 mode master
>     root@funk [~] iwconfig wlan1 essid "SR20"
>     root@funk [~] iwconfig wlan1 channel 6
>     root@funk [~] iwconfig wlan1 rate 11M
>     root@funk [~] ifconfig wlan1 up

Don't do any of that, hostapd configures everything.

>     root@funk [~] ifconfig wlan1 192.168.2.1

Do that after starting hostapd while the interface was down.

>     root@funk [~] hostapd /etc/hostapd.conf
>     Configuration file: /etc/hostapd.conf
>     Opening raw packet socket for ifindex 15
>     BSS count 1, BSSID mask ff:ff:ff:ff:ff:ff (0 bits)
>     Hardware does not support configured mode
>     wlan1: IEEE 802.11 Hardware does not support configured mode (2)
>     Could not select hw_mode and channel. (-1)
>     rmdir[ctrl_interface]: No such file or directory

You need to start hostapd while the interface is down ("ip link set
wlan1 down").

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2007-08-28  8:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27 22:38 which hostapd version for which wireless driver Jochen Voss
2007-08-28  5:54 ` Kalle Valo
2007-08-28 22:28   ` Jochen Voss
2007-08-28  8:54 ` Johannes Berg [this message]
2007-08-28 22:27   ` Jochen Voss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1188291275.7837.72.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=voss@seehuhn.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox