Package: zeroconf Version: 0.6.1-1 Severity: serious I just discovered that I have zeroconf on my system. I didn't ask for it; it came in at the bottom of a dependency chain starting with rhythmbox. The way I discoverd it was this: when I booted up my computer, I had no network connectivity. At all. A brief investigation lead me to this fact:
[EMAIL PROTECTED]:~$ sudo ifup wlan0
dhcpcd.exe: interface wlan0 has been configured with old IP=192.168.0.101
[EMAIL PROTECTED]:~$ /sbin/ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:09:5B:92:31:AA
inet addr:169.254.66.229 Bcast:0.0.0.0 Mask:255.255.0.0
It seems that the zeroconf if-up.d script likes to wipe out existing
settings and replace them with a random private IP address. This is utterly
unacceptable, doubly so since zeroconf is a dependency of other packages.
As it appears from the package description that this is what zeroconf is
intended to do, it should be disabled by default, or at least not activated
unless the interface it's attached to has no IP address.
Daniel
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental'), (1, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages zeroconf depends on:
ii ifupdown 0.6.7 high level tools to configure netw
ii iproute 20051007-3 Professional tools to control the
ii libc6 2.3.5-12.1 GNU C Library: Shared libraries an
zeroconf recommends no packages.
-- no debconf information
signature.asc
Description: Digital signature
