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

[Kartik Thakore]

Or you can process the output of ping:

http://inetdaemon.com/tutorials/troubleshooting/tools/ping/index.html

see the link

PING response type codes

Kartik Thakore

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

>
>
> On Tue, Mar 16, 2010 at 9:53 AM, Kartik Thakore <thakore.kartik at gmail.com 
> > wrote:
> Hi Fulko,
>
> Have you tried NetPacket::ICMP? I have used this module before to  
> decode ICMP packets and get data based on their ICMP code.  
> ICMP_UNREACH is the code you want.
>
> I looked at that last night. It provides a way to decode packets, but
> my confusion lies in, how would I  (easily) get the packet to  
> decode...
> while I was in the middle of actually attempting to receive the actual
> application data.  (I will however, investigate further.)
>
> ... snip ...
>
> use Net::Pcap;
>
> ... snip ...
>
> Yes, I had thought of that, but running a packet sniffer is a 'hell  
> of an overkill'
> to determine something (that in retrospect) should have been  
> reported back
> to the application (somehow).
>
> So far, all I seem to have is an application level timeout.
>
>
> _______________________________________________
> 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/ec4db9a6/attachment.html>