I found this thread, an I felt like commenting on it:
According to the information I have gathered from the forum, the OpenWRT solution for Virtual Access Points (VAPs) is implemented by simply including multiple SSIDs by means of multiple IEs in the same beacon.
Advertising multiple ESSIDs within the same beacon as a solution is said to have a number of shortcomings (see: www.drizzle.com/~aboba/IEEE/). The main drawback is that it is reportedly incompatible with many existing STA implementations (I have heard this from many places, though not experienced it myself.)
Another issue is that the usage scenarios where VAP implementations are particularly valuable normally require support for:
- Different capability sets for each SSID
- Multiple capability sets within an SSID
- Pre-authentication routing
Do you know if OpenWRT is be able to support such general VAP capablities, even though the implementation is based on the simple use of multiple ESSIDs within a beacon?
A good solution for virtual APs is instead to use separate BSSIDs for each Virtual AP, and send a separate beacon for each SSID. That is, only one information element containing the SSID in each beacon, but a separate beacon per each SSID.
Do you know if there is any plans of implementing such VAP functionality in OpenWRT?
Hope these questions make sense to you. I must admit I have not yet tested out OpenWRT. I have ordered an LinkSys WRT, and I am excited about testing out OpenWRT. Meanwhile, I try to figure out what OpenWRT has to offer. And I am daydreaming about all the fun capablities I would like to test out...