[Techtalk] ssh and name resolution

Patricia Fraser trish at thefrasers.org
Tue Sep 9 21:45:01 UTC 2008


Hi Maria,

> The plot thickens. So, when I came into work today, I discovered that 
> the reason that I could no longer contact this machine is that it had 
> decided that it did not want to keep the status ip that I had set in 
> /etc/network/interfaces, but instead decided to go get a dhcp ip.
> 
> Here is /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
> #allow-hotplug eth0
> #iface eth0 inet dhcp
> auto eth0
> iface eth0 inet static
>          address 10.208.108.17
>          netmask 255.255.255.0
>          gateway 10.208.108.10
>          network 10.208.108.0
>          broadcast 10.208.108.255
> 
> The syslog is filled with this stuff:
> Sep  9 06:47:15 buttercup dhclient: DHCPREQUEST on eth0 to
> 10.208.108.10 port 67
> Sep  9 06:47:15 buttercup dhclient: DHCPACK from 10.208.108.10
> Sep  9 06:47:15 buttercup dhclient: bound to 10.208.108.83 -- renewal
> in 1693 seconds.

It doesn't seem *very* likely, but on my Debian machine,
network-manager overrides /etc/network/interfaces - the cure mentioned
most often on the Debian list is to remove network-manager. Do you have
it installed/is it running?

All the best,

-- 
Trish Fraser, GWQTF RP4GD
di sep  9 22:43:19 BST 2008
GNU/Linux 1997-2007 #283226 counter.li.org
perseus up 14 hour(s), 27 min, 50 sec
kernel 2.6.24.4.tex3
--


More information about the Techtalk mailing list