On Mon, Oct 23, 2000 at 09:16:57AM -0400, Michael P. Soulier wrote:
>
> Hmm. I just looked in /etc/init.d, and there's a network script that sets
> up the loopback connection:
>
> #! /bin/sh
> ifconfig lo 127.0.0.1
> route add -net 127.0.0.0
>
> I see an entry in /etc/network/interfaces for this but it's commented out.
> So, if it's supposed to be done in /etc/network/interfaces, what's this
> network script for?
either you upgraded to potato when it was unstable or you upgraded
from slink. /etc/init.d/network is the old way of configuring the
network. it was just a flat shell script, a nice way to do it but not
easy to translate when things change. you can remove the network
script and add the following to /etc/network/interfaces:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
iface lo inet loopback
up route add -net 127.0.0.0 netmask 255.0.0.0 dev lo
down route del -net 127.0.0.0 netmask 255.0.0.0 dev lo
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.10
the route commands i have in the lo entry are not necessary under 2.2
kernels, i just have them there because i like to see that route in
the routing table and 2.2 does not create it (lo works without them
but..)
as for your previous mail, the routing is done automatically by 2.2
kernels, im not sure if ipup does the routing automatically under 2.0
kernels or not. i just know that i don't have to mess with the
routing table for eth0 on my system. (running 2.2 kernels)
--
Ethan Benson
http://www.alaska.net/~erbenson/
Attachment:
pgpXiaARQUsUc.pgp
Description: PGP signature