Package: ifupdown Version: 0.6.8 Followup-For: Bug #393502
This problem has plagued me for a long time, especially when I'm stuck trying to deal with cranky out-of-tree wireless network drivers. It seems like the fundamental problem is that ifup/ifdown use a file to indicate their state rather than detecting it on the fly. Every time I have trouble, /etc/network/run/ifstate claims the interface is up, but in reality, ifconfig shows the device doesn't have an address. If at a minimum, ifup didn't write a change to ifstate unless ifconfig showed that we really have a valid connection, then this problem should go away. Is anyone still looking at this? This bug is over a year old. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ifupdown depends on: ii debconf [debconf-2.0] 1.5.16 Debian configuration management sy ii libc6 2.7-3 GNU C Library: Shared libraries ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip ii net-tools 1.60-17.2 The NET-3 networking toolkit ifupdown recommends no packages. -- debconf information: ifupdown/convert-interfaces: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
