Re: new bootdisks uploaded
On Tue, 2 Mar 1999 Dinh-Tuan.Pham@imag.fr wrote:
> > No, it isn't. With the 2.2.x kernels there's no need to add a route anymore.
> > The kernel adds it automagically. If you are sure that you'll stay with the
> > 2.2.x kernels you can comment out the 'route' commands in /etc/init.d/network
> > after installation.
> >
> > If you leave the route commands alone it won't hurt. You'll only notice them
> > at bootup when you get the error messages otherwise it works fine.
>
> Thank for this possst. I have tried to find out what is wrong with
> this message (which I got both from my linux intel as well as on a
> sparc) for a while and have posted the question to various newsgropu
> without getting an answer.
>
> But I still have a question: how do the kernel find out the gateway 's
> address (could it find out by itself ?). In the /etc/networks (of
> debian-slink) I have
>
> ifconfig lo 127.0.0.1
> route add -net 127.0.0.0
> IPADDR=129.88.33.95
> NETMASK=255.255.255.0
> NETWORK=129.88.33.0
> BROADCAST=129.88.33.255
> GATEWAY=129.88.33.253
> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
> route add -net ${NETWORK}
> [ "${GATEWAY}" ] && route add default gw ${GATEWAY} metric 1
>
> The GATEWAY adressed have been entered at installation time. If the
> route add command is rejected by the kernel, how do it knows this
> address. (especialy in this case where this adress is not
> 129.88.33.254 as often is but 129.88.33.253)
>
It's only the route for the local network that the kernel itself sets
up, all other routes (such as the default route) still has to be set up
manually.
/Ajje
Remember, down, not across!
Reply to: