Net::Ping kind of sucks - see all the posts on this site about it.

I would suggest using the system ping command and parse the results. Something like (on my slack box):
my @res = `ping -c 3 $ip`; if (pop @res =~ /(\d+\.\d+)\/(\d+\.\d+)\/(\d+\.\d+)) { my @sorted = sort ($1,$2,$3); print pop @sorted }
Update: just for kicks, here's the above golfed down a bit :-)
print(((sort(((`ping -c3 $ip`)[-1])=~/(\d+\.\d+)\/(\d+\.\d+)\/(\d+\.\d ++)/))[-1]) )
Also - regarding your question re: multiple OS's. That's the problem with non-modular code. Anyways, what I would suggest is that you set the command you will run earlier in the script depending on the os (ie $ping = "command" if $^O =~ /Solaris/ etc..

In reply to Re: Ping and Tracert by the_slycer
in thread Ping and Tracert by qball

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.