[Dxspider-support] Poorly defined connections?

[Kin]

Hi,

I think I have detected some problems in the information exchanged between
nodes. Possibly as a consequence of an error in the definition of the
neighbour/peer node.

SM7GVF-6 has possibly wrongly defined callsign DL9GTB-1, it should be
DL9GTB-2.
W9TY-1 has possibly wrongly defined callsign K4HNT-1, should be K4HNT-2
IW1QLH-6 has possibly poorly defined callsign NX9G-6, should be NX9G
EI7SDX possibly has ill-defined callsign ON4KST, should be ON4KST-2
ON5MM-2 has possibly ill-defined callsign VK5GR, should be VK5GR-2


The following, I have doubts because I have not been able to trace them:

IW0QNL

1731140467^(chan) <- I HB9VQQ-2 PC92^PY1NB-4^30067^D^^5IW0QNL^H97^
1731115367^(chan) <- I HB9VQQ-2 PC92^PY1NB-4^4967^C^7IW0QNL:5000^H97^

KM3T-5

1731111449^(chan) <- I HB9VQQ-2 PC92^KM3T-10^1049^D^^5KM3T-5^H96^
1731112399^(chan) <- I HB9VQQ-2 PC92^KM3T-10^1999^C^7KM3T-5:5000^H96^

Sysops would be well advised to review their settings. 
In the case of DXSpider, it would be enough to look at its connection file
at: /spider/connect/

73 de Kin EA3CV