Very Computer

by **Bill Unr** » Sat, 17 Apr 1999 04:00:00

Quote:>> I am having trouble getting routes to load properly at boot-up time.

>> The following route table enables my system to work fine with nslookup, ping,
>> sendmail, etc.:

>> Destination Gateway Genmask Flags Metric Ref Use Iface
>> www.alias.com * 255.255.255.255 UH 0 0 0 eth0:0
>> 206.238.176.0 * 255.255.255.0 U 0 0 3 eth0
>> 127.0.0.0 * 255.0.0.0 U 0 0 7 lo
>> default * 0.0.0.0 U 0 0 0 eth0

I do not think you want a default route to your eth0 anyway, since I
suspect that you only have a finite number of machines you can get to on
eth0 (otherwise why would you connect via ppp to the net).
So, get rid of the default entry entirely -- eg put
route del default
at the end of your rc.local file (eg /etc/rc.d/rc.local on RedHat)
Then make sure that all of your machines on eth are listed with
explicit routes.

Quote:
>> With this route table, nslookup just hangs. At this point if I type the
>> following commands, I can get my route table to display the correct
>> information: (Not necessarily correct, but one that works!)

Sorry, why are you using nslookup on a finite sized ethernet ? You
(probably) have no nameserver anyway, and it cannot get out to the net
to get names anyway.

Perhaps you need to be more specific as to your network topology and why
you use ppp as well.

by **David K. Mean** » Sat, 17 Apr 1999 04:00:00

> >> I am having trouble getting routes to load properly at boot-up time.

> >> The following route table enables my system to work fine with nslookup,
ping,
> >> sendmail, etc.:

> >> Destination Gateway Genmask Flags Metric Ref Use
Iface
> >> www.alias.com * 255.255.255.255 UH 0 0 0
eth0:0
> >> 206.238.176.0 * 255.255.255.0 U 0 0 3
eth0
> >> 127.0.0.0 * 255.0.0.0 U 0 0 7
lo
> >> default * 0.0.0.0 U 0 0 0
eth0

> I do not think you want a default route to your eth0 anyway, since I
> suspect that you only have a finite number of machines you can get to on
> eth0 (otherwise why would you connect via ppp to the net).
> So, get rid of the default entry entirely -- eg put
> route del default
> at the end of your rc.local file (eg /etc/rc.d/rc.local on RedHat)
> Then make sure that all of your machines on eth are listed with
> explicit routes.

> >> With this route table, nslookup just hangs. At this point if I type
the
> >> following commands, I can get my route table to display the correct
> >> information: (Not necessarily correct, but one that works!)

> Sorry, why are you using nslookup on a finite sized ethernet ? You
> (probably) have no nameserver anyway, and it cannot get out to the net
> to get names anyway.

> Perhaps you need to be more specific as to your network topology and why
> you use ppp as well.

You later said that this machine is on an ethernet segment that attaches
somehow
to an ISP over a T1 line. It isn't clear (yet) what device makes the
transition
from Ethernet to T1, but in any case, the correct address for your default
gateway
is the IP address of that device (if it routes), or of the `other' end of
the T1 line
(if you convert from ethernet to T1 some other way, like bridging). The
reason for
this is that your webserver needs only to know how to forward packets that
it doesn't
know how to route itself; the right address is that of another box that
(presumably)
does know how to forward the packets to the intended destination.

Very Computer

Default gateway in route table

Default gateway in route table

Default gateway in route table