[Dxspider-support] set/badip - what are its effects?

[Luigi Carlotto IK5ZUK]

Hello Martin and all.

Spider filters out all the spots coming from the badip addresses and 
also prevents (as do the set/lockout cmd) the login inside the node from 
that IP marked as "badip".
When a sysop marks an IP as badip, that action remains locally and it's 
not propagated to all the nodes in the net. Actually, the badip 
propagation from node-to-node into the Net does not exists.
Dirk more that one year ago created two kind of badip list in one of his 
server and we can add to our Spider's crontab file the entries to 
download them into our nodes.

73 Luigi IK5ZUK


Il 02/02/2024 15:59, Martin Davies G0HDB via Dxspider-support ha scritto:
> I've been trawling through the DXSpider documentation and the archives to try to find a
> description of what the effects of the 'set/badip' command are, but I haven't found anything so
> I'll be grateful if someone (eg. Dirk?) can provide some details.
>
> For example, if I use the command to add the IP address of a suspected bad actor to a
> node's local list, does that subsequently completely prevent that IP address from being able
> to access the node, and is the bad IP address automatically promulgated to adjacent nodes
> and hence to the wider DXCluster?  Does setting a bad IP address enable its owner to still
> log in to a node but only as an unregistered user who is unable to enter spots, talks etc?
> What are the differences between using the 'set/badip' and the 'set/lockout' commands and
> when should each be used?
>
> It'll be helpful to gain a better understanding of the effects of the 'set/badip' command before I
> start using it too liberally...!
>
> 73 and thanks in advance,
>