lkml.org 
[lkml]   [2001]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
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
References: <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.



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:13    [W:0.024 / U:12.748 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site