6 discovery for devices beyond AP1 (dhcp/radvd
server was on the other side of AP2). I only have this patch working through
2.6.32 at this point, not tried anything more recent. The router it runs on is
ar71xx based, and openwrt defaults to 2.6.32 for this device.
Pat Erley
On 11/24/10 22:
It depends on your goal. Here's what I've done in the past:
start hostapd on wlan0
iw dev wlan0 interface add wlan1 mode sta
Associate wlan1 to Random access point
route wlan0 through wlan1
What are you trying to achieve?
wlanconfig is a madwifi specific tool.
On 11/04/10 02:44, Queenie de Mel
tion, depending on
your particular needs and what distro you run.
As far as running ath9k in master mode:
http://wireless.kernel.org/en/users/Documentation/hostapd
That should be all you need. I've run ath9k as an AP for a long time now
(since before that page was authored), and when I
a2, 802.11n enabled, running on multiple VIFs.
I'm not running the VIFs bridged with wired though.
Pat Erley
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
nd wpa2 only uses CCMP, but again, that shouldn't
affect dhcp. Tried restarting dhcpd after hostapd? Maybe hostapd startup is
causing dhcpd to get wonky. Aside from that, I'd suspect something in your
firewall rules and/or something in your dhcpd.conf.
Pat Erley
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
This patch enables mesh point operation for ath9k. Tested with b43,
ath9k, rt2500usb, and ath5k as peers.
Signed-off-by: Pat Erley
---
No comments on the RFC, so I'm submitting it for consideration for
inclusion. Thanks to Oxford TEC for providing hardware that was
used in the develo
This patch enables mesh point operation for ath9k. Tested with b43
and ath5k as peers.
Signed-off-by: Pat Erley
---
Currently, you need to trigger a scan on the mesh point interface to
enable beaconing. This is the same behavior the ath5k, rt2500usb and
rt61pci drivers exhibit. Is this a
