On Wed, 8 Mar 2000, Francesco wrote:
Can anyone explain why after booting (which I do frequently as use a laptop) an immediate ifconfig ensures me that eth0 is up and running yet I have to wait several minutes before I can even ping the router downstairs. More to the point how do I prevent this delay?
Depends. Someone told you to check /var/log/messages to see if there are any error messages. When checking network problems, it is always important to make sure that the problem is actually with the machine, and not with some other unit in the network. What do you get from running 'ping localhost' immediately, can the machine ping itself? Is there anything, a switch or a hub, between you and the router? Does other machines on the same network have the same problem when booting? Worth investigating before fiddling too much with the laptop. Bjorn -- Bjørn Tore Sund Phone: (+47) 555-84894 Nothing gives such Sysadmin, Mathematics dept. Fax: (+47) 555-89672 weight and dignity University of Bergen Mobile: (+47) 918 68075 to a mail as a properly system@mi.uib.no Email: bjornts@mi.uib.no formatted .signature with a good quote. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/