Date   

Re: K0SI packet down?

Ryan Raney
 

Hi John,

Looks like you successfully connected and everything happened as it should. If you get a chance later please try once more. I often can get through once, then when I try to reply it fails to finish the transaction. I have no idea why. 

Thanks for testing!

On Thu, Sep 17, 2020, 4:02 PM John Beatty <jebeatty@...> wrote:

 

Ryan, here’s the replay text.  I’m still a novice at this.  I only attempted to connect to your WINLINK. Apparently there was nothing for me (no mail), then it begins the disconnect sequence (apparently).  If I understand everything, this session was expected results.  But I just don’t know

 

** Starting to call with connection script K0SI-10-via-MMJY

*** Attempting to open packet script: C:\RMS Express\NO0I\Scripts_WL2K\K0SI-10-via-MMJY.txt

*** Starting connection script with 4 connect/response lines and 0 command lines.

*** Initial connection node for packet script is MMJY

*** Opening KISS over TCP Host 127.0.0.1 Port 8100

*** Connecting to MMJY

*** Connected to MMJY at 2020/09/17 20:56:14

 

*** Looking for 'CONNECTED' in: CONNECTED

 

*** Found connection response: CONNECTED

 

*** Sending script line 3: C KE5SUI-10

   C KE5SUI-10

*** Looking for 'CONN' in: MMJY:K0SI-2} CONNECTED TO KE5SUI-10

 

*** Found connection response: CONNECTED TO KE5SUI-10

 

*** End of connection script

MMJY:K0SI-2} Connected to KE5SUI-10

Trying ec2-52-205-99-163.compute-1.amazonaws.com

*** NO0I-15 Connected to CMS

[WL2K-5.0-B2FWIHJM$]

;PQ: 30179382

CMS via KE5SUI-10 >

   ;FW: NO0I JOHN-NO0I|04789825

   [RMS Express-1.5.32.0-B2FHM$]

 

   ;PR: 89325050

   ; KE5SUI-10 DE NO0I (EM39UA)

   FF

FQ

*** --- End of session at 2020/09/17 20:56:50 ---

*** Messages sent: 0.  Total bytes sent: 0,  Time: 00:36,  bytes/minute: 0

*** Messages Received: 0.  Total bytes received: 0,  Total session time: 00:36,  bytes/minute: 0

MMJY:K0SI-2} Welcome back.

*** Disconnecting

*** Disconnecting due to timeout

*** Disconnected at 2020/09/17 20:57:34

 

*** Disconnect reported.

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of John Beatty
Sent: Thursday, September 17, 2020 3:33 PM
To: main@CMRA.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

I’ll give it go Ryan.

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 3:31 PM
To: main@cmra.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Can you try to connect to it via winlink express and let me know if it disconnects prematurely for you? Instructions for K0SI-10 are below, substitute KE5SUI-10 to test my node. They're both behaving the same for me so use either one. 

 

To send your winlink packets through MMJY you'll have to change your connection type from direct to script. Then the line below will no longer be greyed out. Next click add script. A new window will pop up, this is where we'll set up the connection script to jump through the node. Go ahead and name the script something memorable like K0SI-10 via MMJY. Next in the body of the script enter the following:

 

C MMJY

CONN

C K0SI-10

CONN

 

Now click save. Make sure your new script is selected in the connection script drop-down and click start. 

 

Once you're done with the test remember to set your connection mode back to direct or you will always go through MMJY, which I don't advise unless you have to. 

 

On Thu, Sep 17, 2020, 3:27 PM John Beatty <jebeatty@...> wrote:

That would help lol.  I pressed the disconnect button on EASY Term screen.

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 3:26 PM
To: main@cmra.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi John,

 

Did you tell it to disconnect or did it do it prematurely on it's own?

 

On Thu, Sep 17, 2020, 3:24 PM John Beatty <jebeatty@...> wrote:

Ryan,

A quick connect from my station to MMJY to you, then a disconnect.  Just for checking purposes…

 

Upper window response----------------

 

*** Connected to station MMJY 9/17/2020 3:17:55 PM

:>c ke5sui-10

MMJY:K0SI-2} Connected to KE5SUI-10

Trying ec2-52-205-99-163.compute-1.amazonaws.com

*** NO0I-15 Connected to CMS

[WL2K-5.0-B2FWIHJM$]

;PQ: 99201778

CMS via KE5SUI-10 >

*** Disconnected from station MMJY 9/17/2020 3:19:02 PM

 

 

Lower window response------------------------------

 

1:Fm NO0I To MMJY <SABM P>[15:17:53]

1:Fm MMJY To NO0I <UA F >[15:17:55]

1:Fm NO0I To MMJY <I P R0 S0 pid=F0 Len=12 >[15:18:16]

c ke5sui-10

 

1:Fm MMJY To NO0I <RR P/F R1 >[15:18:18]

1:Fm NO0I-15 To KE5SUI-10 <SABM P>[15:18:18]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:18:19]

1:Fm MMJY To NO0I <I R1 S0 pid=F0 Len=36 >[15:18:20]

MMJY:K0SI-2} Connected to KE5SUI-10

 

1:Fm NO0I To MMJY <RR R1 >[15:18:21]

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S0 pid=F0 Len=49 >[15:18:22]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R1 >[15:18:23]

1:Fm MMJY To NO0I <I R1 S1 pid=F0 Len=49 >[15:18:24]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I To MMJY <RR R2 >[15:18:24]

1:Fm KE5SUI-10 To NO0I-15 <I R0 S1 pid=F0 Len=29 >[15:18:25]

*** NO0I-15 Connected to CMS

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S2 pid=F0 Len=21 >[15:18:26]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S3 pid=F0 Len=14 >[15:18:26]

;PQ: 99201778

 

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S4 pid=F0 Len=20 >[15:18:26]

CMS via KE5SUI-10 >

 

1:Fm MMJY To NO0I <I R1 S2 pid=F0 Len=29 >[15:18:27]

*** NO0I-15 Connected to CMS

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R5 >[15:18:27]

1:Fm NO0I To MMJY <RR R3 >[15:18:28]

1:Fm MMJY To NO0I <I R1 S3 pid=F0 Len=21 >[15:18:29]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm MMJY To NO0I <I R1 S4 pid=F0 Len=14 >[15:18:29]

;PQ: 99201778

 

1:Fm NO0I To MMJY <RR R5 >[15:18:29]

1:Fm MMJY To NO0I <I R1 S5 pid=F0 Len=20 >[15:18:31]

CMS via KE5SUI-10 >

 

1:Fm NO0I To MMJY <RR R6 >[15:18:31]

1:Fm NO0I To MMJY <DISC P>[15:19:02]

1:Fm MMJY To NO0I <UA F >[15:19:03]

1:Fm NO0I-15 To KE5SUI-10 <DISC P>[15:19:03]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:19:06]

 

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 2:41 PM
To: main@CMRA.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi all,

Sorry to keep bringing this up but it seems like the problem isn't with K0SI-10, it may be with MMJY or MJEF. I went through the trouble to configure my bpq node as a RMS gateway on KE5SUI-10, and I have the same trouble connecting to it through MMJY or MJEF. For some reason MMJY and MJEF are both sending disconnect packets that I didn't tell them to before the transaction is complete.

If anyone has an intimate knowledge of packet radio I'd love to get their thoughts on the logs that have been posted in this thread, or some troubleshooting steps/ideal winlink settings. If anyone else can test connecting to K0SI-10 or KE5SUI-10 via MMJY or MJEF on 145.070 (instructions on how to do that also in this thread) to see if they have the same problems I'd also appreciate that as it could help narrow down if it's just me or not. 

Sorry for any unnecessary trips to the K0SI-10 gateway anyone may have taken. 

73's
KE5SUI

73's


Re: K0SI packet down?

John Beatty
 

 

Ryan, here’s the replay text.  I’m still a novice at this.  I only attempted to connect to your WINLINK. Apparently there was nothing for me (no mail), then it begins the disconnect sequence (apparently).  If I understand everything, this session was expected results.  But I just don’t know

 

** Starting to call with connection script K0SI-10-via-MMJY

*** Attempting to open packet script: C:\RMS Express\NO0I\Scripts_WL2K\K0SI-10-via-MMJY.txt

*** Starting connection script with 4 connect/response lines and 0 command lines.

*** Initial connection node for packet script is MMJY

*** Opening KISS over TCP Host 127.0.0.1 Port 8100

*** Connecting to MMJY

*** Connected to MMJY at 2020/09/17 20:56:14

 

*** Looking for 'CONNECTED' in: CONNECTED

 

*** Found connection response: CONNECTED

 

*** Sending script line 3: C KE5SUI-10

   C KE5SUI-10

*** Looking for 'CONN' in: MMJY:K0SI-2} CONNECTED TO KE5SUI-10

 

*** Found connection response: CONNECTED TO KE5SUI-10

 

*** End of connection script

MMJY:K0SI-2} Connected to KE5SUI-10

Trying ec2-52-205-99-163.compute-1.amazonaws.com

*** NO0I-15 Connected to CMS

[WL2K-5.0-B2FWIHJM$]

;PQ: 30179382

CMS via KE5SUI-10 >

   ;FW: NO0I JOHN-NO0I|04789825

   [RMS Express-1.5.32.0-B2FHM$]

 

   ;PR: 89325050

   ; KE5SUI-10 DE NO0I (EM39UA)

   FF

FQ

*** --- End of session at 2020/09/17 20:56:50 ---

*** Messages sent: 0.  Total bytes sent: 0,  Time: 00:36,  bytes/minute: 0

*** Messages Received: 0.  Total bytes received: 0,  Total session time: 00:36,  bytes/minute: 0

MMJY:K0SI-2} Welcome back.

*** Disconnecting

*** Disconnecting due to timeout

*** Disconnected at 2020/09/17 20:57:34

 

*** Disconnect reported.

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of John Beatty
Sent: Thursday, September 17, 2020 3:33 PM
To: main@CMRA.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

I’ll give it go Ryan.

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 3:31 PM
To: main@cmra.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Can you try to connect to it via winlink express and let me know if it disconnects prematurely for you? Instructions for K0SI-10 are below, substitute KE5SUI-10 to test my node. They're both behaving the same for me so use either one. 

 

To send your winlink packets through MMJY you'll have to change your connection type from direct to script. Then the line below will no longer be greyed out. Next click add script. A new window will pop up, this is where we'll set up the connection script to jump through the node. Go ahead and name the script something memorable like K0SI-10 via MMJY. Next in the body of the script enter the following:

 

C MMJY

CONN

C K0SI-10

CONN

 

Now click save. Make sure your new script is selected in the connection script drop-down and click start. 

 

Once you're done with the test remember to set your connection mode back to direct or you will always go through MMJY, which I don't advise unless you have to. 

 

On Thu, Sep 17, 2020, 3:27 PM John Beatty <jebeatty@...> wrote:

That would help lol.  I pressed the disconnect button on EASY Term screen.

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 3:26 PM
To: main@cmra.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi John,

 

Did you tell it to disconnect or did it do it prematurely on it's own?

 

On Thu, Sep 17, 2020, 3:24 PM John Beatty <jebeatty@...> wrote:

Ryan,

A quick connect from my station to MMJY to you, then a disconnect.  Just for checking purposes…

 

Upper window response----------------

 

*** Connected to station MMJY 9/17/2020 3:17:55 PM

:>c ke5sui-10

MMJY:K0SI-2} Connected to KE5SUI-10

Trying ec2-52-205-99-163.compute-1.amazonaws.com

*** NO0I-15 Connected to CMS

[WL2K-5.0-B2FWIHJM$]

;PQ: 99201778

CMS via KE5SUI-10 >

*** Disconnected from station MMJY 9/17/2020 3:19:02 PM

 

 

Lower window response------------------------------

 

1:Fm NO0I To MMJY <SABM P>[15:17:53]

1:Fm MMJY To NO0I <UA F >[15:17:55]

1:Fm NO0I To MMJY <I P R0 S0 pid=F0 Len=12 >[15:18:16]

c ke5sui-10

 

1:Fm MMJY To NO0I <RR P/F R1 >[15:18:18]

1:Fm NO0I-15 To KE5SUI-10 <SABM P>[15:18:18]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:18:19]

1:Fm MMJY To NO0I <I R1 S0 pid=F0 Len=36 >[15:18:20]

MMJY:K0SI-2} Connected to KE5SUI-10

 

1:Fm NO0I To MMJY <RR R1 >[15:18:21]

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S0 pid=F0 Len=49 >[15:18:22]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R1 >[15:18:23]

1:Fm MMJY To NO0I <I R1 S1 pid=F0 Len=49 >[15:18:24]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I To MMJY <RR R2 >[15:18:24]

1:Fm KE5SUI-10 To NO0I-15 <I R0 S1 pid=F0 Len=29 >[15:18:25]

*** NO0I-15 Connected to CMS

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S2 pid=F0 Len=21 >[15:18:26]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S3 pid=F0 Len=14 >[15:18:26]

;PQ: 99201778

 

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S4 pid=F0 Len=20 >[15:18:26]

CMS via KE5SUI-10 >

 

1:Fm MMJY To NO0I <I R1 S2 pid=F0 Len=29 >[15:18:27]

*** NO0I-15 Connected to CMS

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R5 >[15:18:27]

1:Fm NO0I To MMJY <RR R3 >[15:18:28]

1:Fm MMJY To NO0I <I R1 S3 pid=F0 Len=21 >[15:18:29]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm MMJY To NO0I <I R1 S4 pid=F0 Len=14 >[15:18:29]

;PQ: 99201778

 

1:Fm NO0I To MMJY <RR R5 >[15:18:29]

1:Fm MMJY To NO0I <I R1 S5 pid=F0 Len=20 >[15:18:31]

CMS via KE5SUI-10 >

 

1:Fm NO0I To MMJY <RR R6 >[15:18:31]

1:Fm NO0I To MMJY <DISC P>[15:19:02]

1:Fm MMJY To NO0I <UA F >[15:19:03]

1:Fm NO0I-15 To KE5SUI-10 <DISC P>[15:19:03]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:19:06]

 

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 2:41 PM
To: main@CMRA.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi all,

Sorry to keep bringing this up but it seems like the problem isn't with K0SI-10, it may be with MMJY or MJEF. I went through the trouble to configure my bpq node as a RMS gateway on KE5SUI-10, and I have the same trouble connecting to it through MMJY or MJEF. For some reason MMJY and MJEF are both sending disconnect packets that I didn't tell them to before the transaction is complete.

If anyone has an intimate knowledge of packet radio I'd love to get their thoughts on the logs that have been posted in this thread, or some troubleshooting steps/ideal winlink settings. If anyone else can test connecting to K0SI-10 or KE5SUI-10 via MMJY or MJEF on 145.070 (instructions on how to do that also in this thread) to see if they have the same problems I'd also appreciate that as it could help narrow down if it's just me or not. 

Sorry for any unnecessary trips to the K0SI-10 gateway anyone may have taken. 

73's
KE5SUI

73's


Re: K0SI packet down?

John Beatty
 

I’ll give it go Ryan.

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 3:31 PM
To: main@cmra.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Can you try to connect to it via winlink express and let me know if it disconnects prematurely for you? Instructions for K0SI-10 are below, substitute KE5SUI-10 to test my node. They're both behaving the same for me so use either one. 

 

To send your winlink packets through MMJY you'll have to change your connection type from direct to script. Then the line below will no longer be greyed out. Next click add script. A new window will pop up, this is where we'll set up the connection script to jump through the node. Go ahead and name the script something memorable like K0SI-10 via MMJY. Next in the body of the script enter the following:

 

C MMJY

CONN

C K0SI-10

CONN

 

Now click save. Make sure your new script is selected in the connection script drop-down and click start. 

 

Once you're done with the test remember to set your connection mode back to direct or you will always go through MMJY, which I don't advise unless you have to. 

 

On Thu, Sep 17, 2020, 3:27 PM John Beatty <jebeatty@...> wrote:

That would help lol.  I pressed the disconnect button on EASY Term screen.

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 3:26 PM
To: main@cmra.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi John,

 

Did you tell it to disconnect or did it do it prematurely on it's own?

 

On Thu, Sep 17, 2020, 3:24 PM John Beatty <jebeatty@...> wrote:

Ryan,

A quick connect from my station to MMJY to you, then a disconnect.  Just for checking purposes…

 

Upper window response----------------

 

*** Connected to station MMJY 9/17/2020 3:17:55 PM

:>c ke5sui-10

MMJY:K0SI-2} Connected to KE5SUI-10

Trying ec2-52-205-99-163.compute-1.amazonaws.com

*** NO0I-15 Connected to CMS

[WL2K-5.0-B2FWIHJM$]

;PQ: 99201778

CMS via KE5SUI-10 >

*** Disconnected from station MMJY 9/17/2020 3:19:02 PM

 

 

Lower window response------------------------------

 

1:Fm NO0I To MMJY <SABM P>[15:17:53]

1:Fm MMJY To NO0I <UA F >[15:17:55]

1:Fm NO0I To MMJY <I P R0 S0 pid=F0 Len=12 >[15:18:16]

c ke5sui-10

 

1:Fm MMJY To NO0I <RR P/F R1 >[15:18:18]

1:Fm NO0I-15 To KE5SUI-10 <SABM P>[15:18:18]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:18:19]

1:Fm MMJY To NO0I <I R1 S0 pid=F0 Len=36 >[15:18:20]

MMJY:K0SI-2} Connected to KE5SUI-10

 

1:Fm NO0I To MMJY <RR R1 >[15:18:21]

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S0 pid=F0 Len=49 >[15:18:22]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R1 >[15:18:23]

1:Fm MMJY To NO0I <I R1 S1 pid=F0 Len=49 >[15:18:24]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I To MMJY <RR R2 >[15:18:24]

1:Fm KE5SUI-10 To NO0I-15 <I R0 S1 pid=F0 Len=29 >[15:18:25]

*** NO0I-15 Connected to CMS

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S2 pid=F0 Len=21 >[15:18:26]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S3 pid=F0 Len=14 >[15:18:26]

;PQ: 99201778

 

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S4 pid=F0 Len=20 >[15:18:26]

CMS via KE5SUI-10 >

 

1:Fm MMJY To NO0I <I R1 S2 pid=F0 Len=29 >[15:18:27]

*** NO0I-15 Connected to CMS

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R5 >[15:18:27]

1:Fm NO0I To MMJY <RR R3 >[15:18:28]

1:Fm MMJY To NO0I <I R1 S3 pid=F0 Len=21 >[15:18:29]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm MMJY To NO0I <I R1 S4 pid=F0 Len=14 >[15:18:29]

;PQ: 99201778

 

1:Fm NO0I To MMJY <RR R5 >[15:18:29]

1:Fm MMJY To NO0I <I R1 S5 pid=F0 Len=20 >[15:18:31]

CMS via KE5SUI-10 >

 

1:Fm NO0I To MMJY <RR R6 >[15:18:31]

1:Fm NO0I To MMJY <DISC P>[15:19:02]

1:Fm MMJY To NO0I <UA F >[15:19:03]

1:Fm NO0I-15 To KE5SUI-10 <DISC P>[15:19:03]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:19:06]

 

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 2:41 PM
To: main@CMRA.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi all,

Sorry to keep bringing this up but it seems like the problem isn't with K0SI-10, it may be with MMJY or MJEF. I went through the trouble to configure my bpq node as a RMS gateway on KE5SUI-10, and I have the same trouble connecting to it through MMJY or MJEF. For some reason MMJY and MJEF are both sending disconnect packets that I didn't tell them to before the transaction is complete.

If anyone has an intimate knowledge of packet radio I'd love to get their thoughts on the logs that have been posted in this thread, or some troubleshooting steps/ideal winlink settings. If anyone else can test connecting to K0SI-10 or KE5SUI-10 via MMJY or MJEF on 145.070 (instructions on how to do that also in this thread) to see if they have the same problems I'd also appreciate that as it could help narrow down if it's just me or not. 

Sorry for any unnecessary trips to the K0SI-10 gateway anyone may have taken. 

73's
KE5SUI

73's


Re: K0SI packet down?

Ryan Raney
 

Can you try to connect to it via winlink express and let me know if it disconnects prematurely for you? Instructions for K0SI-10 are below, substitute KE5SUI-10 to test my node. They're both behaving the same for me so use either one. 

To send your winlink packets through MMJY you'll have to change your connection type from direct to script. Then the line below will no longer be greyed out. Next click add script. A new window will pop up, this is where we'll set up the connection script to jump through the node. Go ahead and name the script something memorable like K0SI-10 via MMJY. Next in the body of the script enter the following:

C MMJY
CONN
C K0SI-10
CONN

Now click save. Make sure your new script is selected in the connection script drop-down and click start. 

Once you're done with the test remember to set your connection mode back to direct or you will always go through MMJY, which I don't advise unless you have to. 


On Thu, Sep 17, 2020, 3:27 PM John Beatty <jebeatty@...> wrote:

That would help lol.  I pressed the disconnect button on EASY Term screen.

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 3:26 PM
To: main@cmra.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi John,

 

Did you tell it to disconnect or did it do it prematurely on it's own?

 

On Thu, Sep 17, 2020, 3:24 PM John Beatty <jebeatty@...> wrote:

Ryan,

A quick connect from my station to MMJY to you, then a disconnect.  Just for checking purposes…

 

Upper window response----------------

 

*** Connected to station MMJY 9/17/2020 3:17:55 PM

:>c ke5sui-10

MMJY:K0SI-2} Connected to KE5SUI-10

Trying ec2-52-205-99-163.compute-1.amazonaws.com

*** NO0I-15 Connected to CMS

[WL2K-5.0-B2FWIHJM$]

;PQ: 99201778

CMS via KE5SUI-10 >

*** Disconnected from station MMJY 9/17/2020 3:19:02 PM

 

 

Lower window response------------------------------

 

1:Fm NO0I To MMJY <SABM P>[15:17:53]

1:Fm MMJY To NO0I <UA F >[15:17:55]

1:Fm NO0I To MMJY <I P R0 S0 pid=F0 Len=12 >[15:18:16]

c ke5sui-10

 

1:Fm MMJY To NO0I <RR P/F R1 >[15:18:18]

1:Fm NO0I-15 To KE5SUI-10 <SABM P>[15:18:18]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:18:19]

1:Fm MMJY To NO0I <I R1 S0 pid=F0 Len=36 >[15:18:20]

MMJY:K0SI-2} Connected to KE5SUI-10

 

1:Fm NO0I To MMJY <RR R1 >[15:18:21]

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S0 pid=F0 Len=49 >[15:18:22]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R1 >[15:18:23]

1:Fm MMJY To NO0I <I R1 S1 pid=F0 Len=49 >[15:18:24]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I To MMJY <RR R2 >[15:18:24]

1:Fm KE5SUI-10 To NO0I-15 <I R0 S1 pid=F0 Len=29 >[15:18:25]

*** NO0I-15 Connected to CMS

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S2 pid=F0 Len=21 >[15:18:26]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S3 pid=F0 Len=14 >[15:18:26]

;PQ: 99201778

 

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S4 pid=F0 Len=20 >[15:18:26]

CMS via KE5SUI-10 >

 

1:Fm MMJY To NO0I <I R1 S2 pid=F0 Len=29 >[15:18:27]

*** NO0I-15 Connected to CMS

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R5 >[15:18:27]

1:Fm NO0I To MMJY <RR R3 >[15:18:28]

1:Fm MMJY To NO0I <I R1 S3 pid=F0 Len=21 >[15:18:29]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm MMJY To NO0I <I R1 S4 pid=F0 Len=14 >[15:18:29]

;PQ: 99201778

 

1:Fm NO0I To MMJY <RR R5 >[15:18:29]

1:Fm MMJY To NO0I <I R1 S5 pid=F0 Len=20 >[15:18:31]

CMS via KE5SUI-10 >

 

1:Fm NO0I To MMJY <RR R6 >[15:18:31]

1:Fm NO0I To MMJY <DISC P>[15:19:02]

1:Fm MMJY To NO0I <UA F >[15:19:03]

1:Fm NO0I-15 To KE5SUI-10 <DISC P>[15:19:03]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:19:06]

 

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 2:41 PM
To: main@CMRA.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi all,

Sorry to keep bringing this up but it seems like the problem isn't with K0SI-10, it may be with MMJY or MJEF. I went through the trouble to configure my bpq node as a RMS gateway on KE5SUI-10, and I have the same trouble connecting to it through MMJY or MJEF. For some reason MMJY and MJEF are both sending disconnect packets that I didn't tell them to before the transaction is complete.

If anyone has an intimate knowledge of packet radio I'd love to get their thoughts on the logs that have been posted in this thread, or some troubleshooting steps/ideal winlink settings. If anyone else can test connecting to K0SI-10 or KE5SUI-10 via MMJY or MJEF on 145.070 (instructions on how to do that also in this thread) to see if they have the same problems I'd also appreciate that as it could help narrow down if it's just me or not. 

Sorry for any unnecessary trips to the K0SI-10 gateway anyone may have taken. 

73's
KE5SUI

73's


Re: K0SI packet down?

John Beatty
 

That would help lol.  I pressed the disconnect button on EASY Term screen.

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 3:26 PM
To: main@cmra.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi John,

 

Did you tell it to disconnect or did it do it prematurely on it's own?

 

On Thu, Sep 17, 2020, 3:24 PM John Beatty <jebeatty@...> wrote:

Ryan,

A quick connect from my station to MMJY to you, then a disconnect.  Just for checking purposes…

 

Upper window response----------------

 

*** Connected to station MMJY 9/17/2020 3:17:55 PM

:>c ke5sui-10

MMJY:K0SI-2} Connected to KE5SUI-10

Trying ec2-52-205-99-163.compute-1.amazonaws.com

*** NO0I-15 Connected to CMS

[WL2K-5.0-B2FWIHJM$]

;PQ: 99201778

CMS via KE5SUI-10 >

*** Disconnected from station MMJY 9/17/2020 3:19:02 PM

 

 

Lower window response------------------------------

 

1:Fm NO0I To MMJY <SABM P>[15:17:53]

1:Fm MMJY To NO0I <UA F >[15:17:55]

1:Fm NO0I To MMJY <I P R0 S0 pid=F0 Len=12 >[15:18:16]

c ke5sui-10

 

1:Fm MMJY To NO0I <RR P/F R1 >[15:18:18]

1:Fm NO0I-15 To KE5SUI-10 <SABM P>[15:18:18]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:18:19]

1:Fm MMJY To NO0I <I R1 S0 pid=F0 Len=36 >[15:18:20]

MMJY:K0SI-2} Connected to KE5SUI-10

 

1:Fm NO0I To MMJY <RR R1 >[15:18:21]

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S0 pid=F0 Len=49 >[15:18:22]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R1 >[15:18:23]

1:Fm MMJY To NO0I <I R1 S1 pid=F0 Len=49 >[15:18:24]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I To MMJY <RR R2 >[15:18:24]

1:Fm KE5SUI-10 To NO0I-15 <I R0 S1 pid=F0 Len=29 >[15:18:25]

*** NO0I-15 Connected to CMS

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S2 pid=F0 Len=21 >[15:18:26]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S3 pid=F0 Len=14 >[15:18:26]

;PQ: 99201778

 

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S4 pid=F0 Len=20 >[15:18:26]

CMS via KE5SUI-10 >

 

1:Fm MMJY To NO0I <I R1 S2 pid=F0 Len=29 >[15:18:27]

*** NO0I-15 Connected to CMS

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R5 >[15:18:27]

1:Fm NO0I To MMJY <RR R3 >[15:18:28]

1:Fm MMJY To NO0I <I R1 S3 pid=F0 Len=21 >[15:18:29]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm MMJY To NO0I <I R1 S4 pid=F0 Len=14 >[15:18:29]

;PQ: 99201778

 

1:Fm NO0I To MMJY <RR R5 >[15:18:29]

1:Fm MMJY To NO0I <I R1 S5 pid=F0 Len=20 >[15:18:31]

CMS via KE5SUI-10 >

 

1:Fm NO0I To MMJY <RR R6 >[15:18:31]

1:Fm NO0I To MMJY <DISC P>[15:19:02]

1:Fm MMJY To NO0I <UA F >[15:19:03]

1:Fm NO0I-15 To KE5SUI-10 <DISC P>[15:19:03]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:19:06]

 

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 2:41 PM
To: main@CMRA.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi all,

Sorry to keep bringing this up but it seems like the problem isn't with K0SI-10, it may be with MMJY or MJEF. I went through the trouble to configure my bpq node as a RMS gateway on KE5SUI-10, and I have the same trouble connecting to it through MMJY or MJEF. For some reason MMJY and MJEF are both sending disconnect packets that I didn't tell them to before the transaction is complete.

If anyone has an intimate knowledge of packet radio I'd love to get their thoughts on the logs that have been posted in this thread, or some troubleshooting steps/ideal winlink settings. If anyone else can test connecting to K0SI-10 or KE5SUI-10 via MMJY or MJEF on 145.070 (instructions on how to do that also in this thread) to see if they have the same problems I'd also appreciate that as it could help narrow down if it's just me or not. 

Sorry for any unnecessary trips to the K0SI-10 gateway anyone may have taken. 

73's
KE5SUI

73's


Re: K0SI packet down?

Ryan Raney
 

Hi John,

Did you tell it to disconnect or did it do it prematurely on it's own?

On Thu, Sep 17, 2020, 3:24 PM John Beatty <jebeatty@...> wrote:

Ryan,

A quick connect from my station to MMJY to you, then a disconnect.  Just for checking purposes…

 

Upper window response----------------

 

*** Connected to station MMJY 9/17/2020 3:17:55 PM

:>c ke5sui-10

MMJY:K0SI-2} Connected to KE5SUI-10

Trying ec2-52-205-99-163.compute-1.amazonaws.com

*** NO0I-15 Connected to CMS

[WL2K-5.0-B2FWIHJM$]

;PQ: 99201778

CMS via KE5SUI-10 >

*** Disconnected from station MMJY 9/17/2020 3:19:02 PM

 

 

Lower window response------------------------------

 

1:Fm NO0I To MMJY <SABM P>[15:17:53]

1:Fm MMJY To NO0I <UA F >[15:17:55]

1:Fm NO0I To MMJY <I P R0 S0 pid=F0 Len=12 >[15:18:16]

c ke5sui-10

 

1:Fm MMJY To NO0I <RR P/F R1 >[15:18:18]

1:Fm NO0I-15 To KE5SUI-10 <SABM P>[15:18:18]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:18:19]

1:Fm MMJY To NO0I <I R1 S0 pid=F0 Len=36 >[15:18:20]

MMJY:K0SI-2} Connected to KE5SUI-10

 

1:Fm NO0I To MMJY <RR R1 >[15:18:21]

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S0 pid=F0 Len=49 >[15:18:22]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R1 >[15:18:23]

1:Fm MMJY To NO0I <I R1 S1 pid=F0 Len=49 >[15:18:24]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I To MMJY <RR R2 >[15:18:24]

1:Fm KE5SUI-10 To NO0I-15 <I R0 S1 pid=F0 Len=29 >[15:18:25]

*** NO0I-15 Connected to CMS

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S2 pid=F0 Len=21 >[15:18:26]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S3 pid=F0 Len=14 >[15:18:26]

;PQ: 99201778

 

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S4 pid=F0 Len=20 >[15:18:26]

CMS via KE5SUI-10 >

 

1:Fm MMJY To NO0I <I R1 S2 pid=F0 Len=29 >[15:18:27]

*** NO0I-15 Connected to CMS

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R5 >[15:18:27]

1:Fm NO0I To MMJY <RR R3 >[15:18:28]

1:Fm MMJY To NO0I <I R1 S3 pid=F0 Len=21 >[15:18:29]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm MMJY To NO0I <I R1 S4 pid=F0 Len=14 >[15:18:29]

;PQ: 99201778

 

1:Fm NO0I To MMJY <RR R5 >[15:18:29]

1:Fm MMJY To NO0I <I R1 S5 pid=F0 Len=20 >[15:18:31]

CMS via KE5SUI-10 >

 

1:Fm NO0I To MMJY <RR R6 >[15:18:31]

1:Fm NO0I To MMJY <DISC P>[15:19:02]

1:Fm MMJY To NO0I <UA F >[15:19:03]

1:Fm NO0I-15 To KE5SUI-10 <DISC P>[15:19:03]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:19:06]

 

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 2:41 PM
To: main@CMRA.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi all,

Sorry to keep bringing this up but it seems like the problem isn't with K0SI-10, it may be with MMJY or MJEF. I went through the trouble to configure my bpq node as a RMS gateway on KE5SUI-10, and I have the same trouble connecting to it through MMJY or MJEF. For some reason MMJY and MJEF are both sending disconnect packets that I didn't tell them to before the transaction is complete.

If anyone has an intimate knowledge of packet radio I'd love to get their thoughts on the logs that have been posted in this thread, or some troubleshooting steps/ideal winlink settings. If anyone else can test connecting to K0SI-10 or KE5SUI-10 via MMJY or MJEF on 145.070 (instructions on how to do that also in this thread) to see if they have the same problems I'd also appreciate that as it could help narrow down if it's just me or not. 

Sorry for any unnecessary trips to the K0SI-10 gateway anyone may have taken. 

73's
KE5SUI

73's


Re: K0SI packet down?

John Beatty
 

Ryan,

A quick connect from my station to MMJY to you, then a disconnect.  Just for checking purposes…

 

Upper window response----------------

 

*** Connected to station MMJY 9/17/2020 3:17:55 PM

:>c ke5sui-10

MMJY:K0SI-2} Connected to KE5SUI-10

Trying ec2-52-205-99-163.compute-1.amazonaws.com

*** NO0I-15 Connected to CMS

[WL2K-5.0-B2FWIHJM$]

;PQ: 99201778

CMS via KE5SUI-10 >

*** Disconnected from station MMJY 9/17/2020 3:19:02 PM

 

 

Lower window response------------------------------

 

1:Fm NO0I To MMJY <SABM P>[15:17:53]

1:Fm MMJY To NO0I <UA F >[15:17:55]

1:Fm NO0I To MMJY <I P R0 S0 pid=F0 Len=12 >[15:18:16]

c ke5sui-10

 

1:Fm MMJY To NO0I <RR P/F R1 >[15:18:18]

1:Fm NO0I-15 To KE5SUI-10 <SABM P>[15:18:18]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:18:19]

1:Fm MMJY To NO0I <I R1 S0 pid=F0 Len=36 >[15:18:20]

MMJY:K0SI-2} Connected to KE5SUI-10

 

1:Fm NO0I To MMJY <RR R1 >[15:18:21]

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S0 pid=F0 Len=49 >[15:18:22]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R1 >[15:18:23]

1:Fm MMJY To NO0I <I R1 S1 pid=F0 Len=49 >[15:18:24]

Trying ec2-52-205-99-163.compute-1.amazonaws.com

 

1:Fm NO0I To MMJY <RR R2 >[15:18:24]

1:Fm KE5SUI-10 To NO0I-15 <I R0 S1 pid=F0 Len=29 >[15:18:25]

*** NO0I-15 Connected to CMS

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S2 pid=F0 Len=21 >[15:18:26]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm KE5SUI-10 To NO0I-15 <I R0 S3 pid=F0 Len=14 >[15:18:26]

;PQ: 99201778

 

1:Fm KE5SUI-10 To NO0I-15 <I P R0 S4 pid=F0 Len=20 >[15:18:26]

CMS via KE5SUI-10 >

 

1:Fm MMJY To NO0I <I R1 S2 pid=F0 Len=29 >[15:18:27]

*** NO0I-15 Connected to CMS

 

1:Fm NO0I-15 To KE5SUI-10 <RR P/F R5 >[15:18:27]

1:Fm NO0I To MMJY <RR R3 >[15:18:28]

1:Fm MMJY To NO0I <I R1 S3 pid=F0 Len=21 >[15:18:29]

[WL2K-5.0-B2FWIHJM$]

 

1:Fm MMJY To NO0I <I R1 S4 pid=F0 Len=14 >[15:18:29]

;PQ: 99201778

 

1:Fm NO0I To MMJY <RR R5 >[15:18:29]

1:Fm MMJY To NO0I <I R1 S5 pid=F0 Len=20 >[15:18:31]

CMS via KE5SUI-10 >

 

1:Fm NO0I To MMJY <RR R6 >[15:18:31]

1:Fm NO0I To MMJY <DISC P>[15:19:02]

1:Fm MMJY To NO0I <UA F >[15:19:03]

1:Fm NO0I-15 To KE5SUI-10 <DISC P>[15:19:03]

1:Fm KE5SUI-10 To NO0I-15 <UA F >[15:19:06]

 

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Thursday, September 17, 2020 2:41 PM
To: main@CMRA.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Hi all,

Sorry to keep bringing this up but it seems like the problem isn't with K0SI-10, it may be with MMJY or MJEF. I went through the trouble to configure my bpq node as a RMS gateway on KE5SUI-10, and I have the same trouble connecting to it through MMJY or MJEF. For some reason MMJY and MJEF are both sending disconnect packets that I didn't tell them to before the transaction is complete.

If anyone has an intimate knowledge of packet radio I'd love to get their thoughts on the logs that have been posted in this thread, or some troubleshooting steps/ideal winlink settings. If anyone else can test connecting to K0SI-10 or KE5SUI-10 via MMJY or MJEF on 145.070 (instructions on how to do that also in this thread) to see if they have the same problems I'd also appreciate that as it could help narrow down if it's just me or not. 

Sorry for any unnecessary trips to the K0SI-10 gateway anyone may have taken. 

73's
KE5SUI

73's


Re: K0SI packet down?

Ryan Raney
 

Hi all,

Sorry to keep bringing this up but it seems like the problem isn't with K0SI-10, it may be with MMJY or MJEF. I went through the trouble to configure my bpq node as a RMS gateway on KE5SUI-10, and I have the same trouble connecting to it through MMJY or MJEF. For some reason MMJY and MJEF are both sending disconnect packets that I didn't tell them to before the transaction is complete.

If anyone has an intimate knowledge of packet radio I'd love to get their thoughts on the logs that have been posted in this thread, or some troubleshooting steps/ideal winlink settings. If anyone else can test connecting to K0SI-10 or KE5SUI-10 via MMJY or MJEF on 145.070 (instructions on how to do that also in this thread) to see if they have the same problems I'd also appreciate that as it could help narrow down if it's just me or not. 

Sorry for any unnecessary trips to the K0SI-10 gateway anyone may have taken. 

73's
KE5SUI

73's


Re: K0SI packet down?

John Beatty
 

I would like a packet round table/chat net.  I’m in.

73, NO0I

 

 

From: main@CMRA.groups.io <main@CMRA.groups.io> On Behalf Of Ryan Raney
Sent: Wednesday, September 16, 2020 7:09 PM
To: main@cmra.groups.io
Subject: Re: [CMRA] K0SI packet down?

 

Excellent, I saw you join the chat. I said hi but looks like you left before you saw it. I'll work on making the connect message a bit more intuitive for first time users soon. 

 

Thanks for giving it a go. If there's any interest in doing a packet net in the node chat at some point in the future that could be interesting. 

 

I'm working on getting a friend in Moberly up and running on packet so hopefully we'll have another player soon

 

73

 

On Wed, Sep 16, 2020, 7:06 PM John Beatty <jebeatty@...> wrote:

Hi Ryan, I made it.  I haven't been on packet in like forever.  But the circuit from my qth to you via MMJY is aces. Using Easy Term.

Will try again soon.  73, John - NO0I

On Sep 16, 2020, at 5:26 PM, Ryan Raney <ryanraney@...> wrote:

Hi John, feel free to jump on any time. It should be reachable reliably from MMJY almost 24/7 right now unless I'm messing around with settings over here. The SSID is KE5SUI-14, I've had good luck using EasyTerm by UZ7HO or using AGWterm, with either going to my soundcard tnc software. 

 

On Wed, Sep 16, 2020, 4:36 PM John Beatty <jebeatty@...> wrote:

Ryan, I am currently away from my shack.  But I would like to test connecting to your bbs for your and my benefit. I am typically successful connecting via MMJY.  I can give it a shot later this evening. 

Thanks, John - NO0I

On Sep 16, 2020, at 4:07 PM, Ryan Raney <ryanraney@...> wrote:

I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Ryan Raney
 

Excellent, I saw you join the chat. I said hi but looks like you left before you saw it. I'll work on making the connect message a bit more intuitive for first time users soon. 

Thanks for giving it a go. If there's any interest in doing a packet net in the node chat at some point in the future that could be interesting. 

I'm working on getting a friend in Moberly up and running on packet so hopefully we'll have another player soon

73

On Wed, Sep 16, 2020, 7:06 PM John Beatty <jebeatty@...> wrote:
Hi Ryan, I made it.  I haven't been on packet in like forever.  But the circuit from my qth to you via MMJY is aces. Using Easy Term.

Will try again soon.  73, John - NO0I

On Sep 16, 2020, at 5:26 PM, Ryan Raney <ryanraney@...> wrote:
Hi John, feel free to jump on any time. It should be reachable reliably from MMJY almost 24/7 right now unless I'm messing around with settings over here. The SSID is KE5SUI-14, I've had good luck using EasyTerm by UZ7HO or using AGWterm, with either going to my soundcard tnc software. 

On Wed, Sep 16, 2020, 4:36 PM John Beatty <jebeatty@...> wrote:
Ryan, I am currently away from my shack.  But I would like to test connecting to your bbs for your and my benefit. I am typically successful connecting via MMJY.  I can give it a shot later this evening. 
Thanks, John - NO0I

On Sep 16, 2020, at 4:07 PM, Ryan Raney <ryanraney@...> wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

John Beatty
 

Hi Ryan, I made it.  I haven't been on packet in like forever.  But the circuit from my qth to you via MMJY is aces. Using Easy Term.

Will try again soon.  73, John - NO0I

On Sep 16, 2020, at 5:26 PM, Ryan Raney <ryanraney@...> wrote:
Hi John, feel free to jump on any time. It should be reachable reliably from MMJY almost 24/7 right now unless I'm messing around with settings over here. The SSID is KE5SUI-14, I've had good luck using EasyTerm by UZ7HO or using AGWterm, with either going to my soundcard tnc software. 

On Wed, Sep 16, 2020, 4:36 PM John Beatty <jebeatty@...> wrote:
Ryan, I am currently away from my shack.  But I would like to test connecting to your bbs for your and my benefit. I am typically successful connecting via MMJY.  I can give it a shot later this evening. 
Thanks, John - NO0I

On Sep 16, 2020, at 4:07 PM, Ryan Raney <ryanraney@...> wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Ryan Raney
 

Hi Fred,

MMJY is a mersweb packet node in Centralia on 145.070. it's linked to a similar node in Jefferson City called MJEF on the same frequency. There used to be two other nodes that would make the trip over to STL but they appear do be down indefinitely.

These nodes allow low power stations to relay through them to reach nodes or winlink servers they couldn't reach otherwise. For instance you can connect to my packet node KE5SUI-14 through them if you can't hit it directly. 

To send your winlink packets through MMJY you'll have to change your connection type from direct to script. Then the line below will no longer be greyed out. Next click add script. A new window will pop up, this is where we'll set up the connection script to jump through the node. Go ahead and name the script something memorable like K0SI-10 via MMJY. Next in the body of the script enter the following:

C MMJY
CONN
C K0SI-10
CONN

Now click save. Make sure your new script is selected in the connection script drop-down and click start. 

Once you're done with the test remember to set your connection mode back to direct or you will always go through MMJY, which I don't advise unless you have to. 


Thanks!
-Ryan KE5SUI

On Wed, Sep 16, 2020, 5:37 PM Fred Dittrich <fdittric@...> wrote:
Ryan

What is MMJY?

73

Fred AE0FD


At 05:36 PM 9/16/2020, you wrote:
Hi Fred,

Due to terrain and distance i've never been able to hit K0SI-10 directly. If you have a chance could you try through MMJY? 


Re: K0SI packet down?

Fred Dittrich
 

Ryan

What is MMJY?

73

Fred AE0FD


At 05:36 PM 9/16/2020, you wrote:
Hi Fred,

Due to terrain and distance i've never been able to hit K0SI-10 directly. If you have a chance could you try through MMJY? 


Re: K0SI packet down?

Ryan Raney
 

Hi Fred, 

Due to terrain and distance i've never been able to hit K0SI-10 directly. If you have a chance could you try through MMJY? 


Re: K0SI packet down?

Fred Dittrich
 

Ryan

Directly.

73

Fred AE0FD


At 05:24 PM 9/16/2020, you wrote:
Hi Fred,

Did you connect to K0SI-10 directly or through MMJY / MJEF?Â

On Wed, Sep 16, 2020, 4:34 PM Fred Dittrich <fdittric@...> wrote:
Ryan

FYI, I just connected to K0SI-10 the first time. Hope this helps in your diagnosis.

73

Fred AE0FD


At 04:07 PM 9/16/2020, you wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry.

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me.

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Ryan Raney
 

Hi John, feel free to jump on any time. It should be reachable reliably from MMJY almost 24/7 right now unless I'm messing around with settings over here. The SSID is KE5SUI-14, I've had good luck using EasyTerm by UZ7HO or using AGWterm, with either going to my soundcard tnc software. 


On Wed, Sep 16, 2020, 4:36 PM John Beatty <jebeatty@...> wrote:
Ryan, I am currently away from my shack.  But I would like to test connecting to your bbs for your and my benefit. I am typically successful connecting via MMJY.  I can give it a shot later this evening. 
Thanks, John - NO0I

On Sep 16, 2020, at 4:07 PM, Ryan Raney <ryanraney@...> wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Ryan Raney
 

Hi Fred,

Did you connect to K0SI-10 directly or through MMJY / MJEF? 

On Wed, Sep 16, 2020, 4:34 PM Fred Dittrich <fdittric@...> wrote:
Ryan

FYI, I just connected to K0SI-10 the first time. Hope this helps in your diagnosis.

73

Fred AE0FD


At 04:07 PM 9/16/2020, you wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry.

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me.

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

John Beatty
 

Ryan, I am currently away from my shack.  But I would like to test connecting to your bbs for your and my benefit. I am typically successful connecting via MMJY.  I can give it a shot later this evening. 
Thanks, John - NO0I

On Sep 16, 2020, at 4:07 PM, Ryan Raney <ryanraney@...> wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Fred Dittrich
 

Ryan

FYI, I just connected to K0SI-10 the first time. Hope this helps in your diagnosis.

73

Fred AE0FD


At 04:07 PM 9/16/2020, you wrote:
I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry.

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me.

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan


Re: K0SI packet down?

Ryan Raney
 

I'm still having trouble with K0SI-10, it took over 50 tries yesterday to receive a short message from Bill. Today Its acting even more strange.

Previously while connecting through MJEF or MMJY i could see them send a disconnect to K0SI-10 on my behalf under the call KE5SUI-15, though neither reported it to my winlink client so it sat there and timed out.

Today i'm monitoring my bpq32 node in columbia remotely from jefferson city and i see after my winlink client has timed out K0SI-10 and KE5SUI-15 are going back and forth trying to do God knows what. I get an error that K0SI-10 is busy when I retry. 

Is this a problem only for me? I can't hit K0SI-10 directly and I know I'm probably one of the few using MJEF and MMJY but it's making winlink just about useless for me. 

I'd appreciate any help anyone can provide

Thanks!
-KE5SUI Ryan

481 - 500 of 4579