Hi and TIA 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? Am using 6.2, with a later version of pcmcia (in order to get card support) Francesco -- 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/
Hi, Francesco wrote:
Hi and TIA
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?
Am using 6.2, with a later version of pcmcia (in order to get card support)
I am no network/pcmcia expert, but if I have connection problems on my dekstop system I check the system log files (e.g. /var/log/messages) to see what's going on. Hope that helps. Martijn -- 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/
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/
Hi.
At 15:22 on 8 Mar 00, Francesco begun to yabber about "[SLE] network delay"
From: Francesco
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?
When you first try to ping and are unsucsessfull.. Have a look at the stats in ifconfig and see if you are getting any input or output errors on the card.. That can give you a good idea of any problems with your physical hardware. Cya Matthew Matthew King: Network Engineer, Cable & Wireless Optus. My ICQ#: 2342475 Message me! Cellular Phone: +61 415 257 516 041 525 7516 (Inside .au) Home e-mail: nerd@zip.com.au Work e-mail: Matthew.King@cwo.net.au Homepage: http://www.zip.com.au/~nerd/ -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d+ s: a--- C++++ UL++++ P+ L+++ E---- W++ N++ o++ K w O- M- V- PS+ PE Y+ PGP- t+ 5++++ X++ R+ tv++ b+++ DI+++++ D++ G+++ e* h* r++ y+ ------END GEEK CODE BLOCK------ -- 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/
participants (4)
-
bjornts＠skolem.mi.uib.no -
fgs＠epulse.net -
Martijn.van.den.Burg＠asml.nl -
nerd＠zip.com.au