Comment 12 for bug 64173

Revision history for this message
Fionn (fbe) wrote : Possible fix

As promised I am releasing a patch that seems to help at least on my system, as far as I could test yet. the patch is for the current feisty source. The patch also includes a little fix for Bug #91698 which makes backporting easier.
If you remove the top 47 lines from the patch, the patch will also apply to the edgy source tree.

Just apt-get source, apt-get build-dep, patch and dpkg-buildpackage. Dont blame me if things get stuck.

As you can read in my earlier posts I originally intended to make the timeout configurable via gconf. I dropped this idea for now since network-manager itself is not capable of using gconf at all. It receives all its configuration via dbus command sequences. So I hacked "nm-tool" to include an option for setting the timeout. Feel free to add the functionality to the gnome applet - it can store the settings via gconf then.

Once you have applied the patch you can set the reconnection timeout to e.g. 20 seconds when NM is running by issuing the following command:

#> nm-tool --set-timeout 20000

You can do this automatically in a script and even adjust the timeouts for different connection situations.
Just drop the script in /etc/NetworkManager/dispatcher.d/
See also "man NetworkManagerDispatcher" for info

Happy patching. And report back if it does not do you any good!