* (no subject)
@ 2001-11-29 15:44 Colonel
0 siblings, 0 replies; only message in thread
From: Colonel @ 2001-11-29 15:44 UTC (permalink / raw)
To: irajasek, linux-kernel
From: Colonel <klink@clouddancer.com>
To: irajasek@in.ibm.com
CC: linux-kernel@vger.kernel.org
In-reply-to: <OF8DFA00F6.3DAC22D2-ON65256B31.003CB38A@in.ibm.com>
(irajasek@in.ibm.com)
Subject: Re: Routing table problems
Reply-to: klink@clouddancer.com
In-Reply-To: <OF8DFA00F6.3DAC22D2-ON65256B31.003CB38A@in.ibm.com>
From: "Rajasekhar Inguva" <irajasek@in.ibm.com>
Date: Sat, 29 Dec 2001 17:17:48 +0530
I am facing a problem ( ???, maybe it works that way, but i really dont
know ) with regards to routing table behavior when using ifconfig on a
network interface.
1) netstat -nr Shows my default gateway for network 0.0.0.0
2) ifconfig eth0 down
3) netstat -nr No entry for the default gateway is shown (
understandable )
4) ifconfig eth0 up
After the the 4'th command, my interface is up and has it's IP address set
correctly. But .....
netstat -nr does not show my default gateway for network 0.0.0.0 !!.
Pinging any IP outside of my subnet, results in "Network is unreachable"
error.
While the linux kernel is certainly omnipotent, it's crystal ball is
sometimes hazy. How would it know what the default gateway should
be??? Typically after the interface is configured, you command:
/sbin/route add default gw $GATEWAY netmask 0.0.0.0 metric 1
Some routing daemons will handle that for you, but even they need
appropriate configuration.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-11-29 15:49 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-11-29 15:44 Colonel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®