Bug#691975: wnettools.py does not interface with resolvconf correctly

2012-11-01 Thread Thomas Hood
> > Remark: You should run FlushDNS *before* deconfiguring the interface, thus > > (I presume) before doing SetAddress('0.0.0.0') or anything like that. > > I'm running FlushDNS *before* putting the interface down, so I assume it's > already what you mean here. An idea behind resolvconf is that na

Bug#691975: wnettools.py does not interface with resolvconf correctly

2012-11-01 Thread David Paleino
On Thu, 1 Nov 2012 14:03:31 +0100, Thomas Hood wrote: > Well, the first thing I have done is to read the patch. I can at least say > that the patched code runs resolvconf with the correct syntax and that you > have the right idea. > > I don't know the wicd code very well, so I can't comment on wh

Bug#691975: wnettools.py does not interface with resolvconf correctly

2012-11-01 Thread Thomas Hood
Well, the first thing I have done is to read the patch. I can at least say that the patched code runs resolvconf with the correct syntax and that you have the right idea. I don't know the wicd code very well, so I can't comment on whether or not you are in fact calling FlushDNS() or flush_dns_addr

Bug#691975: wnettools.py does not interface with resolvconf correctly

2012-10-31 Thread David Paleino
Hello again Thomas, On Wed, 31 Oct 2012 21:31:55 +0100, Thomas Hood wrote: > If resolvconf is installed, wnettools.py uses "resolvconf -a" to add a > nameserver information record. However, a grep through the code reveals > that it nowhere removes that record (using "resolvconf -d"). This is a bu

Bug#691975: wnettools.py does not interface with resolvconf correctly

2012-10-31 Thread Thomas Hood
Package: python-wicd Version: 1.7.2.4-2 Severity: important If resolvconf is installed, wnettools.py uses "resolvconf -a" to add a nameserver information record. However, a grep through the code reveals that it nowhere removes that record (using "resolvconf -d"). This is a bug. When the program de