[Dxspider-support] Bad IP

Tue Feb 4 08:50:21 GMT 2025

Hi Enrico,

Now I clearly understand what has happened.
Experimenting is also part of our hobby :) I would suggest that, since you want to connect to as many nodes as possible, you consider the potential impact of forwarding packets to all nodes. As you may have seen in the code and I assume in this forum, when, for example, a spot is sent to the network, it is forwarded via flooding to all nodes, and looking at the topology we have... The same happens with PC92, PC93, PC41, … packets.
I'm sure you will discover significant differences due to the many custom configurations by sysops regarding spot/ann forwarding and routing control.

Regards,

Kin EA3CV

De: Enrico Lorenzoni <iu3azc at gmail.com> 
Enviado el: martes, 4 de febrero de 2025 9:29
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: Kin <ea3cv at cronux.net>
Asunto: Re: [Dxspider-support] Bad IP

Hi Kin,

I tried with different SSIDs when I found out that the cluster network doesn't allow the same callsign to be connected to more than 3 nodes at the same time; then, when I realised that some nodes rejected SSIDs > 10, I moved to changing the call area as well (using callsigns that are not assigned to any Italian ham operator - no one will have my same callsign with just a different number).

            std::string mycall = "IU" + std::to_string(sock % 9) + "AZC-" + std::to_string(sock / 9);

I apologise for the trouble I created. As you can see, I only received data and I didn't submit any spots - also I used variations of my own callsign rather than generating random ones.
As the experiment was very enlightening and enjoyable for the few hours while I was connected to more than half of the nodes of the network at the same time, I'm a bit tempted by setting up a node myself that will achieve a similar function (being connected to as many nodes as possible and receive spots from them, allowing me to compare the latency and the presence or absence of them in various parts of the network).
I might be able to start something in Telehouse East https://www.telehouse.net/data-centre-services/uk/london/telehouse-east/ or a similar level datacenter, with IPv4 + IPv6 connectivity of course.

Are people on this mailing list open to peering requests?

73 de IU4AZC Enrico

Il giorno mar 4 feb 2025 alle ore 07:57 Kin via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> > ha scritto:
Keith,

I don't doubt what IU4AZC says, but I don't think it answers what he actually did. The 3 connections max thing, he skipped it when he used SSIDs.

Anyway, it's just what I see.

     13 IU0AZC-2
     14 IU3AZC-20
     14 IU4AZC-1
     15 IU4AZC-14
     28 IU4AZC-2
     30 IU4AZC-3
     31 IU4AZC-4
     29 IU4AZC-5
     28 IU4AZC-6
     14 IU4AZC-7
     14 IU4AZC-8
     16 IU5AZC-10
     14 IU5AZC-20
     30 IU6AZC
     14 IU6AZC-1
     13 IU7AZC-34
     16 IU8AZC

Regards,

Kin EA3CV

De: Dxspider-support <dxspider-support-bounces at tobit.co.uk <mailto:dxspider-support-bounces at tobit.co.uk> > En nombre de Keith, G6NHU via Dxspider-support
Enviado el: lunes, 3 de febrero de 2025 20:17
Para: The DXSpider Support list <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> >
CC: Keith, G6NHU <g6nhu at me.com <mailto:g6nhu at me.com> >
Asunto: Re: [Dxspider-support] Bad IP

OK, he says he was doing that because he was trying to get around the three connection limit.  In his defence, he’s said that the last three letters of Italian callsigns are unique and are never reused with different prefix numbers so he’s never been using someone else’s callsign.

He’s been doing some tests to see how different clusters vary between them compared to the ones where spots are uploaded the most, to see how they handle traffic and if some spots don’t traverse the entire network.

He’s assured me that from now, he won’t make any more than three connections in at the same time and will only use IU4AZC..I think that’s fair.

73 Keith G6NHU 
On 3 Feb 2025 at 13:13 +0000, Keith, G6NHU via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> >, wrote:
OK, I was checking files up to 031.dat and all I saw was IU4AZC, I see different callsigns after that.  I will ask him.
On 3 Feb 2025 at 12:27 +0000, Kin <ea3cv at cronux.net <mailto:ea3cv at cronux.net> >, wrote:
No, look what I see when I select your node. This indicates all the callsigns you have reported that have connected to your node:

grep "PC92\^G6NHU-2" 032.dat | grep -E "A\^\^1(IU[0-9]AZC)" | sed -E 's/.*A\^\^1(IU[0-9]AZC).*/\1/' | sort | uniq -c
     13 IU0AZC
     14 IU3AZC
    103 IU4AZC
     30 IU5AZC
     44 IU6AZC
     13 IU7AZC
     16 IU8AZC

Kin

De: Keith, G6NHU <g6nhu at me.com <mailto:g6nhu at me.com> >
Enviado el: lunes, 3 de febrero de 2025 11:53
Para: ea3cv at cronux.net <mailto:ea3cv at cronux.net> 
Asunto: Re: [Dxspider-support] Bad IP

I’m only seeing connections here from IU4AZC (with different SSIDs) and I’m fine with that.

73 Keith G6NHU
On 3 Feb 2025 at 10:09 +0000, ea3cv at cronux.net <mailto:ea3cv at cronux.net> , wrote:
Hi,
I think it must still be blocked because it is identifying itself with several different callsigns.
Just do:

grep -E "(IU\dAZC)" spider/local_data/debug/2025/033.dat

Kin EA3CV

Enviado desde Outlook para Android <https://aka.ms/AAb9ysg> 

  _____  

De: Dxspider-support <dxspider-support-bounces at tobit.co.uk <mailto:dxspider-support-bounces at tobit.co.uk> > en nombre de Keith, G6NHU via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> >
Enviado: lunes, febrero 3, 2025 10:38:45 a. m.
Para: The DXSpider Support list <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> >
CC: Keith, G6NHU <g6nhu at me.com <mailto:g6nhu at me.com> >
Asunto: Re: [Dxspider-support] Bad IP

I did this yesterday and have just received an email.

I’ve removed his IP from my bad list now.

73 Keith G6NHU 

"I'm Enrico IU4AZC and I'm a ham radio operator with a recent interest in understanding the behaviour of the DX Cluster network.
To grab a few statistics, I've created a basic software that opens a TCP connection to a few nodes and stores the received spots in a database. I've noticed that in the past hours your node started rejecting my connection and I suspect it's because some bug in my code made it behave in some "abusive" way. If that's the case, I apologise and I don't ask you to remove my ip from the blacklist sooner than the usual policy - I'll wait and use other clusters in the meantime.
But if it's not the case (maybe your software does a GeoIP lookup and the location doesn't match? I moved to London a few years ago), may I ask you to check in the logs the reason of my connections being rejected?
I'm currently connecting over IPv4 from 140.228.74.170."
On 1 Feb 2025 at 20:37 +0000, Kin via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> >, wrote:
Hi,

This IP 140.228.74.170 is being used to try to access different nodes on the
network, using different callsigns, with different SSIDs.
That pattern: IUxAZC-x
Advised: set/badip 140.228.74.170

Kin

_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto: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 <mailto: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 <mailto:Dxspider-support at tobit.co.uk> 
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250204/1db2d035/attachment-0001.htm>