I succeeded to use sudo to run my custom script. The connection is very stable and till now it has never dropped. I think, wicd was incorrectly assuming a broken connection when a network request was made and it took the router more time than wicd expected.

EDIT:
I copied the custom script to the /sbin directory to forbid it being modified since it is allowed to run and practically it can contain any root command.

Its permissions are:
What do you think?

I believe Debian uses Sys-V init. You can find more about startup scripts here.

http://www.debian-administration.org/articles/28

There is also some documentation on using the CLI for Wifi here.

http://wiki.debian.org/WiFi/HowToUse#Command_Line

Ultimately it's up to you how you administer your system. If you are satisfied with the current setup, security, and performance then that's all that really matters. That's the beauty of a Linux system, it can be customized as you/we see fit.

Good luck. ;-)

The custom script is hardened in a way that it cannot be modified unless the user is root. I placed it under /sbin for that precise reason. Moreover, I never log in as root apart from using su because there is no need to log in as root as chmod and chown can do miracles in case one may need to edit system files with a graphical editor. I use vim which obviously doesn't run in a gui environment although kwrite is more attractive but kwrite needs the kde libraries and xorg. If something goes wrong with the gui environment I want to be still able to work around and repair my system becaue gnu linux gives me the tools to recover my system whatever happens to it.

My setup is so stable that it can be incorporated into a package. A small systray applet can call the script whenever the connection drops and the timing parameters can be made accessible to the user for fine tuning.