DXspider status information #108

Open
opened 2026-03-20 16:08:29 +00:00 by ian · 0 comments
Owner

Request from S50U:

A few years ago I worked on a similar web interface for DXSpider. It might make sense to add a feature to the server version—perhaps under "Status"—that lists all current users and nodes on our "Spot Provider" Node. I'm attaching a piece of code that a "Spot provider" could use or implement and which could be enabled as needed. DXSpider commands in use are SH/VERSION and WHO.

In the DXSpider version 560 onwards the 'WHO' command has been slightly modified. The 'State' field has been added to allow sysops to diagnose some connection initialisation problems. Also the 'Type' field label has been changed for partner nodes running CCuster software to the 'NODE CCCL'. I have added some examples where I replaced IP's with xxxx within 'Link' field for security reasons only. The output table will need to be reorganised.

  Callsign Type      State    Started           Name     Ave RTT Link
    S50CLX NODE DXSP indiffer 31-Jan-2025 0539Z Palk
  GB7TLH-2 NODE DXSP normal   31-Jan-2025 0539Z             0.07 xxx.xx.xx.xxx
      S50U USER EXT  prompt   31-Jan-2025 1023Z Dan              xx.xx.xx.xxx
  ON0DXK-5 NODE CCCL normal   31-Jan-2025 0543Z Node        0.08 xxx.xxx.xxx.xxx

Maybe you could also parsing the DXSpider version like DXSpider v1.57 build 560 under users & nodes online line with the SH/VERSION command:

DXSpider v1.57 (build 560 git: mojo/d10e1590[r]) using perl v5.34.0 on Linux
Copyright (c) 1998-2025 Dirk Koopman G1TLH

Here is my work done. Find the corrected scripts in the zip file.

  • added SW: DXSpider version
  • added Rbn skimmers feed count
  • added last update date and time
  • output Users & Nodes table reorganised
  • skiping telnet_user callsign from the table
Request from S50U: > A few years ago I worked on a similar web interface for DXSpider. It might make sense to add a feature to the server version—perhaps under "Status"—that lists all current users and nodes on our "Spot Provider" Node. I'm attaching a piece of code that a "Spot provider" could use or implement and which could be enabled as needed. DXSpider commands in use are SH/VERSION and WHO. > In the DXSpider version 560 onwards the 'WHO' command has been slightly modified. The **'State'** field has been added to allow sysops to diagnose some connection initialisation problems. Also the **'Type'** field label has been changed for partner nodes running CCuster software to the **'NODE CCCL'**. I have added some examples where I replaced IP's with xxxx within **'Link'** field for security reasons only. The output table will need to be reorganised. ``` Callsign Type State Started Name Ave RTT Link S50CLX NODE DXSP indiffer 31-Jan-2025 0539Z Palk GB7TLH-2 NODE DXSP normal 31-Jan-2025 0539Z 0.07 xxx.xx.xx.xxx S50U USER EXT prompt 31-Jan-2025 1023Z Dan xx.xx.xx.xxx ON0DXK-5 NODE CCCL normal 31-Jan-2025 0543Z Node 0.08 xxx.xxx.xxx.xxx ``` > Maybe you could also parsing the DXSpider version like **DXSpider v1.57 build 560** under users & nodes online line with the **SH/VERSION** command: ``` DXSpider v1.57 (build 560 git: mojo/d10e1590[r]) using perl v5.34.0 on Linux Copyright (c) 1998-2025 Dirk Koopman G1TLH ``` Here is my work done. Find the corrected scripts in the zip file. - added SW: DXSpider version - added Rbn skimmers feed count - added last update date and time - output Users & Nodes table reorganised - skiping telnet_user callsign from the table
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ian/spothole#108
No description provided.