-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/24/2008 05:02 PM, Kevin Miller wrote: | I am fairly adamant in opposing any automatic rogue containment. Aside | from the obvious problems with uninformed administrators turning it | loose in inappropriate ways, the more generic complaint is that it | crosses the line from defending one's infrastructure to attacking | someone else's. My reaction is that you should implement restrictions on | the wired network if you observe someone connecting a "rogue" AP to it.
Great point. What strategies do you suggest on detecting rogue APs connecting to the network? Also, what about rogue APs that are not connected to our network. For example, if I have an AP that I setup to stream music in my campus housing, but don't connect it to the network, should this be considered a rogue and shut down? ~From my understanding, any device that is running in AP mode could potentially create noise to our other APs that are running on campus. In my mind, this means any AP device, whether it is connected to our network or not, could cause a service interruption. Thoughts? Thanks, Brian - -- Brian Epstein <[EMAIL PROTECTED]> +1 609-734-8179 Network and Security Officer Institute for Advanced Study Key fingerprint = 128A 38F4 4CFA 5EDB 99CE 4734 6117 4C25 0371 C12A -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFIEPgTYRdMJQNxwSoRAuMvAKClOQNVB/eDXVQEcy4PFvqdnV28TACfZYsr JEDmyYj6iKrxCzqTDilaM9o= =Ggba -----END PGP SIGNATURE----- ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
