NetworkManager won't connect on FC6 box, revisited

["Tony Falcone" <Tony Falcone ssci com>]

Hi again,

I am continuing to have problems on my FC6 box.  In response to

        > > Date: Sun, 19 Nov 2006 19:02:32 -0500
        > > From: Dan Williams <dcbw redhat com>
        
        > I am having the same type of problem: I am using FC6, kernel
        > 2.6.17-1.2849.fc6, and cannot connect to my (wide open, no  encryption,
        > etc.) wireless home network using NetworkManager.  I can do so "by
        > hand," e.g., by issuing
        
        Which card & driver is this?
        
        Dan
        
I should have provided the following info

Card:
	Intersil Corporation Prism 2.5
        Wavelan chipset (rev 01)
                Subsystem: AMBIT Microsystem Corp. Unknown device 0200
                Flags: medium devsel, IRQ 10
                Memory at d000a000 (32-bit, prefetchable) [size=4K]
                Capabilities: [dc] Power Management version 2

Driver:
	hostap / hostap_pci

Upon looking more closely at the system logs, I have noticed that I
never get past "Stage 2" in initialization, i.e., I never reach the "IP
Configuration" stage, even after I receive the "Stage 2 Completed"
point.  For example (from my previously submitted logs):

  Nov 21 20:08:54 invictus NetworkManager: <information>  SUP:
  sending command 'ENABLE_NETWORK 0' 
  Nov 21 20:08:54 invictus NetworkManager: <information>  SUP:
  response was 'OK' 
  Nov 21 20:08:54 invictus NetworkManager: <information>
  Activation (eth1) Stage 2 of 5 (Device Configure) complete.

(At this point I would expect to enter "Stage 3 of 5"...)

  Nov 21 20:08:54 invictus kernel: ADDRCONF(NETDEV_CHANGE): wifi0:
  link becomes ready
  Nov 21 20:08:54 invictus kernel: ADDRCONF(NETDEV_CHANGE): eth1: link   becomes ready
  Nov 21 20:08:54 invictus kernel: wifi0: dropped unencrypted TX
  data frame (drop_unencrypted=1)
  Nov 21 20:08:55 invictus last message repeated 2 times
  Nov 21 20:08:56 invictus avahi-daemon[2531]: New relevant
  interface eth1.IPv6 for mDNS.
  Nov 21 20:08:56 invictus avahi-daemon[2531]: Joining mDNS
  multicast group on interface eth1.IPv6 with address
  fe80::202:8aff:fe7a:5bb3.
  Nov 21 20:08:56 invictus avahi-daemon[2531]: Registering new
  address record for fe80::202:8aff:fe7a:5bb3 on eth1.
  Nov 21 20:08:56 invictus kernel: wifi0: dropped unencrypted TX
  data frame (drop_unencrypted=1)
  Nov 21 20:08:57 invictus last message repeated 6 times
  Nov 21 20:08:57 invictus kernel: wifi0: CMD=0x0121 => res=0x7f,
  resp0=0x0004
  Nov 21 20:08:57 invictus kernel: wifi0: hfa384x_set_rid:
  CMDCODE_ACCESS_WRITE failed (res=127, rid=fc48, len=2)
  Nov 21 20:08:57 invictus kernel: wifi0: LinkStatus=2
  (Disconnected)
  Nov 21 20:08:57 invictus kernel: wifi0: LinkStatus:
  BSSID=00:0c:41:d8:65:82
  Nov 21 20:08:57 invictus kernel: wifi0: LinkStatus=2
  (Disconnected)
  Nov 21 20:08:57 invictus kernel: wifi0: LinkStatus:
  BSSID=44:44:44:44:44:44
  Nov 21 20:08:57 invictus kernel: eth1: Preferred AP (SIOCSIWAP)
  is used only in Managed mode when host_roaming is enabled
  Nov 21 20:08:57 invictus kernel: wifi0: CMD=0x0121 => res=0x7f,
  resp0=0x0004
  Nov 21 20:08:57 invictus kernel: wifi0: hfa384x_set_rid:
  CMDCODE_ACCESS_WRITE failed (res=127, rid=fc48, len=2)
  Nov 21 20:08:57 invictus kernel: wifi0: LinkStatus=2
  (Disconnected)
  Nov 21 20:08:57 invictus kernel: wifi0: LinkStatus:
  BSSID=44:44:44:44:44:44
  Nov 21 20:08:57 invictus kernel: wifi0: LinkStatus=2
  (Disconnected)
  Nov 21 20:08:57 invictus kernel: wifi0: LinkStatus:
  BSSID=44:44:44:44:44:44
  Nov 21 20:08:57 invictus kernel: eth1: Preferred AP (SIOCSIWAP)
  is used only in Managed mode when host_roaming is enabled
  Nov 21 20:08:58 invictus kernel: wifi0: LinkStatus=1 (Connected)
  Nov 21 20:08:58 invictus kernel: wifi0: LinkStatus:
  BSSID=00:0c:41:d8:65:82
  Nov 21 20:08:58 invictus kernel: ADDRCONF(NETDEV_CHANGE): wifi0:
  link becomes ready
  Nov 21 20:09:05 invictus kernel: eth1: no IPv6 routers present
  Nov 21 20:09:14 invictus NetworkManager: <information>
  Activation (eth1/wireless): association took too long (>20s),
  failing activation. 

What am I doing wrong?  I am sure that I have dhcdbd running, but
dhclient is never invoked.  (It is surely installed and working, too,
since I can cannot to the network "manually" via 'ifup wifi0' if I
want.)

BTW, I used NetworkManager on this same hardware (and in this same
network) when it was running FC5, and didn't have this problem.

Again, any help would be appreciated.

Thanks,

Tony

-- 
Tony Falcone, Ph.D.
Principal Research Engineer and
Group Leader, Signal Processing
Scientific Systems Company, Inc.
500 W. Cummings Park, Suite 3000
Woburn, MA  01801-6562
Office Phone: (781) 933-5355, x257      Fax: (781) 938-4752
Email: afalcone ssci com