Re: i stumped

[Florian Kulzer <florian@molphys.leidenuniv.nl>]

On Sun, Jul 23, 2006 at 19:58:29 -0700, Rodney D. Myers wrote:
> I'm running debian etch, with all current updates.
> 
> After a thunderstorm dropped power a few times, I have been back on the
> net, obviously.
> 
> For some reason, the /etc/network/interfaces file is not being
> read, or not being read properly.
> 
> cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> auto eth0
> iface eth0 inet static
>         address 192.168.1.102
>         netmask 255.255.255.0
>         network 192.168.1.0
>         broadcast 192.168.1.255
>         gateway 192.168.1.1
> 
> When using this file, and then doing an ifconfig, I get these results;
> 
> ifconfig eth0
> eth0      Link encap:Ethernet  HWaddr 00:0D:87:15:8E:33
>           inet addr:169.254.*.*  Bcast:0.0.0.0  Mask:255.255.0.0 (removed for a
>           inet6 addr: fe80::20d:87ff:fe15:8e33/64 Scope:Link      bit of privacy) ;-)
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:4293 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:4549 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:2995721 (2.8 MiB)  TX bytes:476602 (465.4 KiB)
>           Interrupt:11 Base address:0xc400
> 
> Yet, if I do the following, I cannot get past the router;
> 
> sudo ifconfig eth0 up address 192.168.1.102 netmask 255.255.255.0 
> 
> this makes this computer think it is 192.168.1.1
> 
> Any ideas?

Do you have the "zeroconf" package installed? It is known to cause this
kind of [expletive deleted]. If you uninstall it everything should come
back to normal (after "ifdown eth0" followed by "ifup eth0").

-- 
Regards,
          Florian