Hi,
We've been using SecureW2 since we rolled out our campus-wide wireless
network in 2003. It has always been an invaluable tool for connecting
Windows-based machines to our wireless.
We're now actually evaluating the Enterprise client and planning to
purchase a license. Previously me and
Hi Shane,
We have a comparable setup with a hidden SSID without encryption and a
more secure broadcasted SSID (not WPA2 yet, still using dynamic per-user
WEP keying with 802.1x). I haven't heard any complaints from iPhone 3G
users; perhaps there is a difference between their behaviour on a WPA2
Ah... how I pine for fat APs on certain days:)
Heh, yeah until you have to reconfigure 100 of them to expand a
subnet size ;) I still have a handful of fat 1200s floating around
in production to remind me how wonderful centrally managed Wireless
really is - despite some of its
At the University of Twente (NL) we support both TTLS/PAP and PEAP; for
PEAP we use an LDAP backend. The LDAP server has the passwords stored
with reversible encryption; our Radius server (Radiator) has the key to
decrypt them. Using cleartext passwords in LDAP would also work, but we
prefer the
You could try a different Radius server... we use Radiator
(http://www.open.com.au/radiator/) but eg FreeRADIUS
(http://freeradius.org/) is also a good choice. Both support a wide
variety of EAP methods, including PEAP and EAP-TTLS. Actually, we
support both on our wireless network (but prefer
