[Dxspider-support] Incorrect node configurations (II)
Ian Maude
maudeij at gmail.com
Wed Nov 20 17:04:24 GMT 2024
This is all in the documentation
73 Ian (G0VGS)
> On 20 Nov 2024, at 08:27, Jan via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>
> Should't that be
>
> login 'py4og-4'
>
> So using only one ' at the beginning and one ' at the end of py4og-4?
>
> 73
> Jan PA4JJ
>
> Op 20-11-2024 om 08:48 schreef Kin via Dxspider-support:
>> Morning OMs,
>>
>> Marcio, you should do the following:
>>
>> Edit the file: connect/SM7IUN-1 and make it contain only this:
>>
>> timeout 15
>> connect telnet dxc.sm7iun.se 7300
>> login:' “PY4OG-4”
>>
>>
>> set/user SM7IUN
>> set/spider SM7IUN-1
>> conn SM7IUN-1
>>
>> And Björn should do nothing.
>>
>> Kin
>>
>>
>> EA3CV-2 dxcluster.cronux.net <http://dxcluster.cronux.net/> 7300
>> http://clustermap.cronux.net/map.html
>>
>> De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> <mailto:dxspider-support-bounces at tobit.co.uk> En nombre de J.Marcio via Dxspider-support
>> Enviado el: martes, 19 de noviembre de 2024 23:05
>> Para: The DXSpider Support list <dxspider-support at tobit.co.uk> <mailto:dxspider-support at tobit.co.uk>
>> CC: J.Marcio <jm.py4og at gmail.com> <mailto:jm.py4og at gmail.com>
>> Asunto: Re: [Dxspider-support] Incorrect node configurations (II)
>>
>> Hi Kin and Björn,
>>
>> I deleted SM7IUN, which one should I add?
>> PY4OG-2 doesn't exist, it might be set to PY3NZ.
>> Good job Kin!
>>
>> J.Marcio
>> PY4OG
>>
>>
>> Em seg., 18 de nov. de 2024 às 04:06, Kin via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>> escreveu:
>> Hi Björn,
>>
>> There are two nodes CS5ARTD-2 and PY4OG-4 that say SM7IUN is a node:
>>
>> PC92^CS5ARTD-2^85800^A^^5SM7IUN:213.164.211.147^H89^
>> PC92^PY4OG-4^85800.02^A^^7SM7IUN:213.164.211.147^H94^
>>
>> And as you commented, your nodes are: SM7IUN-1, SM7IUN-2 and SM7IUN-3.
>>
>> But your SM7IUN-1 node says that you are connected to the nodes: CS5ARTD-2 and PY4OG-4:
>>
>> PC92^SM7IUN-1^85800.02^A^^5CS5ARTD-2:65.109.3.118^H94^
>> PC92^SM7IUN-1^85800.05^A^^5PY4OG-4:138.197.6.118^H91^
>>
>> From the above we can think that in the connection files, the login is not correct because the callsign of the node has not been set.
>>
>> Kin EA3CV
>> EA3CV-2 dxcluster.cronux.net <http://dxcluster.cronux.net/> 7300
>> http://clustermap.cronux.net/map.html
>>
>> De: Björn Ekelund <bjorn at ekelund.nu <mailto:bjorn at ekelund.nu>>
>> Enviado el: domingo, 17 de noviembre de 2024 20:02
>> Para: The DXSpider Support list <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>>
>> CC: s50u at s50e.si <mailto:s50u at s50e.si>; Kin <ea3cv at cronux.net <mailto:ea3cv at cronux.net>>
>> Asunto: Re: [Dxspider-support] Incorrect node configurations (II)
>>
>> I have to expose my ignorance and ask if the problem is in my node or the
>> connecting node when someone connects to SM7IUN rather than SM7IUN-1.
>>
>> My node's outgoing connections are with sk3w-6, zl2arn-10, ve3ey-7, and m0kgx-3.
>> All other connections are incoming.
>>
>> My assumption is that the problem is in the incoming connection's node. Is it?
>>
>> Björn SM7IUN
>>
>>
>> On Sun, Nov 17, 2024 at 7:54 PM Björn Ekelund <bjorn at ekelund.nu <mailto:bjorn at ekelund.nu>> wrote:
>> I'm surprised to see SM7IUN. It should not exist. My nodes are SM7IUN-1, -2, and -3.
>>
>> Björn SM7IUN
>>
>> On Sun, Nov 17, 2024 at 6:21 PM Kin via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>> wrote:
>> Yes Dan, but not only the -32, -2 is a user.
>> It would be advisable to do this:
>>
>> disc IW1QLH-2
>> set/user IW1QLH-2
>> disc IW1QLH-32
>> set/user IW1QLH-32
>>
>> as they are not nodes, it does not affect and ensures that no erroneous data will be sent to the network.
>> Also, there are nodes with PC9x disabled, and when they enable it, they will surely send erroneous information.
>> I do not understand why those who can use PC9x do not do so. And to say that it's a bandwidth problem with the speeds given by the operators ???
>> I advise to run:
>>
>> set/wantPC9x
>>
>> won't notice anything and will be visible to the rest of the network.
>>
>> 73 de Kin EA3CV
>>
>> _______________________________________________
>>
>> EA3CV-2 dxcluster.cronux.net <http://dxcluster.cronux.net/> 7300
>> http://clustermap.cronux.net/map.html
>>
>>
>>
>> De: Dxspider-support <dxspider-support-bounces at tobit.co.uk <mailto:dxspider-support-bounces at tobit.co.uk>> En nombre de Danilo Brelih via Dxspider-support
>> Enviado el: domingo, 17 de noviembre de 2024 18:10
>> Para: Kin via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>>
>> CC: Danilo Brelih <s50u at s50e.si <mailto:s50u at s50e.si>>
>> Asunto: Re: [Dxspider-support] Incorrect node configurations (II)
>>
>> Kin via Dxspider-support je 17.11.2024 ob 14:09 napisal:
>>
>> According to my knowledge IW1QLH-32 should be defined as user since it connects clusters every "x" minutes for his uptime statistics, see:
>>
>> http://www.hamcluster.net/
>>
>> CUL Dan S50U
>>
>>
>> Hi,
>>
>> As an extension to my last message, here is a complete list of what can be
>> seen yesterday, but only with pc9x, if you look at the nodes that don't have
>> it enabled or implemented, there is even more.
>>
>> The list shows 'possible' errors in the definition of the partners. But it
>> does not indicate which one is wrong.
>>
>> origin node partner nodes
>> ----------- ---------------------
>> CS5ARTD-2 SM7IUN SM7IUN-1
>> CS5SEL-5 IW1QLH-2 IW1QLH-32
>> CU3HY-2 SV5FRI SV5FRI-1
>> CX2SA-8 IW1QLH-2 IW1QLH-32
>> DB0ERF-5 F4BWT-3 F4BWT-7
>> EA4FIT-2 EA4FIT EA4FIT-5
>> GB7DJK DK7ET-4 DK7ET-5
>> GB7NHR EA7URG EA7URG-5
>> GB7NHR IW1QLH-2 IW1QLH-32
>> GB7RAU IW1QLH-2 IW1QLH-32
>> GB7VAX GB7DXG GB7DXG-1
>> GB7VAX IW1QLH-2 IW1QLH-32
>> HG8PRC R5ACQ-1 R5ACQ-3
>> IK4ICZ-6 IW1QLH-2 IW1QLH-6
>> IK5PWJ-6 IW1QLH-2 IW1QLH-32
>> IK5ZUK-6 IK5PWJ-6 IK5PWJ-8
>> IK6IHL-6 IW1QLH-2 IW1QLH-32
>> IK6XMI-6 IW1QLH-2 IW1QLH-32
>> IK7NXU-6 IW1QLH-2 IW1QLH-32
>> IQ1LA-6 IW1QLH-2 IW1QLH-6
>> IQ8PQ-6 N0VD N0VD-7
>> IQ8RB-6 N0VD N0VD-7
>> IU4QTF-9 IK4ICZ IK4ICZ-6
>> IW1QLH-2 EA4URE-2 EA4URE-3
>> IW1QLH-2 SM6HOC-2 SM6HOC-6
>> IW1QLH-2 W1NR W1NR-9
>> JH1RFM-9 IW1QLH-2 IW1QLH-6
>> KF8I-3 F1FCA F1FCA-2
>> KF8I-3 KB8PMY KB8PMY-3
>> KF8I-3 W8BS W8BS-2
>> KY9J-2 VE2PKT VE2PKT-9
>> KY9J-2 VK5GR VK5GR-2
>> N3BSQ-1 EA4FIT EA4FIT-2
>> NA4DA-2 WA0O WA0O-9
>> NL7S HI8S HI8S-8
>> NX9G IW1QLH-2 IW1QLH-6 IW1QLH-32
>> PA2SQ-1 PI1LAP PI1LAP-1
>> PA4JJ-1 PA4JJ-2 PA4JJ-3
>> PA4JJ-2 PA4JJ-1 PA4JJ-3
>> PA4JJ-3 PA4JJ-1 PA4JJ-2
>> PI1LAP-1 PI1LAP PI1LAP-2
>> PI4NOS-1 HB9VQQ-2 HB9VQQ-3
>> PY3NZ-8 IW1QLH-2 IW1QLH-6
>> PY3NZ-8 PY4OG-2 PY4OG-4
>> PY4OG-4 SM7IUN SM7IUN-1
>> PY5JO-11 IW1QLH-2 IW1QLH-6 IW1QLH-32
>> R2AKT-9 RA3ATX-8 RA3ATX-9
>> S50DXS IW1QLH-2 IW1QLH-32
>> SK3W-6 SM7IUN-1 SM7IUN-2
>> SM7IUN-1 IW1QLH-2 IW1QLH-32
>> SR4DXC F4GVE F4GVE-2
>> SR4DXC PI1LAP PI1LAP-1
>> VE3CGR-5 IW1QLH-2 IW1QLH-32
>> VE3EY-7 SM7IUN-1 SM7IUN-2
>> VE3ZIN-2 IW1QLH-2 IW1QLH-6
>> VE6CIC-1 SV5FRI SV5FRI-1
>> VE6CIC-1 WB3FFV WB3FFV-2
>> W1DX IW1QLH-2 IW1QLH-32
>> W1NR PA4JJ-2 PA4JJ-3
>> W6RFU N6WS-2 N6WS-6
>> W9TY-1 K4HNT-1 K4HNT-2
>> WB3FFV-2 9M2PJU-1 9M2PJU-2
>> WB3FFV-2 IW1QLH-2 IW1QLH-32
>> YO2LOJ-2 N2YO-2 N2YO-4
>>
>> An example of what I mean is shown with the first one in the list:
>>
>> CS5ARTD-2 SM7IUN SM7IUN-1
>>
>> PC92^CS5ARTD-2^85800.02^A^^7SM7IUN:213.164.211.147^H94^
>> PC92^SM7IUN-1^85799.02^A^^5CS5ARTD-2:65.109.3.118^H95^
>>
>> CS5ARTD-2 says it has SM7IUN connected as a node.
>> On the other hand, SM7IUN-1 says that the node connected to it is CS5ARTD-2.
>>
>> From the above we can conclude that one of the two nodes has its partner
>> configured incorrectly.
>>
>> If you can look at it and fix it, it would be very positive.
>>
>> Thanks for your help.
>>
>> 73 de Kin EA3CV
>>
>>
>> -------------------------------------
>>
>> EA3CV-2 dxcluster.cronux.net <http://dxcluster.cronux.net/> 7300
>> http://clustermap.cronux.net/map.html
>>
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>>
>> --
>> S50CLX DX Cluster <https://s50clx.infrax.si/>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
> --
> ____________________________________________________
> my dxspider clusters running on a raspberry pi:
> pa4jj-2 77.174.195.163 port 7300
> pa4jj-3 77.174.195.163 port 7388
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk <mailto: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/20241120/0d07c8e4/attachment-0001.htm>
More information about the Dxspider-support
mailing list