Your wireless network appears to have been compromised...


[UPDATE: Something about this router (WRT600N), my wife's macbook, and my Macbook Pro is causing this issue. I've turned off my 2.4GHz band on my router and connected an older access point to handle this traffic. Then just had my wife's macbook connect to that older access point and keep my on the 5GHz band. Have not had issues since then.]
Your wireless network appears to have been compromised and will be disabled for about a minute.

The exact error is pictured above. Everytime my wife's macbook would connect to our home's wireless network, this message would appear. Frustrated, I began to search the net for an answer. None of my other systems were having issues, Macbook Pro, PS3, PC, and Wii. So WTF!? Turns out it could be a number of things. It could be legitimate, but I use WPA2 for my 5GHz band and WPA for my 2.4GHz. My other mac's don't report this issue so what gives?

Turns out, that all I needed to do was reserve IP addresses for all my systems on the router. It was because my mac's and or other devices already had an IP address that for some STRANGE reason my Macbook wanted to get its hands... on... too.

Summary:
  • Be sure your router is setup to use WPA or higher security if your clients/systems are compatible.
  • Reserve IP's for your devices on your router's DHCP server.
  • This scenario may only apply to the WRT600N router from Linksys.
These posts were the most helpful in finding my solution:

Comments

Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more