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

Re: interfaces file failes to set gateway



David Liontooth wrote:
> This is my /etc/network/interfaces:
> 
> # The primary network interface
> auto eth0
> iface eth0 inet static
>         address 192.168.0.26
>         netmask 255.255.255.0
>         network 192.168.0.0
>         broadcast 192.168.0.255
>         gateway 192.168.0.178

First, it would be good to remove the network and broadcast lines.
They are redundant information.  It used to be that the
debian-installer would create those as examples.  But those examples
have been removed and the d-i no longer creates those.  Recently there
has been a push to clean these up so that they are no longer
distributing such examples.  Here is a reference:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630551

Second, it would be good to update to the modern event driven style
replacing "auto eth0" with "allow-hotplug eth0" instead.  Or keep
"auto" and also add "allow-hotplug eth0" too.  That is supported.  The
presence of "auto" allows '/etc/init.d/networking restart' to work.
The presence of "allow-hotplug" allows it to be started and stopped
based upon it being detected by the kernel is an the modern code path
for all new systems.  These days it is probably the much better tested
of the two since the older way is deprecated.  I expect you are seeing
the deprecation warnings.

allow-hotplug eth0
iface eth0 inet static
        address 192.168.0.26
        netmask 255.255.255.0
        gateway 192.168.0.178

The format and contents of the file are documented here:

  http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_network_interface_with_the_static_ip

I don't think either of those two things will affect the problem you
are seeing.  But they would both be good changes to make to update to
the current standards before trying to debug further.

> I cloned this entire operating system, which as you see is on a
> private subnet, to another box that is on a public network, and got
> exactly the same problem (with a different gateway). I have other
> machines on the same networks with the same configuration that don't
> have this problem. What could be preventing the default gateway from
> being set on boot?

This information leads me to believe that it is probably not in the
interfaces file.  The file looks okay to me (other than my comments
above) and therefore the problem is probably elsewhere.  The most
likely suspects would be one of the files in the /etc/network/*.d/*
directory.

  ls /etc/network/*.d/

Look through those files and see if any of those might be causing this
problem.  They would have been cloned with the other machine and that
also leads me to think the problem might be there.

Have you looked at the /var/log/syslog file and/or dmesg output to see
if there are any messages related to network setup that might be
clues?

Good luck!
Bob

Attachment: signature.asc
Description: Digital signature


Reply to: