By: David Szpunar

David Szpunar — Sun, 20 May 2007 03:57:00 +0000

Austin – We are only using 802.1x for the employee link)','caption', 'Service Set Identifier' );">SSID (network name). The public wireless uses a second link)','caption', 'Service Set Identifier' );">SSID with broadcast turned on and all security turned off, like a coffee shop is often set up. People still have to authenticate using a single, common username and password (to make sure they’ve actually come in the church) posted on brochures around the lobby areas, but our Nomadix AG-3000 takes care of that and redirects people to the home/login page when they open their browser, no matter where they try to go.

I mentioned our Wirless system briefly on my post about ProCurve networking but I haven’t really said much about the wireless hardware in its own post. The ProCurve equipment we have lets us use 16 (32 in advance mode) SSIDs over the same radios, each with independent security settings and each connected to any specific VLAN I choose. This is why I say that the professional grade equipment rocks…a cheap Linksys won’t do this! (With the exception of a Linksys with modified firmware, but I haven’t done much with this.) Good question, thanks! I’ll write more about the wireless hardware soon.

By: Austin Spooner

Austin Spooner — Sun, 20 May 2007 03:47:07 +0000

David- I did this at our church about a year ago, but the one problem I have is that you cant just have a laptop out for a user to login to over wireless, because it does not authenticate until they are logged in. Have you found a way to fix this?

Comments on: Wireless 802.1x Authentication: Overview

By: David Szpunar

By: Austin Spooner