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

Kartik Thakore thakore.kartik at gmail.com
Tue Mar 16 08:30:38 PDT 2010

To get the low kevel ICMP messages short of a packet listener you will  
need to write some c level socket, then do XS to get it in perl.

Kartik Thakore

On 2010-03-16, at 11:21 AM, Fulko Hew <fulko.hew at gmail.com> wrote:

> 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 itself!
> (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
> messages.
> _______________________________________________
> toronto-pm mailing list
> toronto-pm at pm.org
> http://mail.pm.org/mailman/listinfo/toronto-pm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/toronto-pm/attachments/20100316/f8f08953/attachment.html>

More information about the toronto-pm mailing list