Ubuntu
network-manager package

  1. Bug #78037
  2. Comment #10

Comment 10 for bug 78037

Revision history for this message
Tony HIll (tonyhill) wrote : Re: rt2500 in feisty: problem & solution

Hello,

I have a similar problem with the hostap driver in Feisty. I'm not sure if it's related, but I'm seeing similar behavior with NetworkManager -- no association, but I can manually bring the interface up with iwconfig, or with wireless-* lines in /etc/network/interfaces.

I'm running Feisty with kernel 2.6.20-8-lowlatency and N-M 0.6.4-6ubuntu2.

The card is a PCMCIA Linksys WPC11 with a Prism III inside. The primary firmware is at 1.1.0 and the secondary firmware at 1.8.2. hostap_cs is the driver being used. The ESSID is hidden and the network in encrypted with a shared WEP key.

A few days ago, I decided to let N-M manage this connection. So, I removed the lines from /etc/network/interfaces that specified wlan0. Now, on boot, the connection does not come up. If I tell N-M to "Connect to Other Wireless Network", it prompts me for the ESSID, security, and key. After entering these details, N-M fails to associate with the AP. However, I know the card can work, since if I go to the terminal and enter:

ifconfig [interface] down
iwconfig [interface] essid [ESSID] key restricted [key]
ifconfig [interface] up
dhclient3 [interface]

Then the network works.

For the sake of diagnosis, I have attached the output of N-M when invoked in non-daemon mode.