[Dxspider-support] Ping

[Tim Tuck]

Hi Kin,

OK - then if you want to keep an eye on the app then there a couple of 
ways to do that.

One of my personal favourites is to implement SmokePing. You could 
create a dxspider specific probe using it.

https://oss.oetiker.ch/smokeping/

It allows complex probes to be created to keep an eye on hosts and apps 
and make nice graphs around the returned results.


Or for just doing quick port checks you can use netcat thus...

*nc -vz host port*

This will at least let you know that the destination app port is open 
and listening with results like...

*Connection to host (IP_address) 7300 port [tcp/*] succeeded!*

And you could always wrap nc in a shell script to do a 100 "pings" or 
whatever.

cheers

Tim

On 25/8/24 20:11, Kin wrote:
> Hi Tim,
>
> Good explanation of ICMP ping. What I was asking about was ping at the application layer.
> Conventional ping -as you know- only tells me if the host is accessible, but not if the DXSpider application is UP and responding.
> What I am trying to do is use the internal spider command, also called ping, to see the status of the destination node. Obviously from the spider application itself. Here the node callsign (application level) is used.
>
> I liked your explanation of ping, a widely used tool that complements others, especially for those of us who have been working in networks and systems.
>
> I appreciate your answer.
>
-- 
VK2XAX : QF68KM : ITU59 : CQ30 : ORARC : WIA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240828/14c4e513/attachment.htm>