Hi Mikael, On Wed, Jan 18, 2006 at 03:09:07PM +0100, Mikael Nilsson wrote: > Package: zeroconf > Version: 0.6.1-1 > Severity: critical > Justification: breaks unrelated software
I'll leave these as is, though I suspect these are inflated. > 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 Could you also show me what 'ip addr route' has before and after zeroconf is involved? > 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. Can you also provide /etc/resolv.conf and /etc/nsswitch.conf before and after 'zeroconf' is installed? > I'm at a loss trying to understand what's going on. >From what you have given me, what I think is happening is that your ADSL router also has link-local multicast name resolution available. And that for some reason the link-local address nameserver address is being placed into /etc/resolv.conf host, should never be querying a link-local address, only looks in /etc/resolv.conf -- so if there is a link-local address there, how did it get there? Was it already there? Was it provided? If there isn't a link-local address there, then perhaps the ADSL modem is generating packets with an incorrect source address? I'll need the information about your resolv.conf and nsswitch file (with before/after) to determine what next. Thanks, Anand -- `When any government, or any church for that matter, undertakes to say to its subjects, "This you may not read, this you must not see, this you are forbidden to know," the end result is tyranny and oppression no matter how holy the motives' -- Robert A Heinlein, "If this goes on --" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
