What is the most effective way to connect my STS Developers Kit to Wi-Fi?
Some wireless networks monitor for the presence of what they determine to be “rogue” wireless access points and kill any client access to them by sending out deauthentication messages to clients trying to connect to them. This is a security measure to prevent someone inserting a wireless access point into an “official” network and fooling people into connecting to it.
Ocean Optics has heard from clients of some universities having their networks configured in this way.
To test if rogue access points are the issue, take the Raspberry Pi off-site (well away from your university network) and try to connect to it. If this works, then you may need to seek advice from your IT Group about how to resolve this issue.
Here’s an excerpt from the Cisco website on “Rogue Access Points”, describing in detail what to do if you cannot connect your STS Developers Kit to wi-fi.
Rogue Access Point Challenges
Rogue access points can disrupt wireless LAN operations by hijacking legitimate clients and using plain text or other denial-of-service or man-in-the-middle attacks. That is, a hacker can use a rogue access point to capture sensitive information, such as passwords and usernames. The hacker can then transmit a series of clear-to-send (CTS) frames, which mimics an access point informing a particular wireless LAN client adapter to transmit and instructing all others to wait. This scenario results in legitimate clients being unable to access the wireless LAN resources. Thus, wireless LAN service providers have a strong interest in banning rogue access points from the air space.
The operating system security solution uses the radio resource management (RRM) function to continuously monitor all nearby access points, automatically discover rogue access points, and locate them as described in the “Tagging and Containing Rogue Access Points” section.
Tagging and Containing Rogue Access Points
When the Cisco Unified Wireless Network Solution is monitored using WCS, WCS generates the flags as rogue access point traps and displays the known rogue access points by MAC address. The operator can then display a map showing the location of the access points closest to each rogue access point. The next step is to mark them as Known or Acknowledged rogue access points (no further action), Alert rogue access points (watch for and notify when active), or Contained rogue access points (have between one and four access points discourage rogue access point clients by sending the clients deauthenticate and disassociate messages whenever they associate with the rogue access point).