Last week or so I switched from cable internet to DSL and got and a new wireless gateway from my ISP (an AT&T 4111n). I use wicd to connect to wireless on my laptop.

Under my old wireless connection, wicd would always reconnect automatically when I came out of suspend, exactly as it is supposed to do. With this new connection, however, it would connect fine the first time after boot, but after coming out of suspend it would just hang on trying to get an ip address and never be able to reconnect. A reboot was necessary to get the wireless to work.

Attempting to eliminate any changes that could have caused the problem, I tried playing around with the encryption standards to get everything exactly the same way as my old connection where the issue did not exist. Unfortunately, I don't really remember the way I had it. At any rate, no encryption I tried had any effect.

The solution I found was to put a script in /etc/wicd/scripts/preconnect to unload the iwlwifi module and then load it again. This works, but I still would like to know what this sudden problem is all about.

Does anyone have any ideas?

Well, today it is only working about 50 percent of the time. It won't reconnect at all without reloading the module, though. I guess I need to look into this some more.

Had a similar problem with a laptop a while ago, suspected the router at the time but ended up switching to networkmanager that came with KDE as it didn't have any problems reconnecting automatically after sleep/hibernate.

Hmph. I just switched to wicd a few months ago because Network Manager kept flaking out on me during browsing. If I can't figure out why wicd suddenly won't cooperate I think I'll have to just ditch both of them and go back to the network scripts. I wish I knew what happened, though.