| 1 |
> Under madwifi (not sure if it was madwifi-ng or ye olde one that I used) |
| 2 |
> it can be used in master mode with multiple virtual access-points. For |
| 3 |
> example, one could have separate WEP & open networks on the same |
| 4 |
> wireless card; these were presented as different interfaces (wifi0, |
| 5 |
> wifi1, wifi...) so they could be firewalled appropriately. |
| 6 |
> |
| 7 |
> This card is sitting here ready for when I rebuild the server (in my |
| 8 |
> Copious Free Time, obviously). |
| 9 |
> |
| 10 |
> Can anyone tell me if the ath5k drivers support virtual APs in this way? |
| 11 |
> It is VERY useful. |
| 12 |
|
| 13 |
Last time I checked, ath5k did not support master mode, but the managed mode is |
| 14 |
very good (or better than madwifi-ng) and they fixed a lot of concept problems |
| 15 |
dealing with the creation/destruction of virtual interfaces (or so I was told). |
| 16 |
|
| 17 |
BTW, you can set multiple APs (wlan0, wlan1, etc) with madwifi-ng, but |
| 18 |
everything is locked by the hardware interface (wifi0)... or by everything, I |
| 19 |
mean all your virtual stuff will have to operate under the same radio frequency |
| 20 |
(set on the hardware, in wifi0). |
| 21 |
|
| 22 |
Simon |
Archives