On Sat, 1 Feb 2003, Boris Ratner wrote: > Try doing this by the book: > 1. ping local loopback "ping 127.0.0.1" if successful > 2. ping your nic's ip address (ifconfig) if you don't have an address > (dhcp server unreachable) set one > 'ifconfig eth0 10.0.0.1 nemask 255.255.255.0' > then ping 10.0.0.1 > if both 1 and 2 worked fine the software is good. > 3. ping another box on the same subnet to make sure.
(1) and (2) are almost equivalent (if the network interface is up). A ping to any local interface will not go through that interface and loop back. (2) won't tell you anything about the machine's network settings. I dare say that it will always work (unless "eth0" doesn't exist) Anyway, the original question was (if I understand it correctly): what caused the connection to go down in the first place? A number of possible reasons: - eth10/100 conflicts (as suggested by Shahar) - inavailability of the dhcp server . Though at least isc's standard dhcp client remains active and polls the last known address of the dhcp server every once in a while in such a case. -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
