Package: ifupdown
Version: 0.7.49
Followup-For: Bug #709378

This bug is still present in ifupdown 0.7.49.

Note that this makes it impossible to use the pre-up command in the interfaces 
file.
This can have puzzling and annoying consequences for anyone who planned to use 
that to set up the firewall.

Specifically my firewall is configured to drop all traffic except authorized 
traffic. This means that before the rules have been set up for the lo 
interface, all traffic to lo is dropped. So I was using the following 
interfaces stanza for this in the past:

   iface lo inet loopback
           pre-up    /usr/local/sbin/fire up lo
           post-down /usr/local/sbin/fire down lo

But then my PC started taking a looong time to boot. I don't reboot often so I 
did not investigate immediately. It turns out the delay is caused by the 
if-pre-up.d/bind9 script which runs rndc to send commands to the named daemon 
over the lo interface. So because of this ifupdown bug that script was being 
run before the pre-up command specified in the interfaces file, and thus before 
traffic through the lo interface is allowed, causing the connection to time out 
after minutes.

Of course a workaround is to convert these commands to scripts but it should 
really not be necessary to treat lo as a special case.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ifupdown depends on:
ii  adduser      3.113+nmu3
ii  initscripts  2.88dsf-53.4
ii  iproute      1:3.16.0-2
ii  iproute2     3.16.0-2
ii  libc6        2.19-11
ii  lsb-base     4.1+Debian13

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.3.1-4

Versions of packages ifupdown suggests:
ii  net-tools  1.60-26
ii  ppp        2.4.6-3
pn  rdnssd     <none>

-- no debconf information


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

Reply via email to