[Dxspider-support] HB9DRV-9, what is it?
Kin
ea3cv at cronux.net
Thu Mar 16 09:52:39 GMT 2023
Hi all,
* Objective data:
PC92^IW9FDD-6^36001^A^^7WW1R-6:UNKNOWN^H97^
PC92^IW9FDD-6^37801.02^A^^7PY5JO-1:UNKNOWN^H95^
PC92^DJ4PK-2^38100.02^A^^7HB9DRV-9:UNKNOWN^H93^
PC92^IW9FDD-6^69612.03^A^^5RW3XA-8:UNKNOWN^H95^
PC92^SM6YOU-2^42120.02^A^^5SM6HOC-6:UNKNOWN^H93^
IW9FDD-6 1.55 0.82 Parent: BG2RVL-9, PY1NB-4, PY5JO-11,
RW3XA-8, VE9SC, WW1R-9
DJ4PK-2 1.55 67 Parent: DD5XX-10, WA9PIE-2
SM6YOU-2 1.55 0.82 Parent: IZ0FKE, SK6AW-2, SM6HOC-6,
SM6YOU-4, SM6YOU-7
Entries between day 065 and day 075, all PC92:
HB9DRV-9 33491 5HB9DRV-9 15458 Type: A ???
7HB9DRV-9 18033
WW1R-6 16635 5WW1R-6 3672 5401 Type: A
7WW1R-6 12963
PY5JO-1 23910 5PY5JO-1 11364 5401 Type: A
7PY5JO-1 12546
RW3XA-8 136 5RW3XA-8 136 1.57 497
7RW3XA-8 0
SM6HOC-6 18 5SM6HOC-6 18 1.57 499
7SM6HOC-6 0
I have not been able to find out the differences between the 5 and the 7 in front of the callsign. If anyone knows, I would be grateful if you could share this information.
* My conclusions:
It seems that the common origin of all these PC92 sentences with 'UNKNOWN' information, lies in nodes with ARCHAIC versions.
In the specific case of HB9DRV-9, it seems that it should be WA9PIE-2, because WA9PIE-2 is really the node associated with DJ4PK-2.
* Own observations:
Keeping an outdated, misconfigured or forgotten node can lead to problems and wasted time when a problem arises in the network and we want to narrow it down.
Kin EA3CV
Our knowledge can only be finite, while our ignorance must necessarily be infinite. Karl Popper
-----Mensaje original-----
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Iain Philipps via Dxspider-support
Enviado el: miércoles, 15 de marzo de 2023 22:14
Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
CC: Iain Philipps <iain.philipps at 77hz.net>
Asunto: Re: [Dxspider-support] HB9DRV-9, what is it?
Importancia: Alta
I had a quick look at this; it appears to be a Windows Server 2016 box.
Then:
[root at courier ~]# nslookup spider.ham-radio.ch
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: spider.ham-radio.ch
Address: 81.174.138.141
[root at courier ~]# nslookup blackbeauty.sdr-radio.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: blackbeauty.sdr-radio.com
Address: 81.174.138.141
... and of course, telnet blackbeauty.sdr-radio.com 8000 will get you the Spider login prompt (no surprise).
I recall listening to GD4ELI (as he then was) in the evenings 45 years ago on either 40 or 80M (when I lived in London). Simon was (is?) clearly barking mad but one of the good guys :-)
He's not doing this on purpose; most likely the VM is running in a dark corner of that server and it has been long since forgotten.
Ian says it is "dead"; let's just lock it out and move on. Please?
73 de WR3D
-----Original Message-----
From: Dxspider-support <dxspider-support-bounces at tobit.co.uk> On Behalf Of Mikel EA2CW via Dxspider-support
Sent: 15 March 2023 19:13
To: Kin EA3CV via Dxspider-support <dxspider-support at tobit.co.uk>
Cc: Mikel EA2CW <ea2cw at gautxori.com>
Subject: Re: [Dxspider-support] HB9DRV-9, what is it?
Agreed, Kin, but there are more strange things in relation to this...
Yesterday I browsed to http://www.hamcluster.net/Map.aspx and searched for HB9DRV-9. The page shown me on the map this data:
HB9DRV-9
spider.ham-radio.ch 8000
Uptime: 32d 18h
Links: 6
DXSpider V 1.57 build 511
Well, all ok up to this time, .CH is the TLD for Switzerland. So, then I browsed to http://wwww.ham-radio.ch and there I found this:
www.ham-radio.ch
By HB9DRV
www.ham-radio.ch and www.hb9drv.ch are registered to:
Simon Brown (HB9DRV)
Postfach xxx
xxxxx xxxx
Switzerland
simon at hb9drv.ch
+41 (0)xxxxxxxxxx
Well, all ok again, so the last step was to connect to the node using
telnet:
telnet spider.ham-radio.ch 8000. The node was up, and the answer was:
This is the G4ELI-9 DX-Cluster system using DXSpider software If you are getting echo and you don't want it, do: unset/echo or (if you are a Microsoft telnet user) disable 'local echoing'.
+---------------------------------------------------------------------+
! This system may only be accessed by Radio Amateurs using their real !
! callsigns and in accordance with their jurisdiction's licensing !
! conditions. All connections to this system are recorded. !
+---------------------------------------------------------------------+
login:
You said HB9DRV-9 was answered by a node named after a US callsign.
Now you have another address to a "route" being answered by an UK callsign.
I don't understand what is going on, and yes, by the moment I will block that node.
73, Mikel
El 15/03/2023 a las 16:16, Kin EA3CV via Dxspider-support escribió:
> Mikel,
>
> My interpretation for the captured traces is simple: either someone is
> usurping the callsign or some modification has been made that leads to
> the data that I already showed.
> In the absence of more information, I think it should be marked as
> set/badnode HB9DRV-9 until it's clear what's going on, but only if
> you're concerned about network stability.
>
> Kin EA3CV
--
ea2cw at gautxori.com
Bilbao, Bizkaia. IN83MG
http://radio.gautxori.com
http://qrz.com/db/ea2cw
https://t.me/EA2CW
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
More information about the Dxspider-support
mailing list