[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Something strange with ip configuration

Paolo Pantaleo wrote:

Hi,
I have a Debian testing. I am experiencing sme problmes with ethernet
cards ip configurations. My /etc/network/interfaces file is:

### etherconf DEBCONF AREA. DO NOT EDIT THIS AREA OR INSERT TEXT BEFORE IT.
auto lo

iface lo inet loopback


### END OF DEBCONF AREA.  PLACE YOUR EDITS BELOW; THEY WILL BE PRESERVED.


iface eth1 inet static
address 172.18.255.77
netmask 255.255.255.0

iface eth0 inet static
address 172.18.3.51
netmask 255.255.255.0
gateway 172.18.3.254

auto eth0

auto eth1

but if I run ip addr I get:

1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0c:6e:91:c4:11 brd ff:ff:ff:ff:ff:ff
    inet 169.254.125.207/16 scope link eth0
    inet 172.18.3.51/24 brd 172.18.3.255 scope global eth0
    inet6 fe80::20c:6eff:fe91:c411/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0e:e8:8a:20:cd brd ff:ff:ff:ff:ff:ff
    inet 169.254.130.156/16 scope link eth1
    inet 172.18.255.77/24 brd 172.18.255.255 scope global eth1
    inet6 fe80::20e:e8ff:fe8a:20cd/64 scope link
       valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0

and ip route:
172.18.3.0/24 dev eth0  proto kernel  scope link  src 172.18.3.51
172.18.255.0/24 dev eth1  proto kernel  scope link  src 172.18.255.77
169.254.0.0/16 dev eth0  proto kernel  scope link  src 169.254.125.207
169.254.0.0/16 dev eth1  proto kernel  scope link  src 169.254.130.156
default via 172.18.3.254 dev eth0

So where the 169.* addresses can come from?


Most likely from a package called "zeroconf" which messes with the
network configuration in order to make it easy for people to configure
link-local networks. Unfortunately this package can get installed
without the user really noticing (as a recommended package). Unless you
want to use it to configure your own network you can simply uninstall
and purge it. Then your network configuration should be back to normal
after you do an ifdown/ifup on the interfaces.

Regards,
           Florian
Reply to: