Hans Bieshaar wrote: > Package: network-manager-gnome > Version: 0.6.4-6 > > more likely the problem is in > Package: network-manager > Version: 0.6.4-6 > > After using tasksel to install the desktop, the file /etc/resolv.conf > was empty except for a line that said I should not edit it, and the > routing table contained no default gateway. > > The machine contains 2 ethernet cards. Only eth0 is used for a LAN > connection on a fixed IP-address because the machine is mainly used as a > server. eth1 is only in there in case I need to replace my firewall. The > file /etc/network/interfaces is: > > # 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 eth0 > iface lo inet loopback > > # The primary network interface > allow-hotplug eth0 > iface eth0 inet static > address 192.168.1.232 > netmask 255.255.255.0 > gateway 192.168.1.251 > > ifconfig reports next to eth0 and lo also 2 VMware interfaces (vmnet1 > and vmnet8). If I remember correctly ifconfig also reported eth1 when > network-manager-gnome was installed. You can imagine I removed it > immediately. >
The problem most likely is this: The first interface, eth0, has some custom configuration, so NM simply ignores that device. The second device, eth1, is not configured in /etc/network/interfaces, so NM manages that device and tries to get an IP for that interface. If you haven't connected this device, you're resolv.conf will be empty and the route not set. Either give NM control over your first device, too (by commenting out all lines regarding eth0 in /etc/network/interfaces), or disable NM for your second device. A mixed operation mode (ifupdown+NM) is not really supported by NM. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
