[Dxspider-support] DO5SSB-2 and DB0SUE-7 (long story)

Kin ea3cv at cronux.net
Mon Feb 3 07:18:24 GMT 2025


Hi Gregor,


Once we have clarified what happened with DB0SUE-7 and DO5SSB-2, we could
try to investigate what has been occurring recently and find a solution.

The reason why I reported your IP as a "badip" comes from the following:
If we carefully examine the spots that were apparently generated on
DO5SSB-2, we can see a set of IPs that repeatedly appear as the spotters'
IPs:

201.67.123.106
191.39.7.110
82.149.227.228
98.98.148.135
77.22.208.103

Among them is the IP that appears to belong to your host/node:

1738457360^(chan) <- I EA4URE-5 PC61^28074.0^JH5HDA^ 2-Feb-2025^0049Z^FT8 -3
dB 1936 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738457772^(chan) <- I EA4URE-5 PC61^28074.0^JE1COB^ 2-Feb-2025^0056Z^FT8
-16 dB 982 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738457874^(chan) <- I EA4URE-5 PC61^7090.0^8R1TM^ 2-Feb-2025^0057Z^FT8 -15
dB 1014 Hz^PY3LX^DO5SSB-2^191.39.7.110^H1^~
1738459123^(chan) <- I EA4URE-5 PC61^5358.3^EA4DUT^ 2-Feb-2025^0118Z^FT8 +04
Thx for qso 73^F4BJN^DO5SSB-2^82.149.227.228^H1^~
1738460183^(chan) <- I EA4URE-5 PC61^28074.0^JA2BMW^ 2-Feb-2025^0136Z^FT8 +3
dB 1378 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738460189^(chan) <- I EA4URE-5 PC61^28074.0^JF2FBN^ 2-Feb-2025^0136Z^FT8 -8
dB 2236 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738460680^(chan) <- I EA4URE-5 PC61^28074.0^JI1HFJ^ 2-Feb-2025^0144Z^FT8 -8
dB 2235 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738460720^(chan) <- I EA4URE-5 PC61^28074.0^JF2WXS^ 2-Feb-2025^0145Z^FT8 +8
dB 223 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738460937^(chan) <- I EA4URE-5 PC61^28074.0^JM1SZY^ 2-Feb-2025^0148Z^FT8 +9
dB 2361 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738461355^(chan) <- I EA4URE-5 PC61^28074.0^JK7IKJ^ 2-Feb-2025^0155Z^FT8
-16 dB 1838 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738493108^(chan) <- I EA4URE-5 PC61^144174.0^9A4P^ 2-Feb-2025^1045Z^<TR>
FT8 +4 dB 2264 Hz FB SIG^IC8FAX^DO5SSB-2^98.98.148.135^H1^~
1738493251^(chan) <- I EA4URE-5 PC61^14074.7^HB9HIL^ 2-Feb-2025^1047Z^FT8
-13 Thx for qso 73^F4BJN^DO5SSB-2^82.149.227.228^H1^~
1738493501^(chan) <- I EA4URE-5 PC61^28469.9^CT7AQF^ 2-Feb-2025^1051Z^
^DL9ZAL^DO5SSB-2^188.100.29.150^H1^~
1738493765^(chan) <- I EA4URE-5 PC61^7022.0^9A3VM^
2-Feb-2025^1056Z^CW^DM5UE^DO5SSB-2^77.22.208.103^H1^~
1738494369^(chan) <- I EA4URE-5 PC61^7015.7^S52AW^
2-Feb-2025^1106Z^CW^DM5UE^DO5SSB-2^77.22.208.103^H1^~
1738494534^(chan) <- I EA4URE-5 PC61^7026.0^DJ3CQ^
2-Feb-2025^1108Z^CW^DM5UE^DO5SSB-2^77.22.208.103^H1^~
1738494691^(chan) <- I EA4URE-5 PC61^7011.6^HA7A^
2-Feb-2025^1111Z^CW^DM5UE^DO5SSB-2^77.22.208.103^H1^~
1738538701^(chan) <- I EA4URE-5 PC61^28395.0^PY2EU^ 2-Feb-2025^2325Z^55 into
JA.^7L4LKK^DO5SSB-2^82.149.227.228^H1^~
1738538794^(chan) <- I EA4URE-5 PC61^28180.0^AI6US^ 2-Feb-2025^2326Z^FT4 -2
dB 1088 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738538900^(chan) <- I EA4URE-5 PC61^28180.0^JH3QFY^ 2-Feb-2025^2328Z^FT4 -5
dB 2392 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738539002^(chan) <- I EA4URE-5 PC61^28180.0^W9LNQ^ 2-Feb-2025^2330Z^FT4 -11
dB 1669 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738539098^(chan) <- I EA4URE-5 PC61^28180.0^AH6U^ 2-Feb-2025^2331Z^FT4 -16
dB 792 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738539380^(chan) <- I EA4URE-5 PC61^28395.0^K7PN^ 2-Feb-2025^2336Z^59 into
JA.^7L4LKK^DO5SSB-2^82.149.227.228^H1^~
1738539449^(chan) <- I EA4URE-5 PC61^28180.0^NT4J^ 2-Feb-2025^2337Z^FT4 -7
dB 1491 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738539454^(chan) <- I EA4URE-5 PC61^28180.0^N7XR^ 2-Feb-2025^2337Z^FT4 -8
dB 2086 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738539933^(chan) <- I EA4URE-5 PC61^28180.0^KB8SRX^ 2-Feb-2025^2345Z^FT4 -1
dB 1940 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738539984^(chan) <- I EA4URE-5 PC61^28180.0^AA0N^ 2-Feb-2025^2346Z^FT4 -4
dB 2194 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738540104^(chan) <- I EA4URE-5 PC61^28395.0^N6PSN^ 2-Feb-2025^2348Z^59 into
JA.^7L4LKK^DO5SSB-2^82.149.227.228^H1^~
1738540190^(chan) <- I EA4URE-5 PC61^28180.0^NY6DX^ 2-Feb-2025^2349Z^FT4 -4
dB 1457 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738540278^(chan) <- I EA4URE-5 PC61^28180.0^JG2DZM^ 2-Feb-2025^2351Z^FT4 -9
dB 2553 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738540281^(chan) <- I EA4URE-5 PC61^28475.0^KF0OUQ^ 2-Feb-2025^2351Z^5-57
in HI-4^KC3MYU^DO5SSB-2^82.149.227.228^H1^~
1738540282^(chan) <- I EA4URE-5 PC61^28180.0^JA1QML^ 2-Feb-2025^2351Z^FT4
-12 dB 2315 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738540287^(chan) <- I EA4URE-5 PC61^28180.0^JA0EME^ 2-Feb-2025^2351Z^FT4 +1
dB 866 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738540367^(chan) <- I EA4URE-5 PC61^28395.0^VE7XFA^ 2-Feb-2025^2352Z^55
into JA.^7L4LKK^DO5SSB-2^82.149.227.228^H1^~
1738540385^(chan) <- I EA4URE-5 PC61^28180.0^AA5AT^ 2-Feb-2025^2353Z^FT4 +0
dB 2193 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738540520^(chan) <- I EA4URE-5 PC61^28180.0^JH2LMH^ 2-Feb-2025^2355Z^FT4
-10 dB 1586 Hz^PT9MD^DO5SSB-2^201.67.123.106^H1^~
1738540666^(chan) <- I EA4URE-5 PC61^28395.0^PU5LPZ^ 2-Feb-2025^2357Z^52
into JA.^7L4LKK^DO5SSB-2^82.149.227.228^H1^~

But this does not seem to be correct. Since your node is running Mojo 562,
it is expected that the IP accompanying a spot is not that of your node but
rather that of the spotter.
Moreover, it is very unusual for you to have multiple IPs, as your partners
always indicate that you have the same IP.

1738451940^(chan) <- I EA4URE-5
PC92^ON4KST-2^83940.02^A^^5DO5SSB-2:82.149.227.228^H97^
1738451940^(chan) <- I EA4URE-5
PC92^IU1BOW-2^83940^A^^5DO5SSB-2:82.149.227.228^H94^
1738451940^(chan) <- I EA4URE-5
PC92^SK3W-6^83940^A^^5DO5SSB-2:82.149.227.228^H94^
1738451940^(chan) <- I EA4URE-5
PC92^SK3W-6^83940.02^A^^5DO5SSB-2:82.149.227.228^H94^
1738451940^(chan) <- I EA4URE-5
PC92^SR4DXC^83940.02^A^^5DO5SSB-2:82.149.227.228^H96^
1738451940^(chan) <- I EA4URE-5
PC92^OK2CQR-1^83940^A^^5DO5SSB-2:82.149.227.228^H94^
1738451940^(chan) <- I EA4URE-5
PC92^IQ8DO-6^83940^A^^5DO5SSB-2:82.149.227.228^H94^
1738451940^(chan) <- I EA4URE-5
PC92^KB5VJY-3^83940.02^A^^5DO5SSB-2:82.149.227.228^H94^
1738451940^(chan) <- I EA4URE-5
PC92^PE1ITR-8^83940.02^A^^5DO5SSB-2:82.149.227.228^H94^
1738451940^(chan) <- I EA4URE-5
PC92^IQ8PQ-6^83937.02^A^^5DO5SSB-2:82.149.227.228^H95^
1738451940^(chan) <- I EA4URE-5
PC92^IQ8RB-6^83937.02^A^^5DO5SSB-2:82.149.227.228^H95^
1738451940^(chan) <- I EA4URE-5
PC92^W6RFU^83940.02^A^^5DO5SSB-2:82.149.227.228^H96^
1738451940^(chan) <- I EA4URE-5
PC92^F6BVP-3^83940^A^^5DO5SSB-2:82.149.227.228^H94^

Something is not working as it should, or the code may have been modified,
in my opinion.

Here is a real example of how a node from the Mojo branch is expected to
behave:

1738502325^(chan) <- I EA4URE-5 PC61^28485.0^FY5KE^ 2-Feb-2025^1318Z^5/9
73^EA7BEI^WA9PIE-2^85.60.99.203^H1^~
1738502332^(chan) <- I EA4URE-5 PC61^7075.3^JR5DFW^ 2-Feb-2025^1318Z^CP5H
Vertical,80W^AI6GM-1^WA9PIE-2^76.102.108.94^H1^~
1738502821^(chan) <- I EA4URE-5 PC61^28498.0^W1NVT^02-Feb-2025^1327Z^
^SV2KBO-2^WA9PIE-2^85.72.57.193^H1^~
1738503098^(chan) <- I EA4URE-5 PC61^28430.0^M0ZNK^ 2-Feb-2025^1331Z^
^N2JF-15^WA9PIE-2^47.7.177.23^H1^~
1738503164^(chan) <- I EA4URE-5 PC61^28565.0^W8HB^ 2-Feb-2025^1332Z^
^SV2KBO-2^WA9PIE-2^85.72.57.193^H1^~
1738503183^(chan) <- I EA4URE-5 PC61^28380.0^W2RE^ 2-Feb-2025^1333Z^
^KE2AY-4^WA9PIE-2^68.129.133.234^H1^~
1738503375^(chan) <- I EA4URE-5 PC61^14195.0^W4RN^ 2-Feb-2025^1336Z^
^KK4WP-1^WA9PIE-2^47.205.82.67^H1^~
1738503588^(chan) <- I EA4URE-5 PC61^28380.0^W2RE^ 2-Feb-2025^1339Z^
^G0WCK^WA9PIE-2^92.236.156.156^H1^~
1738504016^(chan) <- I EA4URE-5 PC61^7075.1^JP1LRT^ 2-Feb-2025^1346Z^CP5H
Vertical,80W^AI6GM-1^WA9PIE-2^76.102.108.94^H1^~

WA9PIE-2, for example, displays the IP associated with the callsign of the
spot originator. This is the expected and desired behaviour.

You will understand why your IP was flagged as a bad IP. This is not normal
behaviour for the spider.

Regards,

Kin EA3CV


-----Mensaje original-----
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de
Gregor Surmann via Dxspider-support
Enviado el: lunes, 3 de febrero de 2025 2:44
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: Gregor Surmann <gs at funil.de>
Asunto: [Dxspider-support] DO5SSB-2 and DB0SUE-7 (long story)

Hello guys!

First of all, I would like to apologize if I caused any confusion or
Problems. That was never my intention.

Over 2 years ago, I set up a DXSpider node to participate in the DX cluster.

For a long time, it ran without any significant traffic, it was actually
just for me.

Some time ago, I also tried to get on this mailing list, but unfortunately
without success. Now I'm here.

My own call sign is DO5SSB, the node has DO5SSB-2. When I found out from
Kalle, DK2ZZ, that DB0SUE-7's server was broken and he couldn't continue to
operate it, I wrote to him to take it over. Unfortunately, no response.

Then, a few months later, I saw the domain "db0sue.de" for sale, which I
bought for $100 to continue his work with honor. I "unfortunately" used the
call sign DB0SUE-7 without knowing that it leads to such problems in the
DXSpider software.

The operator of SR4DXC (my first link) pointed out to me that there are
problems and that they are being discussed here.

After I got on the list here, I followed the emails and blocked nodes that
connect to "db0sue.de". So for several weeks there should have been no
traffic with this DB0SUE-7 call sign.

I run the cluster myself because I work in a data center and have the
necessary resources and enough redundancy to keep it running.

The traffic that comes from the IP 82.149.227.228 (mine) is valid and does
not have to be set as "bad IP".

The call sign "DO5SSB-2" is also valid and belongs to me, as you can see on
the BNetzA website.

So again, I'm sorry for causing so much confusion and problems, it wasn't my
intention. I just wanted to keep the DX cluster alive, as the old DB0SUE-7
node was on the net for a long time and reliably.

Regarding the comment that I have so many links, yes, they are also set up
correctly and I use my own call sign correctly. So it's not a problem, I
think.

In my opinion, everything should now run smoothly and I'm happy to be able
to give my part back to the Ham Radio community.

Hope for good teamwork in the future!

BTW. I created a replacement for the SHOW/CONTEST function, but I will write
about that in another mail.

73 de Gregor, DO5SSB

_______________________________________________
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