Bug#3143: sysvinit init.d/network script buglet
On Tue, 28 May 1996, Miquel van Smoorenburg wrote:
> You (Bruce Perens) wrote:
> > Package: sysvinit
> >
> > From: Lukas Nellen <lukas@teorica0.ifisicacu.unam.mx>
> >
> > To me, it looks like there is a small bug in the way the networking
> > gets configured in the base system. The problem is the loopback
> > network 127.0.0.0. AFAIK, no packet addressed to any address on that
> > network should ever leave the local host. Instead, the loopback
> > interface on the local machine has to accept ALL such packets, not
> > just those sent to 127.0.0.1. Could someone confirm that or point me
> > to a document which states the contrary?
>
> Well I couldn't find it documented, but the way Debian does it now
> is the same as Solaris 2.5, SunOS 4.1.4 and FreeBSD do it (I just
> checked).
>
> So I think the "route add 127.0.0.1" is how it should be done.
I refer you to the file Documentation/Changes in recent kernel trees; it
says:
Network errors with recent kernels
==================================
Many default network scripts are set up add a route to the localhost
at 127.0.0.1 at startup. However, they do this incorrectly. To fix
the error, which is now spotted by the kernel, look for a line like
`route add -net 127.0.0.1' in your network configuration files and
change it to `route add -net 127.0.0.0'.
Steve Early
sde1000@cam.ac.uk
Reply to: