now that i have a functional AP i would like some virtual interfaces and
am appealing for some help
1)Define a structure for virtual interfaces [linked list ??]
here is what i have so far this will be the private data of a VIF
struct ath5k_vif *vif_data = (struct ath5k_vif *)conf->vif->drv_priv
Quick Observation ...
it appears IEEE80211 types have been replaced with NL80211 types in
kernel ... so would the following not be more correct and is opmode not
defined as
struct ath5k_softc {
enum nl80211_iftype opmode;
.
@@ -2130,14 +2129,15 @@ ath5k_beacon_config(str
Gents it is great to see this happen one snippet more and you will be
able to set the interface into AP mode from userspace hostapd and friends.
diff --git a/drivers/net/wireless/ath5k/base.c
b/drivers/net/wireless/ath5k/base.c
index e09ed2c..69aad6e 100644
--- a/drivers/net/wireless/ath5k/base
now that ap mode is functional with this driver im looking at multi-bss
VAP/VIF support and would like a quick poll.
as per-bss info is not in hostapd/nl80211 should it be put in there or
should there be a kernel option numradios that creates
number of wlanX interfaces in AP mode [or n-1 in AP
well the patch does compile and all works as expected in STA mode but
still no AP mode with hostapd.
A little bit of sniffing arround i came up with a recipe
Here is a required snipet for things to start moving on ...
@@ -488,6 +488,7 @@ ath5k_pci_probe(struct pci_dev *pdev,
hw->
well as way of introduction im running 2.6.27-rc7-wl-x86-smp and am keen
to get my hands dirty with ath5k AP
ill be tracking this quite closely attached find the patch i have used
to get it working as per Jiri 18/Aug/08
Ill try it out and feed back.
AFAIK some of the snipets bellow seem
