Fedora 4 Routing table question

[Craig White]

On Wed, 2006-03-08 at 10:33 -0500, John Warner wrote:
> > Date: Wed, 08 Mar 2006 13:52:00 +0000
> > From: Paul Howarth <paul at city-fan.org>
> > Subject: Re: Fedora 4 Routing table question
> > To: For users of Fedora Core releases <fedora-list at redhat.com>
> > Message-ID: <440EE180.3090203 at city-fan.org>
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > 
> > John Warner wrote:
> > > Total newb' here, I have a routing issue on my Fedora 4 
> > box. I can see
> > > (read ping etc) IPs on my LAN. I cannot ping off the LAN. 
> > The gateway
> > > for eth0 is listed as 192.168.1.1 (which is correct, that 
> > is the address
> > > of my Linksys DD-WRT router to the DSL Modem). The rest of 
> > the LAN is
> > > properly configured and can see the Internet etc just fine. 
> > I read the
> > > Man Page for route and it does not really help me. I 
> > suspect my issue is
> > > my default setting on my routing table. Less the specific 
> > answer (how
> > > will I ever learn) can some one point me to the complete 
> > idiots guide to
> > > setting up his routing table in Linux. Ideally it would be 
> > oriented to
> > > the home networker.
> > 
> > http://www.brennan.id.au/
> > 
> > What's your routing table look like?
> > 
> > # netstat -rn
> > 
> > What's your interface config?
> > 
> > # ifconfig -a
> > 
> > Paul.
> > 
> > P.S. The gateway is really a property of the system, not of eth0.
> 
> > Date: Wed, 8 Mar 2006 14:01:24 +0000
> > From: Stuart Sears <stuart at sjsears.com>
> > Subject: Re: Fedora 4 Routing table question
> > To: For users of Fedora Core releases <fedora-list at redhat.com>
> > Message-ID: <200603081401.29031.stuart at sjsears.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> > 
> > On Wednesday 08 March 2006 13:46, John Warner decided we 
> > wanted to hear the 
> > following:
> 
> ...
> 
> > as root:
> > ip route show (or route -n)
> > will tell you what your current routing table says.
> > You may already know that.
> > [root at lanky ~]# ip route show
> > 192.168.22.0/24 dev eth0  proto kernel  scope link  src 192.168.22.220
> > 192.168.0.0/24 via 192.168.22.170 dev eth0
> > 169.254.0.0/16 dev eth0  scope link
> > default via 192.168.22.254 dev eth0
> > 
> > that 'default' line is important.
> > 
> > are you saying that you can ping 192.168.1.X but nothing else?
> > that would suggest two possibilities to me:
> > 1) you have no default gateway
> > solution: 
> > system-config-network [Applications -> System Settings -> Networking]
> > double-click on the eth0 entry, and
> > make sure you default gw is correct.
> > 
> > 2) no NAT rules in place between you and the outside world
> > solution: configure your router.
> > 
> > HTH
> > 
> > Stuart
> 
> Ok, maybe it isn't my routing table.
> Netstat -r returns -I left off col heads.
> 
> 192.168.1.0   *   255.255.255.0   U  0  0  0  eth0
> 169.254.0.0   *   255.255.0.0       U  0  0  0  eth0
> default           192.168.1.1 0.0.0.0 UG  0 0 0 eth0 
> 
> In the gui for eth0 the Gateway entry is 192.168.1.1 which is correct.
> I don't seem to have a loop back entry.
> 
> Also if this helps, I am on a Static IP in my LAN at 192.168.1.51
> 
> As to my router, it passes traffic from a couple of Windoze boxes to the
> Internet just fine; you're reading this email <grin/>. The Win boxes can
> ping the Linux box and the Linux box can ping the windows boxes. What it
> cannot do is ping an IP off the LAN nor say  a name www.yahoo.com.  I
> don't think this is a DNS issue yet as like I said I can't ping IPs off
> the LAN.
> 
> What am I missing here?
----
not sure that you are missing anything

what is output of ifconfig?

you should see lo (loopback adaptor) there

you can add dns server addresses to /etc/resolv.conf if you want dns
resolution...for example

# cat /etc/resolv.conf
nameserver 192.168.2.1
nameserver 68.2.16.30
search localdomain

you should be working just fine...

you might want to make sure that firewall isn't a problem by temporarily
turning it off...

/sbin/service iptables stop

(/sbin/service iptables start # turns it back on)

Craig