[Dxspider-support] badIP listing
Kin
ea3cv at cronux.net
Mon Mar 31 08:12:21 BST 2025
Jarmo,
If F6BVP-3 doesn't have badip enabled, it's normal for it to accept that IP.
Read this:
https://mailman.tobit.co.uk/pipermail/dxspider-support/2025-February/019731.
html
F6BVP-3 Version: 5457 Build: 524
This is the consequence of not updating the node.
I've added the sysop to the email.
Kin EA3CV
-----Mensaje original-----
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de
jarmo via Dxspider-support
Enviado el: lunes, 31 de marzo de 2025 9:01
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: jarmo <oh1mrr at nic.fi>
Asunto: [Dxspider-support] badIP listing
I see this happening all the time...
1743376012^(*) PCPROT: PC61 82.149.227.228 in badip list, dropped
1743376270^(*) PCPROT: PC61 82.149.227.228 in badip list, dropped
1743376759^(*) PCPROT: PC61 82.149.227.228 in badip list, dropped
1743376759^(*) PCPROT: PC61 82.149.227.228 in badip list, dropped And
address leads to 1738374476^DXProt^PC92A DO5SSB-2 -> 82.149.227.228 on
F6BVP-3
So, if he's the "bad" guy, why someone let him connect at all? In this case
F6BVP-3....
Jarmo, oh1mrr
_______________________________________________
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