[tpm] how to detect ICMP 'port unreachable'?

Fulko Hew fulko.hew at gmail.com
Tue Mar 16 08:21:50 PDT 2010

On Tue, Mar 16, 2010 at 10:52 AM, Kartik Thakore
<thakore.kartik at gmail.com>wrote:

> Or you can process the output of ping:
> http://inetdaemon.com/tutorials/troubleshooting/tools/ping/index.html

The problem with this approach is that it too is independent of the actual
transactions that may exhibit the problem.

Ie.  If you ping the device first, that doesn't mean that you won't get
an 'unreachable' moments later during the numerous subsequent
transactions.  And to perform a ping right in front of each of those
transactions is mega-overkill.  And then finally, why do an extra ping to
tickle a response, when the actual transaction will generate the response
(Its just a matter of being able to retrieve/extract it from the system.

Its just that doing with the ping approach proabably means that you have
an 'raw' level path open, and you are doing the ICMP protocol (send)
stuff all yourself, and that enables you to do the ICMP receive too.

What I really need is a way that the application still does its high
level stuff, but also 'register a listener' for potential ICMP (low) level
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/toronto-pm/attachments/20100316/bc0818b9/attachment.html>

More information about the toronto-pm mailing list