Reply to Message

.. client side is a good point also though. It's the little things like simply disallowing all ad-hoc wifi through Windows policy.

Once the client node connects, the notice or connection icon should indicate the SSID though. As a connected client node, it knows the SSID.

One could potentially use a secondary router with same SSID and other AP details trying to get valid clients to join the spoofed AP rather than the valid AP. It's less easy than it sounds but justifies wifi enabled IDS and some cool lucient hardware (think that's the one's who make the wifi hunters anyhow).