network-manager "drops IP" "AP change"

are you running gutsy? Can you stop Network Manager, start it from command line with --no-daemon and attach the output you get for the session? At best also insert marks in the log that show me what you did at which time of the log.

Thanks a lot,

 - Alexander

This is what happens after I start NetworkManager I guess I loose connection in the last part.

So when I try to change the access point association I have this (attachement file). However I'll always have the previous AP associatedeth1 IEEE 802.11g ESSID:"nerv"
          Mode:Managed Frequency:2.412 GHz Access Point: XX:XX:XX:XX:XX:XX<- OLD AP MAC address
          Bit Rate:11 Mb/s Tx-Power:15 dBm
          Retry limit:15 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=40/100 Signal level=-85 dBm Noise level=-86 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:2208 Missed beacon:0

On Fri, Aug 31, 2007 at 11:25:15AM -0000, João Mamede wrote:
> This is what happens after I start NetworkManager I guess I loose
> connection in the last part.
>
> ** Attachment added: "afterstarting.txt"
> http://launchpadlibrarian.net/9074220/afterstarting.txt
>

about what time window does this capture? 10sec? 30 sec? 1 min? more?

 - Alexander

As I said when I change access point it's like this right after

Trying to associate with 00:13:46:b9:79:5a (SSID='nervg' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.

After the boot it's like 30-45 seconds I think..Do you need a precise count?I do know that it's like 10 seconds between these two events:

NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:0e:a6:5b:52:39 (SSID='nerv' freq=2412 MHz)

On Sat, Sep 01, 2007 at 04:28:04AM -0000, João Mamede wrote:
> As I said when I change access point it's like this right after
>
> Trying to associate with 00:13:46:b9:79:5a (SSID='nervg' freq=2437 MHz)
> Authentication with 00:00:00:00:00:00 timed out.
>
> After the boot it's like 30-45 seconds I think..Do you need a precise
> count?I do know that it's like 10 seconds between these two events:
>
> NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
> Authentication with 00:00:00:00:00:00 timed out.
> Trying to associate with 00:0e:a6:5b:52:39 (SSID='nerv' freq=2412 MHz)
>

What was your driver/chipset? ipw3945?

 - Alexander

yes it's ipw3945..I saw some other bug reports with the same problem didn't got solved I think. And I think the problems only start after the window manager login. 'Cause my gdm/kdm->gnome/kde login got broken in a recent update and i'm running e17 from startx and it doesn't drop the IP

i think that this should be fixed now in:

modinfo ipw3945 | grep ^version
version: 1.2.2mp.ubuntu1

If you still see this bug, feel free to reopen and let us know.