Package: ifupdown
Version: 0.6.9
Severity: normal

--- Please enter the report below this line. ---

Hello!

I use ifupdown 0.6.9, resolvconf 1.45 and udhcpc 0.9.8cvs20.
eth3 is configured by dhcp
When I call "ifdown eth3" eth3-specific data (sent to me by dhcp server) is
not cleaned out from /etc/resolv.conf

Details of problem:
My settings are
   /etc/network/interfaces: eth3 inet dhcp
   udhcpc is installed, no other dhcp-clients are installed
   resolvconf is installed

I perform:
   1) cat /etc/resolv.conf
   2) ifup eth3
   3) cat /etc/resolv.conf
   4) ifdown eth3
   5) cat /etc/resolv.conf

I wish to get:
   1) eth3-specific lines absent
   3) eth3-specific lines present
   5) eth3-specific lines absent

I get:
   1) eth3-specific lines absent
   3) eth3-specific lines present
   5) eth3-specific lines present


Possible reasons:
Why these lines are not cleaned?
I found even 3 attempts to clean them.

First one is located in /etc/udhcpc/default.deconfig
but this script isn't launched when I call "ifdown eth3"
I think this happens because ifconfig sends TERM signal to udhcpc (see code 1)
but udhcpc is listening for SIGUSR1, SIGUSR2 (see code 2)

Second and third attempts (something like a hack) are located in /etc/network/if-down.d/resolvconf:
/sbin/resolvconf -d "${IFACE}"
/sbin/resolvconf -d "${IFACE}.${ADDRFAM}"
But udhcpc's file is named "${IFACE}".udhcpc and leaves unproceeded after these operations

Possible ideas for solution:
should the /sbin/resolvconf -d be called by dhcp client or via /etc/network/if-down.d/resolvconf? is sending TERM signal to udhcpc a bug? maybe udhcpc remains holding the lease?

maybe there should be a naming conventions for resolvconf interface files?
e.g. ${IFACE}.${ADDRFAM} regardless of dhcp client name

---code 1---
bashtanov:/home/bash# ifdown -v eth3
Configuring interface eth3=eth3 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/openvpn
run-parts: executing /etc/network/if-down.d/resolvconf
cat /var/run/udhcpc.eth3.pid | xargs -i kill -TERM {}
ifconfig eth3 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
Configuring interface eth3=eth3 (inet6)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/openvpn
run-parts: executing /etc/network/if-down.d/resolvconf
ifconfig eth3 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
---/code 1---

---code 2---
bashtanov:/home/bash# man udhcpc|grep TERM
bashtanov:/home/bash# man udhcpc|grep -A 2 -B 3 SIGUSR
NOTES
      udhcpc responds to the following signals:

      SIGUSR1
This signal causes udhcpc to renew the current lease or, if it does not have one,
             obtain a new lease.

      SIGUSR2
             This signal caused udhcpc to release the current lease.

)
---/code 2---

Regards,
   Alexey Bashtanov

--- System information. ---
Architecture: i386
Kernel: Linux 2.6.30-1-686

Debian Release: 5.0
500 testing debian.local
500 stable debian.local

--- Package information. ---
Depends (Version) | Installed
========================-+-===========
net-tools | 1.60-22
libc6 (>= 2.3) | 2.9-4
lsb-base | 3.2-22


Package's Recommends field is empty.

Suggests (Version) | Installed
===========================-+-===========
iproute |
dhcp3-client | 3.1.1-6
OR dhcp-client |
ppp | 2.4.4rel-10.1







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

Reply via email to