Comment 5 for bug 314574

Looking at the Network Manager code (version 0.7), it appears that the "(none)" string originates in the file nm-device-wifi.c . Digging around, it *seems* like this may be an issue with a failure of some of the expected IOCTL's in "n" mode.

In the function "nm_device_wifi_get_ssid" there is an IOCTL call to retrieve the SSID. I wonder if that is somehow failing? While I'm a programmer, this is getting beyond my skills with Linux development.

 memset (ssid, 0, sizeof (ssid));
 wrq.u.essid.pointer = (caddr_t) &ssid;
 wrq.u.essid.length = sizeof (ssid);
 wrq.u.essid.flags = 0;
 strncpy (wrq.ifr_name, nm_device_get_iface (NM_DEVICE (self)), IFNAMSIZ);

 if (ioctl (sk, SIOCGIWESSID, &wrq) < 0) {
  nm_warning ("Couldn't get SSID: %d", errno);
  goto out;
    }

It appears that at some point the SSID was correct, but then switches according to daemon.log:

Jan 6 18:46:34 ubuntu-laptop avahi-daemon[4877]: Registering new address record for 192.168.0.2 on eth1.IPv4.
Jan 6 18:46:34 ubuntu-laptop dhclient: bound to 192.168.0.2 -- renewal in 60998 seconds.
Jan 6 18:46:35 ubuntu-laptop NetworkManager: <info> (eth1): device state change: 7 -> 8
Jan 6 18:46:35 ubuntu-laptop NetworkManager: <debug> [1231289195.494675] periodic_update(): Roamed from BSSID 00:22:3F:36:6A:C8 (seteran) to (none) ((none))
Jan 6 18:46:35 ubuntu-laptop NetworkManager: <info> Policy set 'Auto seteran' (eth1) as default for routing and DNS.
Jan 6 18:46:35 ubuntu-laptop NetworkManager: <info> Activation (eth1) successful, device activated.
Jan 6 18:46:35 ubuntu-laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.