calling iwconfig and ifconfig every three seconds not efficient

Bug #510275 reported by jidanni on 2010-01-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
David Paleino

Bug Description

Turning on debugging, one discovers wicd is calling iwconfig and
ifconfig every three seconds. This seems not to efficient. Wouldn't it
be better to use some function calls, instead of execing whole /sbin
programs? I.e., use some tools found in other than man1 or man8 parts
of the UNIX manuals.

Andrew Psaltis (nacl) wrote :

This will not be dealt with in the 1.x series, it will be included in the rewrite, to be released in the yet unknown late future.

All bugs in wicd 1.x will not be fixed unless they are considered sufficiently problematic by the development team.

Changed in wicd:
status: New → Triaged
David Paleino (dpaleino) on 2011-09-18
Changed in wicd:
importance: Undecided → Medium
Wim Lewis (wiml) wrote :

(It does seem like using an rtnetlink socket and RTMGRP_LINK would be a much more efficient way to monitor link state changes, which I assume is what wicd is doing here.)

David Paleino (dpaleino) wrote :


I've been investigating how to use netlink sockets from Python, but it's quite a nightmare. I hope I won't finally give up :)

What I'd like to do is reimplement the behaviour of "ip monitor link" using Python. I already looked at the source code of "ip monitor" and "iotop" (the first one for the proper implementation, the second one because it uses netlink within Py).
However, the code is quite complex, and I haven't yet been able to make a simple status monitor listening to a netlink socket.

Be assured that this is what WICD is heading to though ;)


Changed in wicd:
importance: Medium → High
assignee: nobody → David Paleino (dpaleino)
milestone: none → 1.7.4
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers