Re: 30 second delay before ping command will succeed
- From: "Skymaster" <michael@xxxxxxxxxxxxx>
- Date: 30 Dec 2006 15:31:08 -0800
It is an important feature of our application to dynamically
connect/disconnect from various networks.
I would think so. It sounds like SpanningTree (STP) at work.
Does anyone have any ideas on how to troubeshoot/eliminate this 30
second delay?
Why would you want to do this? 30sec. is acceptable in keeping the
network safe.
If you turn on the PortFast feature on the ports, STP is still active,
but the switch's port will be accessible instantly. This is what you
want on all ports not connected to layer-2 devices
(switches/hubs/bridges). If, for some reason, a loop is created, STP
will pick this up very quickly, although there is the second or two of
a potential broadcast storm.
I think in the case that the OP is talking about, the need to quickly
connect and disconnect from networks outweighs the need for the
30second check. Non-Portfast ports on a switch can also negatively
impact DHCP when a computer is first powered up, if it is very quick in
booting, or requires to be network booted, in which case the system may
fall back to a disk, a potential security risk dependant on the
configuration.
.
- References:
- 30 second delay before ping command will succeed
- From: airish
- Re: 30 second delay before ping command will succeed
- From: Robert
- 30 second delay before ping command will succeed
- Prev by Date: Re: One computer only on home net having DNS lookup trouble
- Next by Date: Re: bind problem
- Previous by thread: Re: 30 second delay before ping command will succeed
- Next by thread: Why is pktgen v1.3 causing an error message like this? (See message body)
- Index(es):
Relevant Pages
|
