I am another person who has suffered strange network behaviour that turns out to be related to the default behaviour of zeroconf and which took quite some effort to track down.
At work we have a class B public IP address range that covers the whole site, though the site is divided into a number of class C subnets. I have two Debian machines at work on this network that have the public address set statically with a class C netmask. On booting zeroconf added a link-level (169.254) address to the first Ethernet interface on each machine and reset the broadcast address so the machine broadcasts to the whole of the class B network associated with the public IP address rather than the class C subnet as statically configured. At home I have statically assigned private addresses and I have had ssh prompt me asking if I really want to connect to another machine, presumably because it has identified itself by the link-level address rather than the private IP address. To add further confusion the ifconfig command appears only to report one of the IP addresses associated with an interface and whenever I tried it it always reported the link-level address rather than the public or private address. Multiple IP addresses per interface and link-level addresses are no doubt useful but to me this package in it's default configuration breaks too many things. Either the default configuration of this package needs to be changed so it does not touch interfaces with static addresses assigned or dependencies (including recommends) on this package need to be removed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
