after update to network-manager 0.6.6 my wireless stopped to work

[Marco Cimmino]

1) my wireless was ok after network-manager 0.6.6 updates
2) I've today 27 March 2008 up-to-date hardy and still problems
3) tried also to disable ipv6 but didn't help: alias net-pf-10 off ipv6
4) my wireless usb card is a: d-link DWL-G122
5) wireless connects correctly, works for few seconds then stop to retrieve any packet, but seems always connected and functional

Please help me, this is a severe regression

[Alexander Sack (asac)]

please attach the complete /var/log/syslog taken after a failed connect attempt.

[Marco Cimmino (cimmo)]

updated to 29/3/2008 still have the same problem

[Marco Cimmino (cimmo)]

updated to 5/4/2008 still the same problem, attached new syslog from today session

any help?

[Alexander Sack (asac)]

the syslog looks good from network-manager point of view. seems like you successfully connected and received an IP. So there is not much left that could be broken than the driver. reassigning to kernel.

[Andy Whitcroft (apw)]

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks!

[Luftikus (ubuntu-luto)]

I have a similar issue using the Karmic Koala daily-build live CD from today: I can connect to the AP entering IP address, netmask and other parameters. Using the automated setup by only entering the AP-Wifi-key results in a drop of the connection because there is no dhcp address found (don't know why). I will try to get some dmesg output and attach it here asap.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]