What's new

Detect and log network connection drops

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

SLS

New Around Here
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.
 
The conventional solution for wired is managed switches and a syslog server. Someone reports a drop, you review logs and confirm.
Wireless is tricky. The closest you get to a wired interface event is association/disassociation events, but those only work when the AP can hear the disassociation frames, which isn't a given. Also doesn't address poor signal scenarios. For wireless, you may be headed down the wrong path--you can spend a lot of effort cobbling together a monitoring solution that doesn't quite do what you want, or you can spend that effort actually fixing the problem.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top