Access points appear with wrong names

[wad]

Sometimes an access point is not what it appears in the neighborhood display.

Running build 703, Q2D14, on MP laptops.

If access points are present which have a "null" essid, they appear in the neighborhood view as the first access point listed in /home/olpc/.sugar/default/nm/networks.cfg.

A laptop (X50, CSN7470144B), was showing the problem and logged. It was connected to a school WiFi access point, zoom50, but showed two circles in the neighborhood view (other than the three mesh circles). Both were labelled zoom50.

Scan logs from X50 are available at: http://xs-dev.laptop.org/mesh/test0417/twocircle/scan.log.x50 http://xs-dev.laptop.org/mesh/test0417/twocircle/scan.log.x50.1 http://xs-dev.laptop.org/mesh/test0417/twocircle/scan.log.x50.2

The Sugar, system, kernel and networking logs from this laptop are available at: http://xs-dev.laptop.org/mesh/test0417/twocircle/logs.CSN7470144B.2008-04-18.03-02-02.tar.bz2

In previous occasions, when the school access point has been turned off, we have also seen this, and the name or names are still zoom50, or linksys (the first name in some of the laptop's networks.cfg file).

[wad]

The extra beacons listed in the scan list are the active antennas monitoring the packets. The fix for turning them off obviously wasn't applied properly...