I confirm the bug in the 1.6.1 (installed via Karmic repos.). Strictly speaking, this is not a wicd bug: if I understood correctly from the wicd sources, wicd relies on a external dhcp clientto adquire the dynamic network configuration. In Debian/Ubuntu this client is dhclient. By default, the dhclient config requests DNS information (checkout the "request" line in /etc/dhcp3/dhclient.conf or your distro equivalent). Until the dhclient updates, my DNS config is correct
In order to fix this bug we have to write a good configuration file (which doesn't DNS requests) and pass it through
"dhclient -cf $FILE". I guess the:
"
client_dict = { "dhclient" : {'connect' : r"%(cmd)s %(iface)s", 'release' : r"%(cmd)s -r %(iface)s", 'id' : misc.DHCLIENT,
},
" @ wnettools.py
must be changed to "'connet': ... -cf %(file)" ....
I confirm the bug in the 1.6.1 (installed via Karmic repos.). Strictly speaking, this is not a wicd bug: if I understood correctly from the wicd sources, wicd relies on a external dhcp clientto adquire the dynamic network configuration. In Debian/Ubuntu this client is dhclient. By default, the dhclient config requests DNS information (checkout the "request" line in /etc/dhcp3/ dhclient. conf or your distro equivalent). Until the dhclient updates, my DNS config is correct
In order to fix this bug we have to write a good configuration file (which doesn't DNS requests) and pass it through
"dhclient" :
{'connect' : r"%(cmd)s %(iface)s",
'release' : r"%(cmd)s -r %(iface)s",
'id' : misc.DHCLIENT,
"dhclient -cf $FILE". I guess the:
"
client_dict = {
},
" @ wnettools.py
must be changed to "'connet': ... -cf %(file)" ....