W3LPL Cluster login

Need help? - Post here and we will find a solution for you.
Post Reply
w9mdb
Old Man
Posts: 105
Joined: 13 Jul 2014, 12:05

W3LPL Cluster login

Post by w9mdb » 18 Jul 2019, 20:43

The W3LPL cluster does not contain "login:" and I'd like to modify the clusterlogonscript to recognize the prompt
"Please enter your call:" to basically need to recognize "call:" instead of "login:"

The default script doesn't show "login:".
And I can't find any documentaion on the scripting language.
So how can I wait for specific string before sending callsign?

de Mike W9MDB

User avatar
W7DRM
Log4OM Alpha Team
Posts: 552
Joined: 19 Feb 2014, 19:44

Re: W3LPL Cluster login

Post by W7DRM » 19 Jul 2019, 05:23

Hi Mike,

The Login script is in the Log4OM configuration folder - and the file is ClusterLogonScript.txt.

I am not sure if my login script is default, but mine simply reads as follows:

// use <callsign> command to send your callsign to the server.
<callsign>


With it, I can log into dxc.w3lpl.net and get spots delivered. My callsign is furnished a bit out of order, but it accepts it. First time logging in I had to give my name and confirm QTH, using manual commands. After that, logged in fine with the above script.

As for the script, I know of no delay command that are available to use, or interactive commands. Maybe Lele or Terry can confirm or deny that.

I hope this helps.

Doug - W7DRM

User avatar
G4POP
Moderator
Posts: 5619
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: W3LPL Cluster login

Post by G4POP » 19 Jul 2019, 05:59

<DELAY> adds 1 second delay

<DELAY>
<DELAY>
<DELAY>
Three on separate lines adds 3 secconds
73 Terry G4POP

w9mdb
Old Man
Posts: 105
Joined: 13 Jul 2014, 12:05

Re: W3LPL Cluster login

Post by w9mdb » 19 Jul 2019, 17:16

It's very irregular in whether or not it succeeds....

Here's a successful one
QRX ... # 1 in line
-> W9MDB
*** Connected to: W3LPL
Welcome to the W3LPL AR-Cluster node Telnet port!
-> sh/dx/30
Please enter your call:
Hello Mike Black (W9MDB)

Then it will fail with the same sequence
QRX ... # 1 in line
-> W9MDB
*** Connected to: W3LPL
Welcome to the W3LPL AR-Cluster node Telnet port!
-> sh/dx/30
Please enter your call:
Invalid call.

We really need to be able to wait for the "call:" prompt before sending anything.

Where is the scripting language located in the code? I was just going to hexedit the binary and change login: to call:"

I also don't understand why it's not timing out after NOT receiving "login:".

Mike

User avatar
W7DRM
Log4OM Alpha Team
Posts: 552
Joined: 19 Feb 2014, 19:44

Re: W3LPL Cluster login

Post by W7DRM » 19 Jul 2019, 22:18

Hi Mike,

Did you try the <Delay> as Terry suggested?

Doug - W7DRM

User avatar
G4POP
Moderator
Posts: 5619
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: W3LPL Cluster login

Post by G4POP » 20 Jul 2019, 07:11

I am sorry but I fail to see the issue it works fine for me!

This is my login script

// use <callsign> command to send your callsign to the server.
<DELAY>
<callsign>
sh/mydx/70

I always use one delay because so servers are slow but as you can see from the screen shot it works 100%

Untitled.jpg
Untitled.jpg (215.27 KiB) Viewed 124 times

BTW dont comment that the cluster was disconnected I had to stop the cluster to take a screen shot of the login section
73 Terry G4POP

w9mdb
Old Man
Posts: 105
Joined: 13 Jul 2014, 12:05

Re: W3LPL Cluster login

Post by w9mdb » 21 Jul 2019, 04:16

Try port 23 instead of 7373.

Seems 7323 works much better here too but 23 has problems.

Mike

User avatar
G4POP
Moderator
Posts: 5619
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: W3LPL Cluster login

Post by G4POP » 21 Jul 2019, 04:23

w9mdb wrote:
21 Jul 2019, 04:16
Try port 23 instead of 7373.

Seems 7323 works much better here too but 23 has problems.

Mike
Then you should contact the cluster provider
73 Terry G4POP

w9mdb
Old Man
Posts: 105
Joined: 13 Jul 2014, 12:05

Re: W3LPL Cluster login

Post by w9mdb » 21 Jul 2019, 14:27

I was able to write a simple client that talks to w3lpl port 23 without any problem.
Simply waits to see "call:".

I thought I saw where Log4OM is supposed to be waiting for "login:" or time out....but I don't see that happening.

I really don't want to hassle w3lpl when the client should be able to handle such things.

It appears to me that Log4OM is taking the 1st line of response and running with it or something along that line where it simply is not waiting long enough...and the extra delays don'd deal with it in a stable manner.

And I can't find "login:" anywhere in any of the binaries in Log4OM so perhaps that info I saw was bogus.

It's not just me either....I have a friend who sees the same problem.

And yes...using the 7373 port does seem to work much better probably because there's hardly anybody on it.

So can you answer these questions:
#1 Is the connection waiting for "login:" ? If so, where is that code.
#2 Is there ANY documentation on the scripting language?

Post Reply