[Dxspider-support] BadIPs on PC92

IZ2LSC iz2lsc.andrea at gmail.com
Wed Apr 9 22:34:43 BST 2025


Kin, Dirk,
I suspect there could be a bug when a user is using the same callsign to
login into different clusters.
Look at this log.
when G0TRT-3 is logged in locally to his cluster he's using his private IP
address.
when he is logged in into my cluster obviously he is using his public ip
address (unless he hacked my VPN), but in some PC92A messages he is
advertised with this private address.
and vice versa, sometime when logged in locally on his cluster, the public
address is advertised.


03.dat:1741791264^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1741791275^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on G0TRT-9
03.dat:1741808155^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on G0TRT-9
03.dat:1742336162^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on G0TRT-9
03.dat:1742336174^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on IZ2LSC-99
03.dat:1742417155^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1742417162^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on G0TRT-9
03.dat:1742664386^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1742664418^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on G0TRT-9
03.dat:1742679851^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1742805869^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1742805871^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on G0TRT-9
03.dat:1742806351^DXProt^PC92A G0TRT-3 -> 98.159.234.163 on G0TRT-9
03.dat:1742807359^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1742807371^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on G0TRT-9
03.dat:1742850126^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1742850171^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on G0TRT-9
03.dat:1742897016^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1742897031^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on G0TRT-9
03.dat:1742916351^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on G0TRT-9
03.dat:1742916387^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on IZ2LSC-99
03.dat:1743006873^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1743006896^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on G0TRT-9
03.dat:1743082698^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1743082726^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on G0TRT-9
03.dat:1743197318^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on IZ2LSC-99
03.dat:1743197358^DXProt^PC92A G0TRT-3 -> 86.159.58.202 on G0TRT-9
03.dat:1743453723^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on G0TRT-9
03.dat:1743453777^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on IZ2LSC-99
04.dat:1743625876^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on G0TRT-9
04.dat:1743625915^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on IZ2LSC-99
04.dat:1744230514^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on IZ2LSC-99
04.dat:1744231776^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on G0TRT-9



-->


On Wed, Apr 9, 2025 at 11:03 PM IZ2LSC <iz2lsc.andrea at gmail.com> wrote:

> Hi Kin,
> 3rd line is for my test cluster (iz2lsc-55) that is connected only with
> iz2lsc-99 on the local lan, so it has not a public ip and no users (apart
> me doing some test).
>
> First 2 lines seems somthing coming from G0TRT-9, or al least this is what
> I see from my log:
>
> 1744182831^DXProt^PC92A G0TRT-3 -> 86.189.145.93 on IZ2LSC-99
> 1744182831^DXCommand^G0TRT-3 connected from 86.189.145.93 cols 80
> 1744182856^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on G0TRT-9
>
>
> 1744228950^DXProt^PC92A G0TRT-3 -> 86.189.145.93 on IZ2LSC-99
> 1744228950^DXCommand^G0TRT-3 connected from 86.189.145.93 cols 80
> 1744228986^DXProt^PC92A G0TRT-3 -> 192.168.1.254 on G0TRT-9
>
> Andrea
>
>
> -->
>
>
> On Wed, Apr 9, 2025 at 10:28 PM Kin <ea3cv at cronux.net> wrote:
>
>> This, Andrea:
>>
>>
>>
>> 1744182868^(chan-11) <- I EA4URE-7
>> PC92^IZ2LSC-99^26068^A^^1G0TRT-3:192.168.1.254^H95^
>>
>> 1744228994^(chan-9) <- I EA4URE-7
>> PC92^IZ2LSC-99^72194^A^^1G0TRT-3:192.168.1.254^H95^
>>
>> 1744229610^(chan-9) <- I EA4URE-7
>> PC92^IZ2LSC-99^72810.02^A^^5IZ2LSC-55:192.168.1.131^H95^
>>
>>
>>
>> Kin
>>
>>
>>
>> *De:* IZ2LSC <iz2lsc.andrea at gmail.com>
>> *Enviado el:* miércoles, 9 de abril de 2025 22:18
>> *Para:* The DXSpider Support list <dxspider-support at tobit.co.uk>
>> *CC:* Kin <ea3cv at cronux.net>
>> *Asunto:* Re: [Dxspider-support] BadIPs on PC92
>>
>>
>>
>> What did you receive from iz2lsc-99?
>>
>>
>>
>> andrea
>>
>>
>>
>> -->
>>
>>
>>
>>
>>
>> On Wed, Apr 9, 2025 at 8:32 PM Kin via Dxspider-support <
>> dxspider-support at tobit.co.uk> wrote:
>>
>> The list is updated by removing PC92Cs that are forwarded with LAN IPs.
>>
>> 7N4TWL-7
>> 9A0DXC
>> 9M2PJU-2
>> CT1EBQ-9
>> DB0ERF-5
>> DB0LJ-6
>> DB0PER
>> DB0PER-1
>> DL8FCL-7
>> DO5SSB-2
>> EA4FIT-2
>> EA6VQ-1
>> EI7MRE
>> F1FCA-2
>> F1MAC-3
>> F1MAC-6
>> F4IAA-3
>> GB7DXC-5
>> HG8PRC
>> I0OJJ-6
>> I3ITX-6
>> IK4ICZ-6
>> IK4ICZ-7
>> IR2UGI-6
>> IZ0ORT-6
>> IZ2LSC-99
>> IZ3LSV-6
>> IZ7AUH-6
>> JE3YEK
>> JG1VGX-9
>> JH1RFM-9
>> KB5VJY-3
>> KM3T-10
>> LW2DQC-6
>> LZ0DXC
>> N2WQ-73
>> N9JR-2
>> NN1D
>> OK0DXI
>> OZ5BBS-7
>> PA1RBZ
>> PI1LAP-1
>> PI4CC
>> PY4OG-4
>> PY5JO-11
>> TA2NC
>> VA3MW-7
>> VE3EY-7
>> VE6DXC
>> WA9PIE-2
>> WB3FFV-2
>> WT3Q
>>
>> Kin EA3CV
>>
>>
>> -----Mensaje original-----
>> De: Kin <ea3cv at cronux.net>
>> Enviado el: miércoles, 9 de abril de 2025 20:10
>> Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
>> Asunto: BadIPs on PC92
>>
>> Hi all,
>>
>> List of nodes that do not send their public IP address (today).
>>
>> This could be due to a misconfiguration or a bug in the build.
>> If you have it configured correctly, indicate it in the List, it may be a
>> defect.
>>
>> Nodes that identify themselves as 172.0.0.1
>>
>> GB7DXC-5        614
>> IK6XMI-12       614
>> IK6XMI-6        614
>> IZ8MBW-6        614
>> KM8V            611
>> SM6HOC-2        614
>> SM7IUN-1        614
>> VA3BAL-1        611
>> VE3CLG-1        614
>> VE3TOK-1        611
>> IZ3LSV-6        568
>> SK3W-6          568
>> HB9VQQ-2        568
>> IV3SCP-6        568
>> IZ5IIN-6        568
>> DB0OVN-6        568
>>
>> Nodes that send all or some users with 127.0.0.1 10.* 192.*
>> 172.16.*/172.31.*
>>
>> 7N4TWL-7
>> 9A0DXC
>> 9M2PJU-2
>> BG2RVL-9
>> DA0BCC-7
>> DB0ERF-5
>> DH1TW-2
>> DO5SSB-2
>> EA4FIT-2
>> F4IAA-3
>> G0TRT-9
>> G1FEF-2
>> G6NHU-2
>> GB7DXC-5
>> GB7DXM
>> GB7HTL
>> GB7RAU
>> GB7TLH
>> GB7VAX
>> HG8PRC
>> I0OJJ-6
>> IK4ICZ-7
>> IK5PWJ-6
>> IK5ZUK-6
>> IK6IHL-6
>> IK6XMI-12
>> IK6XMI-6
>> IK8HJC-6
>> IZ2LSC-99
>> IZ3LSV-6
>> IZ3MEZ-8
>> IZ7AUH-6
>> JE3YEK
>> JG1VGX-9
>> JH1RFM-9
>> K4GSO-2
>> K4ZR
>> KB5VJY-3
>> KE2L-5
>> KM3T-10
>> LU9DA-6
>> LW2DQC-6
>> LZ0DXC
>> N2KI
>> N2WQ-73
>> N6WS-6
>> NN1D
>> OH1RCF
>> OK0DXI
>> ON0LLV-4
>> ON0LLV-5
>> ON5MM-2
>> OZ5BBS-7
>> PA0ESH-3
>> PA1RBZ
>> PI1LAP-1
>> PI4CC
>> PY1NB-4
>> PY1TSP-1
>> PY4OG-4
>> S50DXS
>> SM7IUN-1
>> VA3MW-7
>> VE2PKT-9
>> VE6DXC
>> WI3W-2
>> WT3Q
>>
>> Let's build a better network.
>>
>> Kin EA3CV
>>
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> 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/20250409/e61e2d04/attachment-0001.htm>


More information about the Dxspider-support mailing list