Today i have fallen in the these bug caused by zeroconf an i want to
contribute with information to confirm them and hoping to be useful to
solve them.
Also for me zeroconf was not installed on my choice but as a recommended
package. This package was present on my system since some week but its
effects was clear to me only today, when i've tryed a new ADSL router:
trying to understand why i could not connect to internet, ifconfig
revelead me the presence of a 169.254.0.0/16 network address, that i
had never set. And working with the ifup/ifdown/ifconfig programs
brought me to strange behaviours.
Up to yesterday i haven't got connection troubles since i was using an
ADSL modem with PPPoE, and seems it was unaffected.
The first thing that i have to report, and that i found to be related to
zeroconf, is that the boot process hang for some seconds during the eth0
bring up phase.
This delay is present even using ifup by hand.
After the boot process has completed, ifconfig reveal that eth0 has not
the network address i have set but another one that seems to be randomly
applied (and when i searched for information about such zeroconf thing,
i found that it was true).
The network address that i have set in /etc/network/interface file (say
192.168.1.1) it is not visible, but it is present in the system. In fact
if i ping 192.168.1.1, it replies me.
Now if i try to bring down eth0, it seems to success, but if try to
bring it up again it says:
-------------------------------------------------------------------
# ifup eth0
SIOCSIFADDR: File exists
Failed to bring up eth0.
#
-------------------------------------------------------------------
In fact, now ifconfig surprisingly reveal:
-------------------------------------------------------------------
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:01:4A:07:4C:1A
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::201:4aff:fe07:4c1a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1386 errors:0 dropped:0 overruns:0 frame:0
TX packets:1289 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1140907 (1.0 MiB) TX bytes:152146 (148.5 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
#
-------------------------------------------------------------------
My IP address is here but i can't bring it down with ifdown because it
correctly says:
-------------------------------------------------------------------
# ifdown eth0
ifdown: interface eth0 not configured
#
-------------------------------------------------------------------
I have to thank those who have reported these bugs since has pointed me
that the cause of such caos was zeroconf. Before that i was lost in the
dark, since i really couldn't understand what was happening.
For now i have uninstalled zeroconf, since i don't need it and now i
don't want to learn how can it be useful to me. But i hope that the
package maintainer will found a solution that make the package default
settings do not conflict with existing configuration. And if it is not
possible, to print at least a warning message during install, as happen
when you upgrade a kernel using the same version.
Regards.
Cesare.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
