seem to connect correctly with static IP but can't communicate with the net

[Luca Dariz]

Binary package hint: network-manager

I am using Ubuntu 9.04 and my wireless has WEP encryption.

Seems to connect correctly, the association and autentication with the AP works fine (I have static IP configuration), but can't exchange packets, nor perform arp requests (if I set DHCP, it keeps waiting for DHCPOFFER).
Setting up the connection manually with iwconfig works fine, with both static IP and DHCP.
I followed the instructions found in https://wiki.ubuntu.com/DebuggingNetworkManager and I attach the output of syslog and nm-serial

Currenly I am running:
luca@descartes:~$ uname -a
Linux descartes 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:38:53 UTC 2009 i686 GNU/Linux

[Luca Dariz (luca-dariz)]

I noticed that when connecting manually iwconfig gives me:

wlan0 IEEE 802.11bg ESSID:"WLAN_C0"
          Mode:Managed Frequency:2.422 GHz Access Point: 00:1A:2B:05:DA:A9
          Bit Rate=12 Mb/s Tx-Power=27 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2352 B
          Encryption key: <key> Security mode:open
          Power Management:off
          Link Quality=56/100 Signal level:-59 dBm Noise level=-69 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

but when trying with network manager gives me:

wlan0 IEEE 802.11bg ESSID:"WLAN_C0"
          Mode:Managed Frequency:2.422 GHz Access Point: 00:1A:2B:05:DA:A9
          Bit Rate=12 Mb/s Tx-Power=27 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2352 B
          Encryption key:<another key> Security mode:open
          Power Management:off
          Link Quality=56/100 Signal level:-58 dBm Noise level=-68 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

so the field Encryption key is different.
May this mean that NM has some trouble managing the key after authenticating with the AP?

[Alexander Sack (asac)]

disabling DHCP and using static is just pushing the issue back until you want to communicate for real. can you please use DHCP, reproduce and attach a new syslog?

Also i see you are using b43 driver. Have you tried other broadcom drivers available? e.g. b44, bcm... wl?

[Luca Dariz (luca-dariz)]

Finally I found a workaround:
setting manually the key in the options of the wireless connection and NOT when prompted automatically.

Here I have to set the key that gives me the iwconfig command when connected correctly and run as root, it's not the ASCII key but the key in hexadecimal.

In detail, to make things work again, I did:

-deleted the connection
-restart network manager, which attempt to connect but fails and prompt me for the key
-cancel the prompt
-manually set the key: right click on the applet->edit connections->wireless->edit the connection that fails
-on the security tab, replace the key with the hex value of the key
-apply the changes and try to connect again, this time it works!

I took a syslog when trying to connect after have deleted the connection, which is the step that fails to save the key, hope it can help.

I haven't tried with other driver since I was using Ubuntu 7.10, at that time I was using ndiswrapper and worker fine; b44 do not support my chipset, I have a 4318.
I may try with ndiswrapper or with the old bcm43xx or wl, which I never heard about, and see if it solves.

[Luca Dariz (luca-dariz)]

I wrote fast, and I wrote a bit wrong how I did to make things work, here's the correction:

-deleted the connection
-restart network manager(maybe not necessary), choose the wireless net and insert the ASCII key
-Network manager attempt to connect but fails and prompt again for the key
-cancel the prompt
-manually set the key: right click on the applet->edit connections->wireless->edit the connection
-on the security tab, replace the key with the hex value of the key
-apply the changes and try to connect again, this time it works!

[Luca Dariz (luca-dariz)]

With ndiswrapper the issue remains and I solve it in the same way

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]