Anthony,

Can you have a look at this report ? My guess is that the problem is 
due to ifdown's behaviour. But maybe it is rather bad coordination 
between ifupdown and updhc ?

Thanks.


On Wed, Nov 09, 2005 at 07:55:02PM +0100, Fabian Kneißl wrote:
> Package: udhcpc
> Severity: normal

Thanks for your report.

> 
> System description:
> - udhcpc 0.9.8cvs20050303-1
> - resolvconf 1.33
> 
> Problem description (steps to proceed):
> 1. ifup eth0
>    => Interface is up, 
>       in /etc/resolvconf/run/interface/ are the files eth0.inet,
>       eth0.dhcpc
> 2. ifdown eth0
>    => Interface is down,
>       in /etc/resolvconf/run/interface/ is the file eth0.dhcpc,
>       which should not be there
> 
> Proposed solution:
> Change the parameter with which resolvconf is revoked:
> in files /etc/dhcpc/default.bound, [..]/default.deconfig, [..]/default.renew:
>       resolvconf -[ad] "${interface}.udhcpc"
> If you think, this is a problem of the resolvconf-package, please
> forward it to them.

I'm not sure whether this is a problem of udhcpc and/or resolvconf 
and/or ifupdown.


Apparently not resolvconf:

samples[0]# ls /etc/resolvconf/run/interface/
samples[0]# udhcpc -i eth0
udhcpc (v0.9.9-pre) started
Sending discover...
Sending select for 10.64.251.123...
Lease of 10.64.251.123 obtained, lease time 3600
Resetting default routes
adding dns 194.179.1.100
adding dns 194.179.1.101
samples[0]# ls /etc/resolvconf/run/interface/
eth0.udhcpc
samples[0]# resolvconf -d eth0.udhcpc
samples[0]# ls /etc/resolvconf/run/interface/
samples[0]#

So apparently, resolvconf does its job.


udhcpc looks ok too:

samples[0]# ls /etc/resolvconf/run/interface/
samples[0]# udhcpc -i eth0
udhcpc (v0.9.9-pre) started
Sending discover...
Sending select for 10.64.251.123...
Lease of 10.64.251.123 obtained, lease time 3600
Resetting default routes
adding dns 194.179.1.100
adding dns 194.179.1.101
samples[0]# ls /etc/resolvconf/run/interface/
eth0.udhcpc
samples[0]# killall -SIGUSR2 udhcpc
samples[0]# ls /etc/resolvconf/run/interface/
samples[0]# 


Now simply killing udhcpc leaves a dangling file:

samples[0]# udhcpc -i eth0
udhcpc (v0.9.9-pre) started
Sending discover...
Sending select for 10.64.251.123...
Lease of 10.64.251.123 obtained, lease time 3600
Resetting default routes
adding dns 194.179.1.100
adding dns 194.179.1.101
samples[0]# ls /etc/resolvconf/run/interface/
eth0.udhcpc
samples[0]# killall udhcpc
samples[0]# ls /etc/resolvconf/run/interface/
eth0.udhcpc


My guess is that ifdown just kills udhcpc without deconfiguring the 
interface.

-- 
Eric VAN BUGGENHAUT
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to