[Dxspider-support] Incorrect node configurations/Solution (III)

Kin ea3cv at cronux.net
Mon Nov 18 17:03:04 GMT 2024


Hi all,

Here is an example of what is happening with the failure to define
connections between pairs of nodes.
What is incorrect is shown in red and what is correct or corrected is shown
in blue.
I hope it can help you to understand that the callsign of the node does not
have to be identical to the sysop, and if it is not, we will authenticate
with the callsign of the node.  


Nodes:   XX0AAA-2                               ZZ9BBB-5
IPs:     1.1.1.1:7300  <--------------------->  2.2.2.2:8000
sysops:  XX0AAA                                 ZZ9BBB

file:  connect/ZZ9BBB-5                       connect/XX0AAA-2

       timeout 15                             timeout 15
       connect telnet 2.2.2.2 8000            connect telnet 1.1.1.1 7300
       'login:' 'XX0AAA'                      'login:' 'ZZ9BBB-5'
	 
cmd:   set/spider ZZ9BBB-5                    set/spider XX0AAA


cmd:   who                                    who
	 ZZ9BBB-5  NODE DXSP ...                XX0AAA  NODE DXSP ...


                                         PC92^ZZ9BBB-5^53523^D^^5XX0AAA^H98^

The solution is this:

File:  connect/ZZ9BBB-5                       
	

       timeout 15                             
       connect telnet 2.2.2.2 7300
       'login:' 'XX0AAA-2'

cmd:                                           disc XX0AAA
                                               set/user XX0AAA
                                               set/spider XX0AAA-2

To solve it properly requires the collaboration of both nodes involved, but
if there is no agreement, it is preferable that at least the one that is
willing, changes it.
Here is a list of some couples that should agree to modify their
configurations:

CT2IWW-2   CS5ARTD-2  PC92^CS5ARTD-2^52204^D^^5CT2IWW-2^H93^
EA7URG     GB7NHR     PC92^GB7NHR^52624^D^^5EA7URG^H97^
F4BWT      I8ZSE-1    PC92^I8ZSE-1^19496^C^7F4BWT:5000^H96^
F4GVE      SR4DXC     PC92^SR4DXC^23175^C^7F4GVE:54.55^H94^
HI8S       NL7S       PC92^NL7S^51005^D^^5HI8S^H95^
IK3STG-6   I3ITX-6    PC92^I3ITX-6^48680^C^7IK3STG-6:5451^H96^
IW0QNL     PY1NB-4    PC92^PY1NB-4^52730^C^7IW0QNL:5401^H94^
IW2OHX-6   IK2DUW-6   PC92^IK2DUW-6^52803^D^^5IW2OHX-6^H95^
IZ0ORT-8   IZ0ORT-6   PC92^IZ0ORT-6^49653^D^^5IZ0ORT-8^H94^
IZ0ORT-8   IZ0FKE     PC92^IZ0FKE^52710^D^^5IZ0ORT-8^H96^
K1RFI      NN1D       PC92^NN1D^37153^D^^5K1RFI^H95^
K7EK       IQ1IM-6    PC92^IQ1IM-6^54243^D^^5K7EK^H94^
KB8PMY     KF8I-3     PC92^KF8I-3^52384^C^7KB8PMY:5457^H94^
LY4I       GB7HTL     PC92^GB7HTL^53294^D^^1LY4I^H95^
N2YO-4     YO2LOJ-2   PC92^YO2LOJ-2^52508^D^^5N2YO-4^H97^
OK0DXP     DB0ERF-5   PC92^DB0ERF-5^46997^D^^4OK0DXP^H98^
PI1LAP     PA2SQ-1    PC92^PA2SQ-1^53523^D^^5PI1LAP^H97^
PY1TSB-1   DH1TW-2    PC92^DH1TW-2^52804^D^^5PY1TSB-1^H94^
PY4OG-2    PY3NZ-8    PC92^PY3NZ-8^52505^D^^5PY4OG-2^H97^
SM7IUN     PY4OG-4    PC92^PY4OG-4^52973^C^7SM7IUN:54.57^H97^
SV5FRI     CU3HY-2    PC92^CU3HY-2^52415^C^7SV5FRI:5457^H97^
SV5FRI-2   F1FCA-2    PC92^F1FCA-2^53414^D^^5SV5FRI-2^H96^
UT1U       EI7MRE     PC92^EI7MRE^53109^D^^5UT1U^H97^
VE2PKT     KY9J-2     PC92^KY9J-2^53407.01^D^^5VE2PKT^H95^
VE3TOK     SR4DXC     PC92^SR4DXC^53820^D^^5VE3TOK^H95^
VE7CC      IZ0FKE-6   PC92^IZ0FKE-6^53520^C^7VE7CC:5000^H97^
VK5GR      VK5GR-2    PC92^VK5GR-2^53703.02^A^^5KY9J-2:74.130.145.58^H98^
W7JD       NL7S       PC92^NL7S^52505^D^^5W7JD^H95^
W8BS       KF8I-3     PC92^KF8I-3^53404^D^^5W8BS^H94^
WB3FFV     VE6CIC-1   PC92^VE6CIC-1^6903^A^^5WB3FFV:204.9.93.14^H97^


Regards,

Kin EA3CV


EA3CV-2 dxcluster.cronux.net 7300
http://clustermap.cronux.net/map.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 8242 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20241118/09206d25/attachment.bin>


More information about the Dxspider-support mailing list