Package: zeroconf
Version: 0.6.1-1
Severity: critical
Justification: breaks unrelated software
Installing zeroconf (which was done without me noticing through a
recommends, probably) makes network connectivity in two completely separate
settings completely unusable. Thus breaks unrelated software.
I have a laptop, and I use laptop-net for managing eth0. This has worked in
a number of settings, including at home and at work.
Home:
Speedtouch ADSL2+ modem, which acts as gateway, DHCP server and DNS server.
Without zeroconf, I have
# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen
1000
link/ether 00:0d:56:ec:09:3c brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/24 brd 192.168.0.255 scope global eth0
inet6 fe80::20d:56ff:feec:93c/64 scope link
valid_lft forever preferred_lft forever
and everything works. My /etc/network/interfaces contains just
iface eth0 inet dhcp
and laptop-net is unmodified from its factory setting. I use dhcpcd, and
resolvconf.
Installing zeroconf, unplugging cable and reinserting cable results in the
following syslog:
Jan 18 14:49:27 yossarian ifd[7457]: executing:
'/usr/share/laptop-net/link-change eth0 managed up,running,disconnected
up,running,connected'
Jan 18 14:49:27 yossarian laptop-net: No change to network scheme
Jan 18 14:49:27 yossarian laptop-net: Starting network interface "eth0"
Jan 18 14:49:27 yossarian dhcpcd[25203]: broadcasting DHCP_DISCOVER
Jan 18 14:49:28 yossarian kernel: eth0: Setting full-duplex based on MII #24
link partner capability of 01e1.
Jan 18 14:49:28 yossarian kernel: ADDRCONF(NETDEV_CHANGE): eth0: link
becomes ready
Jan 18 14:49:31 yossarian dhcpcd[25203]: broadcastAddr option is missing in
DHCP server response. Assuming 192.168.0.255
Jan 18 14:49:31 yossarian dhcpcd[25203]: dhcpIPaddrLeaseTime=7200 in DHCP
server response.
Jan 18 14:49:31 yossarian dhcpcd[25203]: dhcpT1value is missing in DHCP
server response. Assuming 3600 sec
Jan 18 14:49:31 yossarian dhcpcd[25203]: dhcpT2value is missing in DHCP
server response. Assuming 6300 sec
Jan 18 14:49:31 yossarian dhcpcd[25203]: DHCP_OFFER received from
(192.168.0.254)
Jan 18 14:49:31 yossarian dhcpcd[25203]: broadcasting DHCP_REQUEST for
192.168.0.1
Jan 18 14:49:31 yossarian dhcpcd[25203]: dhcpIPaddrLeaseTime=7200 in DHCP
server response.
Jan 18 14:49:31 yossarian dhcpcd[25203]: dhcpT1value is missing in DHCP
server response. Assuming 3600 sec
Jan 18 14:49:31 yossarian dhcpcd[25203]: dhcpT2value is missing in DHCP
server response. Assuming 6300 sec
Jan 18 14:49:31 yossarian dhcpcd[25203]: DHCP_ACK received from
(192.168.0.254)
Jan 18 14:49:31 yossarian avahi-daemon[14473]: New relevant interface
eth0.IPv4 for mDNS.
Jan 18 14:49:31 yossarian avahi-daemon[14473]: Joining mDNS multicast group
on interface eth0.IPv4 with address 192.168.0.1.
Jan 18 14:49:31 yossarian avahi-daemon[14473]: Registering new address
record for 192.168.0.1 on eth0.
Jan 18 14:49:31 yossarian ifd[7457]: + dhcpcd.exe: interface eth0 has been
configured with new IP=192.168.0.1
Jan 18 14:49:31 yossarian ifd[7457]: + dhcpcd: MAC address =
00:0d:56:ec:09:3c
Jan 18 14:49:31 yossarian ifd[7457]: + dhcpcd: your IP address = 192.168.0.1
Jan 18 14:49:31 yossarian dhcpcd.exe: interface eth0 has been configured
with new IP=192.168.0.1
Jan 18 14:49:33 yossarian ifd[7457]: + Restarting filtering proxy server:
privoxy.
Jan 18 14:49:38 yossarian ntpdate[25253]: step time server 130.237.228.28
offset 0.147430 sec
Jan 18 14:49:38 yossarian ifd[7457]: + Running ntpdate to synchronize clock.
Jan 18 14:49:39 yossarian kernel: eth0: no IPv6 routers present
and
# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen
1000
link/ether 00:0d:56:ec:09:3c brd ff:ff:ff:ff:ff:ff
inet 169.254.253.111/16 scope link eth0
inet 192.168.0.1/24 brd 192.168.0.255 scope global eth0
inet6 fe80::20d:56ff:feec:93c/64 scope link
valid_lft forever preferred_lft forever
Fine, I don't necessarily have a problem with that. However, now things
start ot break.
$ host debian.org
;; reply from unexpected source: 169.254.141.11#53, expected 192.168.0.254#53
;; reply from unexpected source: 169.254.141.11#53, expected 192.168.0.254#53
169.254.141.11 happens to be my ADSL router's second address.
I'm at a loss trying to understand what's going on.
At work, the situation is very different. I can't reach computers on the
same subnet, but behind a hub (such as our mail and web servers). If I move to
the same hub
as them, I can reach them. I can also reach external computers.
removing zeroconf and disconnecting/reconnecting solves all these truobles
at home and at work.
Please advise.
/Mikael
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Versions of packages zeroconf depends on:
ii ifupdown 0.6.7 high level tools to configure netw
ii iproute 20041019-4.1 Professional tools to control the
ii libc6 2.3.5-12 GNU C Library: Shared libraries an
zeroconf recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
