in reply to Re: Re: Ping and check for server running on port 27015
in thread Ping and check for server running on port 27015

use IO::Socket then...
Although you must be warned that ping isn't a PERFECT way to check if a server is up as some boxes are configured to ignore ICMP echo, and some routers even drop those packet...
(try pinging www.microsoft.com for example)
IMHO a tcp connect on a well known USED port (port 80 in the microsoft case...) is far better.

In brief if you use IO::Socket, Net::Ping shouldn't be necessary...

Replies are listed 'Best First'.
Re: Re: Re: Re: Ping and check for server running on port 27015
by Beatnik (Parson) on Jan 23, 2001 at 22:08 UTC
    AFAIK there is more than one way to do a Ping (mmmm sounds familiar)... Anyway, you can also use TCP Ack packets and Syn packets to "Ping" but they dont really fall under ya good ole' Ping :)

    Greetz
    Beatnik
    ... Quidquid perl dictum sit, altum viditur.
      And sending mangled/raw IP packets in this fashion is a "feature" unavailable to mortal users. You would need root or administrative privileges on the machines in question to perform this. Generally when somebody wants to "ping" another machine, it's an ICMP echo request/reply. If you want to test to see if the machine is responding to connection requests, simply try to make a connection. Sending out bare SYN packets and watching for responses is stuff you see packet kiddies doing, so you're quite likely to set off some intrusion detection systems.
        Well, I never said it was a normal way to ping :) In fact, I said "...but they dont really fall under ya good ole' Ping" :)

        Greetz
        Beatnik
        ... Quidquid perl dictum sit, altum viditur.