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

[Gregor Surmann]

On 03.02.25 08:18, Kin wrote:
> 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:
> 
> [...]
> 
> 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.

I use the Mojo 562, always up2date, no changes to code. Vanilla unchanged.
But, perhaps this may come from mixing listener and xinetd usage. But for 
some things I need the xinetd.

> Moreover, it is very unusual for you to have multiple IPs, as your partners
> always indicate that you have the same IP.

I don't have multiple IPs on this VM, only 1x IPv4 and 1x IPv6 (not used yet).


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

No, always "git reset --hard" and "git pull", branch is "mojo".

sysop at dxspider:/spider$ git status
On branch mojo
Your branch is up to date with 'origin/mojo'.

nothing to commit, working tree clean
sysop at dxspider:/spider$ git reset --hard
HEAD is now at 691ed8f6 fix dx,ann cmds, add state to who cmd


> 
> 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.

I understand, I will investigate more in the next days. Thank you!

> 
> Regards,
> 
> Kin EA3CV

73 de Gregor, DO5SSB