802.1X Cofiguration query - can 802.1X authentication be optional?
Tue Sep 26 15:53:07 PDT 2006
I have received no reply to the mail below. These features are cutting
edge in expensive productuion hardware, so it may be that the development
effort has not reached this stage. Can the HostAP developers comment? If
not, can someone let me know how to speak with (one of) them?
Perhaps this is a feature request. Or perhaps it's so easy to configure
it's a dumb question. Either way, I do not know but need to.
Many thanks in advance for your time guys,
On Tue, 19 Sep 2006, lloyd wrote:
> We provide a community wireless network across much of our city. We
> promote open source and refuse to use anything but.
> We are looking at implementing an authentication system and have some
> queries regarding HostAPd's 802.1X implementation.
> Basically we want to run 802.1X alongside traditional WLAN user
> authentication systems such as NoCat, WifiDog etc which run at the
> transport level. As such we need to make 802.1X authentication 'optional'
> where failed connections are redirected to a different vlan. We can then
> run NoCat or whatever on traffic from this vlan.
> An example of this in the proprietary world would be the
> "auth-fail-action restricted-vlan"
> configuration directive found on Foundry routers and switches (see
> http://www.foundrynet.com/services/documentation/srcli/8021X_cmds.html for
> notes here).
> Basically we're looking to implement this proprietary feature in Open
> Source on a wireless AP, however I cannot see anything in HostAPd
> configuration to allow it. Any thoughts/comments on this would be
> BristolWireless Infrastructure
> HostAP mailing list
> HostAP at shmoo.com
More information about the Hostap