Bug#3130: sysvinit init.d/network script buglet
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?
However, in the configuration that was shipped at least with the disks
dated end of April, 127.x.y.z, except 127.0.0.1, is sent to the
default gateway.
The way out it to add the line
route add -net 127.0.0.0
or
route add -net 127.0.0.0 dev lo
after the line
route add 127.0.0.1
in /etc/init.d/network.
BTW, it seems to be sufficient to have only
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
in /etc/init.d/network to configure the loopback interface. However,
I'm not sure if that just happens to work by chance. Could someone who
knows the documented requirements of the interface and routing setup
in linux provide an `offical and stable' setup? I don't want to
suggest something that might break when the networking code in the
kernel changes.
Cheers,
Lukas
-------------------------------------------------------------------------------
Dr. Lukas Nellen | Email: lukas@teorica0.ifisicacu.unam.mx
Depto. de Fisica Teorica, IFUNAM |
Apdo. Postal 20-364 | Tel.: +52 5 622 5014 ext. 218
01000 Mexico D.F., MEXICO | Fax: +52 5 622 5015
--
*** Re-elect Clinton ***
Bruce Perens Bruce@Pixar.com http://www.hams.com/
Reply to: