Hi All,
How does one go about detecting a network drop/disconnect. This is not limited to wireless but also to wired connections. Usually people use it to refer to a wireless device losing a connection for a big enough period of time that they notice. The actual drop might be longer than they notice but due to bufferring it takes a while.
What I am interested in is a phys*cal drop at the network interface level.
(Phys*cal is banned word??)
Google searching usually brings up nothing better than the suggestion to ping a target or an application that does that. But a non response is not neccessarily a drop, and a ping is ICMP so what about TCP? What about length of interval of drop? What do we consider as a phys*cal drop milliseconds? longer?
How do we detect this?
Consider a network card losing connection because of a hardware issue? How do we detect this and then log it.
How does one go about detecting a network drop/disconnect. This is not limited to wireless but also to wired connections. Usually people use it to refer to a wireless device losing a connection for a big enough period of time that they notice. The actual drop might be longer than they notice but due to bufferring it takes a while.
What I am interested in is a phys*cal drop at the network interface level.
(Phys*cal is banned word??)
Google searching usually brings up nothing better than the suggestion to ping a target or an application that does that. But a non response is not neccessarily a drop, and a ping is ICMP so what about TCP? What about length of interval of drop? What do we consider as a phys*cal drop milliseconds? longer?
How do we detect this?
Consider a network card losing connection because of a hardware issue? How do we detect this and then log it.