Educause Security Discussion mailing list archives
Re: WPA2/Enterprise startup/rollout headaches...
From: Josh Richard <jrichar4 () D UMN EDU>
Date: Fri, 15 Jul 2011 20:11:03 -0500
We configured it to only demote our SSIDs. I suppose if someone had a like named network at home. In addition to the utility, we also publish the connection requirements if individuals wish to connect manually. -j On Fri, Jul 15, 2011 at 3:13 PM, Rich Graves <rgraves () carleton edu> wrote:
Could (something like) XpressConnect ever create problems for users of other networks? What about a device configured to use WEP or WPA2-Personal at home? What about adjunct faculty who need to connect the same device to wireless networks at two different instititions with different sets of requirements?
-- Josh Richard Information Technology Systems & Services University of Minnesota Duluth
Current thread:
- WPA2/Enterprise startup/rollout headaches... Jeff Kell (Jul 13)
- Re: WPA2/Enterprise startup/rollout headaches... Randall C Grimshaw (Jul 13)
- Re: WPA2/Enterprise startup/rollout headaches... Justin Azoff (Jul 13)
- Re: WPA2/Enterprise startup/rollout headaches... Maloney, Michael (Jul 13)
- Re: WPA2/Enterprise startup/rollout headaches... Josh Richard (Jul 13)
- Re: WPA2/Enterprise startup/rollout headaches... Jeff Kell (Jul 14)
- Re: WPA2/Enterprise startup/rollout headaches... Lang, Matthew (Jul 15)
- Re: WPA2/Enterprise startup/rollout headaches... Josh Richard (Jul 15)
- Re: WPA2/Enterprise startup/rollout headaches... Rich Graves (Jul 15)
- Re: WPA2/Enterprise startup/rollout headaches... Randall C Grimshaw (Jul 15)
- Re: WPA2/Enterprise startup/rollout headaches... Josh Richard (Jul 15)
- Re: WPA2/Enterprise startup/rollout headaches... Whitlow, Michael (Jul 26)
