Make auto-reconnect throttling configurable

Bug #1152802 reported by Paul Cowan on 2013-03-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
Medium
David Paleino

Bug Description

monitor.py throttles auto-reconnect to every 200 seconds after 3 retries.

Please make both values configurable so we can decide ourselves how agressive we want auto-retries to be:

        if (self.reconnect_tries > 3 and
            (time.time() - self.last_reconnect_time) < 200):

David Paleino (dpaleino) on 2013-03-09
Changed in wicd:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → David Paleino (dpaleino)
milestone: none → 2.0
Lionel Conrad-Bruat (lionelcb) wrote :

Actually, the long delay before reconnecting may be mistaken for the bug 'never reconnect after power-cycling the router'. Patching the above lines in monitor.py solved that.

FNB (fibean) wrote :

I know this feature is already assigned and on a milestone, but I do agree with the need of a configurable parameter. I'm currently working on an embedded project in which I'm using wicd and I need some seriously aggressive reconnect behaviour. For me, it was just a matter of commenting out those lines, but it would be nice to be able to reproduce the setting without changing the source code.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers