If there's no default route listed when you issue the command
route -n, then you won't be able to ping out. If you type route you
should get 4 entries (that's what I get on all the default install
boxes i have):
Dest Gate Mask Flags Int
192.168.1.2 0.0.0.0 255.255.255.255 UH Eth0
192.168.1.0 0.0.0.0 255.255.255.0 U Eth0
127.0.0.1 0.0.0.0 255.0.0.0 U lo
0.0.0.0 192.168.1.1 0.0.0.0 UG Eth0
Where 192.168.1.2 would be the linux box and 192.168.1.1 is the
router. If these aren't in there it could explain why you can't ping
out but do receive pings (it can't find any a route to the address
to ping, but the windoze box has it's own routing table and can find
the linux box). Of course you may have links to multiple networks
and other things so it could look different. But the point is, to
get to the internet you need the default route and to ping other
machines on the subnet you need the 192.168.1.0 entry.
-----Original Message-----
From: John Aldrich [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 31, 2000 10:43 AM
To: [EMAIL PROTECTED]
Subject: Help! Network stopped working!
My linux box at home is a dual-PPro motherboard (only uni-processor
right now -- 2nd CPU died) with a built-in 10/100 Intel EtherExpress
NIC.
For some reason it has stopped seeing the network. My *guess* since
I
can ping the box from another machine is that somehow it got set to
100 Megabit-only from 10/100 (only have 10 Mbit network.)
The other wierdness is that it doesn't show a default gateway when I
type "route" at the command line. However, my linux box here at work
DOES show the default route. When I open up netcfg or linuxconf, it
shows the default route just fine.
any ideas???
Thanks...
--
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
