[Dxspider-support] DXSpider mojo branch build 482

[Luigi Carlotto IK5ZUK]

Hi Dirk,

thanks, I've supposed this work around.

73 Luigi IK5ZUK


Il 20/01/2023 17:24, Dirk Koopman via Dxspider-support ha scritto:
> Not at the moment. I will put it in next time, but it's just a text 
> file. If you need it right away, just edit badip.local and then do a 
> 'load/badip' in a console.
>
> Dirk
>
> On 20/01/2023 15:47, Luigi Carlotto IK5ZUK wrote:
>> Hi Dirk,
>>
>> on the new  v1.57 build 482 I've seen set/badip and sh/badip, but 
>> it's missing the unset/badip (just in case of typo or something 
>> else)... Are you planning to add this command later ?
>>
>> 73 Luigi IK5ZUK
>>
>> Il 20/01/2023 15:41, Dirk Koopman via Dxspider-support ha scritto:
>>> There is a new release on the mojo branch.
>>>
>>> The main changes that will be of interest are:
>>>
>>> 1. There is now a complete implementation of stopping logins from 
>>> TOR nodes and some other bad IP addresses. I maintain the 
>>> badip.torexit, badip.torrelay and badip.global files. If you follow 
>>> the instructions below for your local crontab, you will keep a 
>>> current set of 'bad ip addresses'. You can also add your own local 
>>> bad ip addresses with the set/badip command. But if you think this 
>>> IP address is a problem, tell the support mailing list and I will 
>>> add it to the 'global' list, which will be distributed around those 
>>> nodes that download the master lists.
>>>
>>> You will need to install Net::CIDR::Lite to utilise the badip stuff.
>>>
>>> 2. There is a mechanism for aliasing localhost on client connections 
>>> and/or other rfc1918 addresses for more complex node arrangements 
>>> such as web clusters etc. The default arrangement a simple node with 
>>> one external ip address will "just work" automatically, once it has 
>>> either connect to another node, or an external user connects.
>>>
>>> This means that sshing into a node, running a console and doing a 
>>> few dx commands will result in the external address appearing in the 
>>> routing tables locally and externally automatically. If you have a 
>>> more complex networking arrangement, please get in touch on here (or 
>>> privately) for advice.
>>>
>>> 3. There is a mechanism that uses information from incoming PC92 A 
>>> records as well as PC61 spots to "upgrade" PC11 spots into PC61s. 
>>> There is command 'show/spotstats' (or 'sh/spot' for short) that 
>>> displays some statistics as to how this is all going where you are 
>>> in the network. Don't be disheartened if you only see a small 
>>> percentage of upgrades. It depends very much on how many and which 
>>> nodes that only send PC11 spots you are connected to. I happen to 
>>> get upwards of 6% on my test machine, but that means there will be 
>>> that many fewer for some other node to do.
>>>
>>> I expect that there will be questions....
>>>
>>> 73 Dirk G1TLH
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230121/f7caff94/attachment.htm>