Date   

Re: ThumbDV Issue

Eduardo Gallegos <xe2jeg@...>
 

Thanks John.

Regards

Eduardo
XE2JEG


On Jun 3, 2019, at 3:20 PM, John D Hays - K7VE <john@...> wrote:

Forwarded to Anna, NH6Z, Buster's author.

On Mon, Jun 3, 2019, 14:17 Eduardo Gallegos via Groups.Io <xe2jeg=me.com@groups.io> wrote:
Hi...

I am running a ThumbDV device on a Mac with Buster software but now I can’t connect to few Reflectors like 1C, 12A or 30C.  I CAN connect to few others but not he ones that I mention.

I am a register user on D-Star.

Any help will be greatly appreciated.

Regards,

Eduardo Gallegos
XE2JEG





Re: paclink-unix incoming messages

Keith Williamson
 

Sorry..I had cleaned it out again.

The email message you sent is now in the outbox:

pi@Compass:/usr/local/var/wl2k/outbox $
pi@Compass:/usr/local/var/wl2k/outbox $ cat BWU7Q_KF7DRV
Mid: BWU7Q_KF7DRV
Date: 2019/06/04 05:55
Type: Private
From: SMTP:N7NIX@...
To: SMTP:KF7DRV@...
Subject: Re: //WL2K Compass plu 06/03/19, size: 32, #0
Mbo: N7NIX
Body: 185

I received both of your test messages sent just before 5pm Monday.
/Basil

On Mon, Jun 03, 2019 at 11:50:00PM +0000, KF7DRV@... wrote:
> Sent on: 06/03 16:50:42 PDT
> /pi
pi@Compass:/usr/local/var/wl2k/outbox $


Repeating the directory listings:

pi@Compass:~ $ ls -alt /usr/local/var/wl2k/outbox
total 12
drwxrwsr-x 2 pi mail 4096 Jun  4 07:28 .
-rw------- 1 pi mail  383 Jun  4 07:28 BWU7Q_KF7DRV
drwxrwsr-x 3 pi mail 4096 Jun  3 16:19 ..
pi@Compass:~ $
pi@Compass:~ $ ls -alt ~/Mail/
total 48
drwxr-xr-x 40 pi pi 4096 Jun  4 07:23 ..
drwxr-xr-x  2 pi pi 4096 Jun  3 16:53 new
drwxr-xr-x  2 pi pi 4096 Jun  3 16:50 tmp
drwxr-xr-x 12 pi pi 4096 Jun  3 16:13 .
-rw-r--r--  1 pi pi    0 Jun  3 16:13 .mh_sequences
drwxr-xr-x  5 pi pi 4096 Jun  3 16:12 sent
drwxr-xr-x  5 pi pi 4096 Jun  3 16:12 inbox
drwx------  2 pi pi 4096 Jun  3 14:57 queue
drwxr-xr-x  5 pi pi 4096 Jun  3 12:36 trash
drwx------  2 pi pi 4096 Jun  3 11:00 draft
drwxr-xr-x  5 pi pi 4096 Jun  3 09:05 attachments
drwxr-xr-x  5 pi pi 4096 Jun  3 09:05 drafts
drwxr-xr-x  2 pi pi 4096 Jun  3 09:05 cur
pi@Compass:~ $


There are no messages in mutt. Is there a mutt command to retrieve email?

-Keith

On Tue, Jun 4, 2019 at 7:35 AM Basil Gunn <basil@...> wrote:

There are no incoming messages in your outbox.
Why do you think there are?

Can you reply to the winlink email I sent to you with mutt?

/Basil

Keith Williamson <hkwilliamson@...> writes:

> Here you go:
>
> pi@Compass:~ $ ls -alt /usr/local/var/wl2k/outbox
> total 8
> drwxrwsr-x 2 pi mail 4096 Jun  3 16:50 .
> drwxrwsr-x 3 pi mail 4096 Jun  3 16:19 ..
> pi@Compass:~ $ ls -alt ~/Mail/
> total 48
> drwxr-xr-x  2 pi pi 4096 Jun  3 16:53 new
> drwxr-xr-x  2 pi pi 4096 Jun  3 16:50 tmp
> drwxr-xr-x 12 pi pi 4096 Jun  3 16:13 .
> -rw-r--r--  1 pi pi    0 Jun  3 16:13 .mh_sequences
> drwxr-xr-x  5 pi pi 4096 Jun  3 16:12 sent
> drwxr-xr-x  5 pi pi 4096 Jun  3 16:12 inbox
> drwxr-xr-x 39 pi pi 4096 Jun  3 16:00 ..
> drwx------  2 pi pi 4096 Jun  3 14:57 queue
> drwxr-xr-x  5 pi pi 4096 Jun  3 12:36 trash
> drwx------  2 pi pi 4096 Jun  3 11:00 draft
> drwxr-xr-x  5 pi pi 4096 Jun  3 09:05 attachments
> drwxr-xr-x  5 pi pi 4096 Jun  3 09:05 drafts
> drwxr-xr-x  2 pi pi 4096 Jun  3 09:05 cur
> pi@Compass:~ $
>
> -Keith
>
> On Mon, Jun 3, 2019 at 10:43 PM Basil Gunn <basil@...> wrote:
>
>> With respect to incoming messages ending up in
>> /usr/local/var/wl2k/output/, I don't know how to fix that. I thought that
>> postfix was configured correctly by the scripts.
>>
>> It is. I just tried a new install & things work the way I expect. Send me
>> the output of these commands.
>>
>> ls -alt /usr/local/var/wl2k/outbox
>> ls -alt ~/Mail/
>>
>> Is it possible that building the latest paclink-unix broke the postfix
>> config? No /Basil
>>
>>
>>
>>
>
>





Re: auto-rmsgw-find

Keith Williamson
 

Hi Basil,

No gps..just UDRC.

However, looks like this is working correctly now:

pi@Compass:~/auto-rmsgw-find $ rm ~/tmp/rmsgwprox.*
pi@Compass:~/auto-rmsgw-find $ ./wlgw-check.sh -g CN88tu
Using existing /home/pi/tmp/rmsgw_stats.log

Refreshing RMS List

RMS GW proximity file has changed
wc: /home/pi/tmp/rmsgwprox.bak: No such file or directory
New proximity file has 12 entries, old file has
Using VFOA as data radio
In Mem channel mode
Current Chan: 3, name: LKOUT, chan freq: 146.5, Frequency: 144930000

Start: 2019 06 04 07:27:02 PDT: grid: CN88tu, debug: , GW list refresh: true, connect: true, cron: false

Chan Conn
RMS GW    Freq Dist Name Index Stat Stat Time  Conn
Connected to AX.25 stack
Child process
wl2kax25: ---

wl2kax25: <[WL2K-5.0-B2FWIHJM$]
wl2kax25: sid [WL2K-5.0-B2FWIHJM$] inboundsidcodes -B2FWIHJM$
wl2kax25: <;PQ: 14728660
wl2kax25: Challenge received: 14728660
wl2kax25: <CMS via KC7OAS >
wl2kax25: >[UnixLINK-0.8-B2FIHM$]
wl2kax25: >;PR: 20191930
wl2kax25: >; KC7OAS-10 DE KF7DRV QTC 0
wl2kax25: >FF
wl2kax25: <;PM: KF7DRV 7GF5QC_N7NIX 280 N7NIX@... Re: //WL2K Compass plu 06/03/19, size: 32, #0 [92]
wl2kax25: <FC EM 7GF5QC_N7NIX 334 280 0 [28]
wl2kax25: proposal code C type E mid 7GF5QC_N7NIX usize 334 csize 280 next (nil) path (null) ubuf (nil) cbuf (nil)
wl2kax25: <F> 74 [5]
wl2kax25: sentcksum=74 proposalcksum=74
wl2kax25: 1 proposal received
wl2kax25: >FS Y
wl2kax25: title: Re: //WL2K Compass plu 06/03/19, size: 32, #0
wl2kax25: offset: 0
wl2kax25: STX
wl2kax25: len 250
wl2kax25: STX
wl2kax25: len 30
wl2kax25: EOT
wl2kax25: extracting...
wl2kax25: calling sendmail for delivery: /usr/sbin/sendmail -bm hkwilliamson@...
wl2kax25: delivery completed
wl2kax25: >FF
wl2kax25: <FQ [2]
Child process exiting
EOF on child fd, terminating communications loop.
Closing ax25 connection
Child exit status: 0
Waiting for AX25 peer ... timeout
KC7OAS-10   144950000 8 NET-12          n/a  OK 47   4
Connected to AX.25 stack
Child process
wl2kax25: ---
 outbound proposal list
wl2kax25: proposal code C type E mid STLRF_KF7DRV usize 383 csize 300 next (nil) path STLRF_KF7DRV ubuf 0xf78ba0 cbuf 0xf649b8
wl2kax25: <W7ECG-10 - Linux RMS Gateway 2.5.0 Dec 21 2018 (CN88rt)    **** WECG RMS Gateway ****    INFO: Host Name cms.winlink.org, Port 8772
wl2kax25: <Connected
wl2kax25: <[WL2K-5.0-B2FWIHJM$]
wl2kax25: sid [WL2K-5.0-B2FWIHJM$] inboundsidcodes -B2FWIHJM$
wl2kax25: <;PQ: 41357213
wl2kax25: Challenge received: 41357213
wl2kax25: <CMS via W7ECG-10 >
wl2kax25: >[UnixLINK-0.8-B2FIHM$]
wl2kax25: >;PR: 65853655
wl2kax25: >; W7ECG-10 DE KF7DRV QTC 1
wl2kax25: >FC EM STLRF_KF7DRV 383 300 0
wl2kax25: >F> 39
wl2kax25: <FS Y
wl2kax25: transmitting [Re: //WL2K Compass plu 06/03/19, size: 32, #0] [offset 0]
wl2kax25: ... 300
wl2kax25: ... 45
wl2kax25: <FF [2]
wl2kax25: DELETING PROPOSAL:
wl2kax25: proposal code C type E mid STLRF_KF7DRV usize 383 csize 300 next (nil) path STLRF_KF7DRV ubuf 0xf78ba0 cbuf 0xf649b8
wl2kax25: >FQ
Child process exiting
EOF on child fd, terminating communications loop.
Closing ax25 connection
Child exit status: 0
Waiting for AX25 peer ... disconnected
W7ECG-10    144930000 8 NET-17          n/a  OK 26   4
Connected to AX.25 stack
Child process
wl2kax25: ---

wl2kax25: <KF7VOL-10 - Linux RMS Gateway 2.5.0 Dec 21 2018 (CN88SX)    **** Keyed Up RMS Gateway ****    INFO: Host Name cms.winlink.org, Port 8772
wl2kax25: <Connected
wl2kax25: <[WL2K-5.0-B2FWIHJM$]
wl2kax25: sid [WL2K-5.0-B2FWIHJM$] inboundsidcodes -B2FWIHJM$
wl2kax25: <;PQ: 71451109
wl2kax25: Challenge received: 71451109
wl2kax25: <CMS via KF7VOL-10 >
wl2kax25: >[UnixLINK-0.8-B2FIHM$]
wl2kax25: >;PR: 29618764
wl2kax25: >; KF7VOL-10 DE KF7DRV QTC 0
wl2kax25: >FF
wl2kax25: <;PM: KF7DRV STLRF_KF7DRV 279 N7NIX@... Re: //WL2K Compass plu 06/03/19, size: 32, #0 [92]
wl2kax25: <FC EM STLRF_KF7DRV 334 279 0 [28]
wl2kax25: proposal code C type E mid STLRF_KF7DRV usize 334 csize 279 next (nil) path (null) ubuf (nil) cbuf (nil)
wl2kax25: <F> 2E [5]
wl2kax25: sentcksum=2E proposalcksum=2E
wl2kax25: 1 proposal received
wl2kax25: >FS Y
wl2kax25: title: Re: //WL2K Compass plu 06/03/19, size: 32, #0
wl2kax25: offset: 0
wl2kax25: STX
wl2kax25: len 250
wl2kax25: STX
wl2kax25: len 29
wl2kax25: EOT
wl2kax25: extracting...
wl2kax25: calling sendmail for delivery: /usr/sbin/sendmail -bm hkwilliamson@...
wl2kax25: delivery completed
wl2kax25: >FF
wl2kax25: <FQ [2]
Child process exiting
EOF on child fd, terminating communications loop.
Closing ax25 connection
Child exit status: 0
Waiting for AX25 peer ... disconnected
KF7VOL-10   145010000 9 NET111          n/a  OK 26   1
connect(): Connection timed out

Call to wl2kax25 timed out

NG2G-10     144990000 9 NET-11          n/a  to 22   1
connect(): Connection timed out

Call to wl2kax25 timed out

W7RE-10     147420000 12 unknown          Err  to 23   0
VA7TSA      7101000 15 unknown       Unqual n/a  0   0
  Pause for a bit, gateway count: 5, modulo 5 0
VA7TSA      14109000 15 unknown       Unqual n/a  0   0
  Pause for a bit, gateway count: 5, modulo 5 0
connect(): Connection timed out

Call to wl2kax25 timed out

VA7TSA-10   144970000 15 NET-15          n/a  to 23   0
connect(): Connection timed out

Call to wl2kax25 timed out

VA7TSA-10   145030000 15 NET112          n/a  to 23   0
connect(): Connection timed out

Call to wl2kax25 timed out

VE7ECC-10   144360000 15 unknown          Err  to 21   0
connect(): Connection timed out

Call to wl2kax25 timed out

W7BPD-10    145630000 17 NET-13          n/a  to 22   1
connect(): Connection timed out

Call to wl2kax25 timed out

W7BPD-11    145630000 17 NET-13          n/a  to 22   2
  Pause for a bit, gateway count: 10, modulo 5 0
Number of gateways: in array: 14, in list 12 /home/pi/tmp/rmsgwprox.txt

Finish: 2019 06 04 07:31:23 PDT: Elapsed time: 4 min, 21 secs,  Found 10 RMS Gateways, connected: 3

Setting radio back to original memory channel 3
pi@Compass:~/auto-rmsgw-find $
pi@Compass:~/auto-rmsgw-find $
pi@Compass:~/auto-rmsgw-find $ ./show_log.sh
Using date: 2019 06 04, starting at line number: 146, numb_lines: 17
Start: 2019 06 04 07:27:02 PDT: grid: CN88tu, debug: , GW list refresh: true, connect: true, cron: false

Chan Conn
RMS GW    Freq Dist Name Index Stat Stat Time  Conn
KC7OAS-10   144950000 8 NET-12          n/a  OK 47   4
W7ECG-10    144930000 8 NET-17          n/a  OK 26   4
KF7VOL-10   145010000 9 NET111          n/a  OK 26   1
NG2G-10     144990000 9 NET-11          n/a  to 22   1
W7RE-10     147420000 12 unknown          Err  to 23   0
VA7TSA      7101000 15 unknown       Unqual n/a  0   0
VA7TSA      14109000 15 unknown       Unqual n/a  0   0
VA7TSA-10   144970000 15 NET-15          n/a  to 23   0
VA7TSA-10   145030000 15 NET112          n/a  to 23   0
VE7ECC-10   144360000 15 unknown          Err  to 21   0
W7BPD-10    145630000 17 NET-13          n/a  to 22   1
W7BPD-11    145630000 17 NET-13          n/a  to 22   2
Finish: 2019 06 04 07:31:23 PDT: Elapsed time: 4 min, 21 secs,  Found 10 RMS Gateways, connected: 3
pi@Compass:~/auto-rmsgw-find $
pi@Compass:~/auto-rmsgw-find $
pi@Compass:~/auto-rmsgw-find $ rmslist.sh
Proximity file is: 0 hours 7 minute(s), 40 seconds old
Using existing proximity file with unknown grid_square

  Callsign       Frequency  Distance    Baud
 KC7OAS-10 144950000 8 1200
 W7ECG-10   144930000 8 1200
 KF7VOL-10 145010000 9 1200
 NG2G-10   144990000 9 1200
 W7RE-10   147420000 12 1200
 VA7TSA       7101000 15 600
 VA7TSA      14109000 15 600
 VA7TSA-10 144970000 15 1200
 VA7TSA-10 145030000 15 1200
 VE7ECC-10 144360000 15 1200
 W7BPD-10   145630000 17 1200
 W7BPD-11   145630000 17 1200
pi@Compass:~/auto-rmsgw-find $
pi@Compass:~/auto-rmsgw-find $
pi@Compass:~/auto-rmsgw-find $


-Keith

Virus-free. www.avg.com

On Mon, Jun 3, 2019 at 10:35 PM Basil Gunn <basil@...> wrote:

Keith,

Are you running with gps enabled? Do you have a gps antenna installed?

Update to the latest scripts cd cd n7nix git pull cd config ./bin_refresh.sh

Then run these 3 scripts and show me the console output of everything Change GWDIST=20 in wlgw-check.sh to make it run a little quicker.

cd cd auto-rmsgw-find rm ~/tmp/rmsgwprox.*

./wlgw-check.sh -g CN88tu ./show-log.sh rmslist.sh

/Basil


Re: paclink-unix incoming messages

Basil Gunn
 

There are no incoming messages in your outbox.
Why do you think there are?

Can you reply to the winlink email I sent to you with mutt?

/Basil

Keith Williamson <hkwilliamson@...> writes:

Here you go:

pi@Compass:~ $ ls -alt /usr/local/var/wl2k/outbox
total 8
drwxrwsr-x 2 pi mail 4096 Jun 3 16:50 .
drwxrwsr-x 3 pi mail 4096 Jun 3 16:19 ..
pi@Compass:~ $ ls -alt ~/Mail/
total 48
drwxr-xr-x 2 pi pi 4096 Jun 3 16:53 new
drwxr-xr-x 2 pi pi 4096 Jun 3 16:50 tmp
drwxr-xr-x 12 pi pi 4096 Jun 3 16:13 .
-rw-r--r-- 1 pi pi 0 Jun 3 16:13 .mh_sequences
drwxr-xr-x 5 pi pi 4096 Jun 3 16:12 sent
drwxr-xr-x 5 pi pi 4096 Jun 3 16:12 inbox
drwxr-xr-x 39 pi pi 4096 Jun 3 16:00 ..
drwx------ 2 pi pi 4096 Jun 3 14:57 queue
drwxr-xr-x 5 pi pi 4096 Jun 3 12:36 trash
drwx------ 2 pi pi 4096 Jun 3 11:00 draft
drwxr-xr-x 5 pi pi 4096 Jun 3 09:05 attachments
drwxr-xr-x 5 pi pi 4096 Jun 3 09:05 drafts
drwxr-xr-x 2 pi pi 4096 Jun 3 09:05 cur
pi@Compass:~ $

-Keith

On Mon, Jun 3, 2019 at 10:43 PM Basil Gunn <@basil860> wrote:

With respect to incoming messages ending up in
/usr/local/var/wl2k/output/, I don't know how to fix that. I thought that
postfix was configured correctly by the scripts.

It is. I just tried a new install & things work the way I expect. Send me
the output of these commands.

ls -alt /usr/local/var/wl2k/outbox
ls -alt ~/Mail/

Is it possible that building the latest paclink-unix broke the postfix
config? No /Basil




Re: paclink-unix incoming messages

Keith Williamson
 

Here you go:

pi@Compass:~ $ ls -alt /usr/local/var/wl2k/outbox
total 8
drwxrwsr-x 2 pi mail 4096 Jun  3 16:50 .
drwxrwsr-x 3 pi mail 4096 Jun  3 16:19 ..
pi@Compass:~ $ ls -alt ~/Mail/
total 48
drwxr-xr-x  2 pi pi 4096 Jun  3 16:53 new
drwxr-xr-x  2 pi pi 4096 Jun  3 16:50 tmp
drwxr-xr-x 12 pi pi 4096 Jun  3 16:13 .
-rw-r--r--  1 pi pi    0 Jun  3 16:13 .mh_sequences
drwxr-xr-x  5 pi pi 4096 Jun  3 16:12 sent
drwxr-xr-x  5 pi pi 4096 Jun  3 16:12 inbox
drwxr-xr-x 39 pi pi 4096 Jun  3 16:00 ..
drwx------  2 pi pi 4096 Jun  3 14:57 queue
drwxr-xr-x  5 pi pi 4096 Jun  3 12:36 trash
drwx------  2 pi pi 4096 Jun  3 11:00 draft
drwxr-xr-x  5 pi pi 4096 Jun  3 09:05 attachments
drwxr-xr-x  5 pi pi 4096 Jun  3 09:05 drafts
drwxr-xr-x  2 pi pi 4096 Jun  3 09:05 cur
pi@Compass:~ $

-Keith

On Mon, Jun 3, 2019 at 10:43 PM Basil Gunn <basil@...> wrote:

With respect to incoming messages ending up in /usr/local/var/wl2k/output/, I don't know how to fix that. I thought that postfix was configured correctly by the scripts.

It is. I just tried a new install & things work the way I expect. Send me the output of these commands.

ls -alt /usr/local/var/wl2k/outbox
ls -alt ~/Mail/

Is it possible that building the latest paclink-unix broke the postfix config? No /Basil


paclink-unix incoming messages

Basil Gunn
 

With respect to incoming messages ending up in /usr/local/var/wl2k/output/, I don't know how to fix that. I thought that postfix was configured correctly by the scripts.

It is. I just tried a new install & things work the way I expect. Send me the output of these commands.

ls -alt /usr/local/var/wl2k/outbox
ls -alt ~/Mail/

Is it possible that building the latest paclink-unix broke the postfix config? No /Basil


Re: Getting started with paclink-unix

Basil Gunn
 

Splitting this into 2 threads. One for auto-rmsgw-find and the other for
paclink-unix incoming messages.
/Basil

Keith Williamson <hkwilliamson@...> writes:

Hi Basil,

I deleted the rmsgwprox* files in ~/tmp and ran wlgw-check.sh -g CN88tu.
Here is the resultant output from show_log.sh:


Start: 2019 06 03 17:01:54 PDT: grid: CN88tu, debug: , GW list refresh:
true, connect: true, cron: false

Chan Conn
RMS GW Freq Dist Name Index Stat Stat Time Conn
KF7FIT-10 223780000 0 NET-21 Unqual n/a 0 0
N7NIX-10 144910000 0 NET-16 Unqual n/a 0 0
K7KCA-10 440125000 3 NET-45 n/a to 0 0
KE7KML-10 223780000 3 NET-21 Unqual n/a 1 0
AF4PM-10 145690000 4 NET-14 n/a to 22 1
AF5TR-10 145690000 11 NET-14 n/a to 21 1
AE7LW-10 145050000 16 NET113 n/a to 22 1
AE7LW-10 440950000 16 NET-46 n/a to 1 0
KD7X-10 145630000 16 NET-13 n/a to 21 1
KI7ULA-10 145050000 16 NET113 n/a to 22 1
W0QJM-10 145630000 19 NET-13 n/a to 22 1
WA7GJZ-10 145630000 19 NET-13 n/a to 22 2
WA7GJZ-10 145630000 19 NET-13 n/a to 22 2
NG2G-10 144990000 26 NET-11 n/a to 21 1
W7ECG-10 144930000 28 NET-17 n/a OK 49 3
KC7OAS-10 144950000 33 NET-12 n/a OK 26 3
KG7WFV-10 145630000 35 NET-13 n/a to 21 1
W7BPD-10 145630000 35 NET-13 n/a to 22 1
W7BPD-11 145630000 35 NET-13 n/a OK 33 2
Finish: 2019 06 03 17:07:50 PDT: Elapsed time: 5 min, 56 secs, Found 16
RMS Gateways, connected: 3
pi@Compass:/usr/local/src/auto-rmsgw-find $

With respect to incoming messages ending up in /usr/local/var/wl2k/output/,
I don't know how to fix that. I thought that postfix was configured
correctly by the scripts.

Is it possible that building the latest paclink-unix broke the postfix
config?

cd /usr/local/src/paclink-unix
git pull
./build-all.sh

Thanks,

Keith


On Mon, Jun 3, 2019 at 4:48 PM Basil Gunn <@basil860> wrote:


First figure out how to ssh into your RPi from the same machine you use
for email. I really prefer a cut & paste of console output rather than a
jpg.

I think all of the infrastructure is in place and working. I just can't
get
email working. I followed the instructions for configuring Claws. I chose
the option to use it for my winlink email client (KF7DRV@...).
When
I get to the last screen where I save the config, Claws complains that it
can't connect to "IMAP server: localhost: 143".
Please send the console output of:
netstat -tulpn | grep 143

You may have to reboot your machine after the paclink-unix install to
start the IMAP server.

On a separate note, I have tested wl2kax25 to w7ecg-10, kf7vol-10, and
kc7oad-10. They all answer up fine and terminate normally. However, when
I
run "wlgw-check.sh -g CN88tu", it doesn't appear to honor the -g
argument.
The gateway list it tests appears to be the default list. Here's the
output
from show_log.sh:
I couldn't replicate this problem.
There is a mechanism in rmslist.sh to not interrogate the Winlink server
too frequently. If you have ever run rmslist.sh without any arguments
that may be what you are seeing. Try deleting the rmslist.sh output
files & running wlgw-check.sh again

cd
cd tmp
rm rmsgwprox.*

Because you sent a jpg of the console I couldn't really tell if there was
anything else in the show_log.sh output.

/Basil




auto-rmsgw-find

Basil Gunn
 

Keith,

Are you running with gps enabled? Do you have a gps antenna installed?

Update to the latest scripts cd cd n7nix git pull cd config ./bin_refresh.sh

Then run these 3 scripts and show me the console output of everything Change GWDIST=20 in wlgw-check.sh to make it run a little quicker.

cd cd auto-rmsgw-find rm ~/tmp/rmsgwprox.*

./wlgw-check.sh -g CN88tu ./show-log.sh rmslist.sh

/Basil


Re: Getting started with paclink-unix

Keith Williamson
 

Hi Basil,

I deleted the rmsgwprox* files in ~/tmp and ran wlgw-check.sh -g CN88tu. Here is the resultant output from show_log.sh:


Start: 2019 06 03 17:01:54 PDT: grid: CN88tu, debug: , GW list refresh: true, connect: true, cron: false

Chan Conn
RMS GW    Freq Dist Name Index Stat Stat Time  Conn
KF7FIT-10   223780000 0 NET-21       Unqual n/a  0   0
N7NIX-10    144910000 0 NET-16       Unqual n/a  0   0
K7KCA-10    440125000 3 NET-45          n/a  to  0   0
KE7KML-10   223780000 3 NET-21       Unqual n/a  1   0
AF4PM-10    145690000 4 NET-14          n/a  to 22   1
AF5TR-10    145690000 11 NET-14          n/a  to 21   1
AE7LW-10    145050000 16 NET113          n/a  to 22   1
AE7LW-10    440950000 16 NET-46          n/a  to  1   0
KD7X-10     145630000 16 NET-13          n/a  to 21   1
KI7ULA-10   145050000 16 NET113          n/a  to 22   1
W0QJM-10    145630000 19 NET-13          n/a  to 22   1
WA7GJZ-10   145630000 19 NET-13          n/a  to 22   2
WA7GJZ-10   145630000 19 NET-13          n/a  to 22   2
NG2G-10     144990000 26 NET-11          n/a  to 21   1
W7ECG-10    144930000 28 NET-17          n/a  OK 49   3
KC7OAS-10   144950000 33 NET-12          n/a  OK 26   3
KG7WFV-10   145630000 35 NET-13          n/a  to 21   1
W7BPD-10    145630000 35 NET-13          n/a  to 22   1
W7BPD-11    145630000 35 NET-13          n/a  OK 33   2
Finish: 2019 06 03 17:07:50 PDT: Elapsed time: 5 min, 56 secs,  Found 16 RMS Gateways, connected: 3
pi@Compass:/usr/local/src/auto-rmsgw-find $

With respect to incoming messages ending up in /usr/local/var/wl2k/output/, I don't know how to fix that. I thought that postfix was configured correctly by the scripts.

Is it possible that building the latest paclink-unix broke the postfix config?

cd /usr/local/src/paclink-unix
git pull
./build-all.sh

Thanks,

Keith


On Mon, Jun 3, 2019 at 4:48 PM Basil Gunn <basil@...> wrote:

First figure out how to ssh into your RPi from the same machine you use
for email. I really prefer a cut & paste of console output rather than a
jpg.

> I think all of the infrastructure is in place and working. I just can't get
> email working. I followed the instructions for configuring Claws. I chose
> the option to use it for my winlink email client (KF7DRV@...). When
> I get to the last screen where I save the config, Claws complains that it
> can't connect to "IMAP server: localhost: 143".

Please send the console output of:
netstat -tulpn | grep 143

You may have to reboot your machine after the paclink-unix install to
start the IMAP server.

> On a separate note, I have tested wl2kax25 to w7ecg-10, kf7vol-10, and
> kc7oad-10. They all answer up fine and terminate normally. However, when I
> run "wlgw-check.sh -g CN88tu", it doesn't appear to honor the -g argument.
> The gateway list it tests appears to be the default list. Here's the output
> from show_log.sh:

I couldn't replicate this problem.
There is a mechanism in rmslist.sh to not interrogate the Winlink server
too frequently. If you have ever run rmslist.sh without any arguments
that may be what you are seeing. Try deleting the rmslist.sh output
files & running wlgw-check.sh again

cd
cd tmp
rm rmsgwprox.*

Because you sent a jpg of the console I couldn't really tell if there was
anything else in the show_log.sh output.

/Basil




Re: Getting started with paclink-unix

Basil Gunn
 

It appears that perhaps I should have done "app_config.sh pluimap" instead
of "app_config.sh plu". I'll work on that upgrade later and just
concentrate on sending and receiving email via Mutt.
My current version (BETA13) of the paclink-unix install is NOT using
pluimap just plu. This will install postfix, dovecot, claws-mail,
rainloop, mutt & the web interface to paclink-unix. I am working on a
lighter version of the install that just installs postfix & mutt for
embedded apps ie. that do not use a screen, like Linux RMS Gateway.

My understanding (please correct) is that when I compose email with Mutt
and then send it, it gets reformatted for Winlink (by postfix MTA?) and
deposited in /usr/local/var/wl2k/outbox. The next time I run wl2ktelnet or
wl2kax25, the message will be sent to CMS (directly if wl2ktelnet or via
RMS if wl2kax25).
That's correct. When you send mail with your email app it just deposits
the email into a directory. To complete the operation you have to select
a transport method:

wl2ktelnet: telnet
wl2kax25: packet radio
wl2kserial: pactor modem (SCS-PTC-IIpro)


If I send email to KF7DRV@... from my Gmail account, it stays on
CMS until I retrieve it via paclink. However, I thought when I retrieve it
via paclink, postfix would send it to the Mutt inbox. Instead, I find it in
/usr/local/var/wl2k/outbox.
If you are finding your received mail in your outbox that would be a
configuration mistake.

Is my postfix configuration messed up somehow?
Yes


Re: Getting started with paclink-unix

 

On Mon, Jun 3, 2019 at 04:35 PM, Keith Williamson wrote:
I should have done "app_config.sh pluimap" instead of "app_config.sh plu"
Following along with interest. Was looking at these scripts for other reasons, learning about hostap. It looks like the pluimap argument redirects to the plu argument in that script.

https://github.com/nwdigitalradio/n7nix/blob/master/config/app_config.sh


Re: Getting started with paclink-unix

Basil Gunn
 

First figure out how to ssh into your RPi from the same machine you use
for email. I really prefer a cut & paste of console output rather than a
jpg.

I think all of the infrastructure is in place and working. I just can't get
email working. I followed the instructions for configuring Claws. I chose
the option to use it for my winlink email client (KF7DRV@...). When
I get to the last screen where I save the config, Claws complains that it
can't connect to "IMAP server: localhost: 143".
Please send the console output of:
netstat -tulpn | grep 143

You may have to reboot your machine after the paclink-unix install to
start the IMAP server.

On a separate note, I have tested wl2kax25 to w7ecg-10, kf7vol-10, and
kc7oad-10. They all answer up fine and terminate normally. However, when I
run "wlgw-check.sh -g CN88tu", it doesn't appear to honor the -g argument.
The gateway list it tests appears to be the default list. Here's the output
from show_log.sh:
I couldn't replicate this problem.
There is a mechanism in rmslist.sh to not interrogate the Winlink server
too frequently. If you have ever run rmslist.sh without any arguments
that may be what you are seeing. Try deleting the rmslist.sh output
files & running wlgw-check.sh again

cd
cd tmp
rm rmsgwprox.*

Because you sent a jpg of the console I couldn't really tell if there was
anything else in the show_log.sh output.

/Basil


Re: Getting started with paclink-unix

Keith Williamson
 

Hi Basil,

It appears that perhaps I should have done "app_config.sh pluimap" instead of "app_config.sh plu". I'll work on that upgrade later and just concentrate on sending and receiving email via Mutt.

My understanding (please correct) is that when I compose email with Mutt and then send it, it gets reformatted for Winlink (by postfix MTA?) and deposited in /usr/local/var/wl2k/outbox. The next time I run wl2ktelnet or wl2kax25, the message will be sent to CMS (directly if wl2ktelnet or via RMS if wl2kax25).

If I send email to KF7DRV@... from my Gmail account, it stays on CMS until I retrieve it via paclink. However, I thought when I retrieve it via paclink, postfix would send it to the Mutt inbox. Instead, I find it in /usr/local/var/wl2k/outbox.

Is my postfix configuration messed up somehow?

Thanks,

Keith


On Mon, Jun 3, 2019 at 3:28 PM Keith Williamson via Groups.Io <hkwilliamson=gmail.com@groups.io> wrote:
Hi Basil,

I think all of the infrastructure is in place and working. I just can't get email working. I followed the instructions for configuring Claws. I chose the option to use it for my winlink email client (KF7DRV@...). When I get to the last screen where I save the config, Claws complains that it can't connect to "IMAP server: localhost: 143".

On a separate note, I have tested wl2kax25 to w7ecg-10, kf7vol-10, and kc7oad-10. They all answer up fine and terminate normally. However, when I run "wlgw-check.sh -g CN88tu", it doesn't appear to honor the -g argument. The gateway list it tests appears to be the default list. Here's the output from show_log.sh:

image.png

Here's the output from "rmslist.sh 30 CN88tu":

image.png

73,

Keith
KF7DRV



On Mon, Jun 3, 2019 at 1:58 PM Basil Gunn <basil@...> wrote:

Keith Williamson <hkwilliamson@...> writes:

> Err..meant "Hi Basil". Not to be confused with "Nigel Gunn" over in the
> Chirp forums...

Not a problem. I thought you were referring to Nigel Bruce who played
Dr. Watson to Basil Rathbone's Sherlock Holmes :)

>
> On Mon, Jun 3, 2019 at 1:08 PM Keith Williamson via Groups.Io <hkwilliamson=
> gmail.com@groups.io> wrote:
>
>> Hi Nigel,
>>
>> More headway but some hiccups. First the headway:




Re: Getting started with paclink-unix

Keith Williamson
 

Hi Basil,

I think all of the infrastructure is in place and working. I just can't get email working. I followed the instructions for configuring Claws. I chose the option to use it for my winlink email client (KF7DRV@...). When I get to the last screen where I save the config, Claws complains that it can't connect to "IMAP server: localhost: 143".

On a separate note, I have tested wl2kax25 to w7ecg-10, kf7vol-10, and kc7oad-10. They all answer up fine and terminate normally. However, when I run "wlgw-check.sh -g CN88tu", it doesn't appear to honor the -g argument. The gateway list it tests appears to be the default list. Here's the output from show_log.sh:

image.png

Here's the output from "rmslist.sh 30 CN88tu":

image.png

73,

Keith
KF7DRV



On Mon, Jun 3, 2019 at 1:58 PM Basil Gunn <basil@...> wrote:

Keith Williamson <hkwilliamson@...> writes:

> Err..meant "Hi Basil". Not to be confused with "Nigel Gunn" over in the
> Chirp forums...

Not a problem. I thought you were referring to Nigel Bruce who played
Dr. Watson to Basil Rathbone's Sherlock Holmes :)

>
> On Mon, Jun 3, 2019 at 1:08 PM Keith Williamson via Groups.Io <hkwilliamson=
> gmail.com@groups.io> wrote:
>
>> Hi Nigel,
>>
>> More headway but some hiccups. First the headway:




Re: ThumbDV Issue

 

Forwarded to Anna, NH6Z, Buster's author.


On Mon, Jun 3, 2019, 14:17 Eduardo Gallegos via Groups.Io <xe2jeg=me.com@groups.io> wrote:
Hi...

I am running a ThumbDV device on a Mac with Buster software but now I can’t connect to few Reflectors like 1C, 12A or 30C.  I CAN connect to few others but not he ones that I mention.

I am a register user on D-Star.

Any help will be greatly appreciated.

Regards,

Eduardo Gallegos
XE2JEG




ThumbDV Issue

Eduardo Gallegos <xe2jeg@...>
 

Hi...

I am running a ThumbDV device on a Mac with Buster software but now I can’t connect to few Reflectors like 1C, 12A or 30C. I CAN connect to few others but not he ones that I mention.

I am a register user on D-Star.

Any help will be greatly appreciated.

Regards,

Eduardo Gallegos
XE2JEG


Re: Getting started with paclink-unix

Basil Gunn
 

Keith Williamson <hkwilliamson@...> writes:

Err..meant "Hi Basil". Not to be confused with "Nigel Gunn" over in the
Chirp forums...
Not a problem. I thought you were referring to Nigel Bruce who played
Dr. Watson to Basil Rathbone's Sherlock Holmes :)


On Mon, Jun 3, 2019 at 1:08 PM Keith Williamson via Groups.Io <hkwilliamson=
gmail.com@groups.io> wrote:

Hi Nigel,

More headway but some hiccups. First the headway:


Re: Getting started with paclink-unix

Basil Gunn
 

Keith Williamson <hkwilliamson@...> writes:

Hi Nigel,
Actaully Basil but I will answer to that as well.
(Nigel Bruce, Basil Rathbone, Sherlock Holmes)

More headway but some hiccups. First the headway:

I edited the grid locator in gatewaylist.sh and ran "gatewaylist.sh -l".
The list then showed that w7ecg-10 was closest to me. I successfully sent a
message using "wl2kax25 -c w7ecg-10"! Woo hoo!
Woo hoo indeed!
I also use rmslist.sh to get the list of gateways to check.

Usage: ./rmslist.sh <integer_distance_in_miles> <maidenhead_grid_square>

Now the hiccups:

1) I have a message that's stuck in the outbox
(/usr/local/var/wl2k/outbox). Each time I run either wl2kax25 or
wl2ktelnet, it's resent successfully to my gmail account. When I run
"chk_perm.sh", I get "permissions OK: pi:mail" and "1 files in outbox". I
originally created the message using Claws mail. Is it OK to just delete
the file from /usr/local/var/wl2k/outbox? Don't want to do that if there is
some meta data in another file tracking it.
Yes you can safely delete any file in /usr/local/var/wl2k/outbox
You should then delete the message ID data base
/usr/local/var/wl2k/mid.db

Be sure you do that as user (ie. pi) & not root.

Is this a possible symptom of a configuration problem?

2) When I run "wlgw-check.sh -g CN88tu", I am seeing an error from rigctl
for the set memory index command (E 35).
Yep. That is something I need to fix. Memory index 35 is my 2m aprs
memory location. I just need any 2M memory location that has been
programmed. This is due to the hack required to change bands (2M/440)
for the TM-V71a rig control.

In wlgw-check.sh look for the line: set_memchan_index 35 and change 35
to what ever 2M digital frequency memory index is programmed in your
radio.

Also you should program the two 440 frequencies into your memory so they
can be accessed via memory location instead of VFO.
K7KCA-10 440125000 32 1200 (in Lopez Village)
AE7LW-10 440950000 33 9600

Although, they are far enough away you will probably not be able to hit
them unless you live on a mountain.

If I run rigctl, I can do set
memory index commands for any of the memory channels I have written to
using Chirp but not memory channels that haven't been set to anything. So
far, I programmed the first 20 memory channels with Chirp. So, "rigctl -m
234 -r /dev/ttyUSB0 -E 20" will work but "rigctl -m 234 -r /dev/ttyUSB0 -E
35" fails. I imagine a workaround would be for me to program something into
channel 35 using Chirp (or directly from the radio), and that may fix that.
I'll try that next but wanted you to be aware of the issue. I just got this
radio but I imagine your V71a's have had many more channels previously
programmed so you might not have seen this issue. It would seem that once
the set memory index issue is fixed, the wlgw-check script should work.
When I did run it I could see it was changing the V71a frequency and
transmitting so I think we're really close.
When I run rmslist.sh using your gridsquare, 3 RMS gateways come up that
I control.
So there is an assumption that you are connecting to 1200 baud
Gateways. Just an FYI it is possible to change to 9600 baud on the fly
as well. I need to spend some time to test that out.

/Basil


Re: Getting started with paclink-unix

Keith Williamson
 

Err..meant "Hi Basil". Not to be confused with "Nigel Gunn" over in the Chirp forums...



On Mon, Jun 3, 2019 at 1:08 PM Keith Williamson via Groups.Io <hkwilliamson=gmail.com@groups.io> wrote:
Hi Nigel,

More headway but some hiccups. First the headway:

I edited the grid locator in gatewaylist.sh and ran "gatewaylist.sh -l". The list then showed that w7ecg-10 was closest to me. I successfully sent a message using "wl2kax25 -c w7ecg-10"! Woo hoo!

Now the hiccups:

1) I have a message that's stuck in the outbox (/usr/local/var/wl2k/outbox). Each time I run either wl2kax25 or wl2ktelnet, it's resent successfully to my gmail account. When I run "chk_perm.sh", I get "permissions OK: pi:mail" and "1 files in outbox". I originally created the message using Claws mail. Is it OK to just delete the file from /usr/local/var/wl2k/outbox? Don't want to do that if there is some meta data in another file tracking it. 

2) When I run "wlgw-check.sh -g CN88tu", I am seeing an error from rigctl for the set memory index command (E 35). If I run rigctl, I can do set memory index commands for any of the memory channels I have written to using Chirp but not memory channels that haven't been set to anything. So far, I programmed the first 20 memory channels with Chirp. So, "rigctl -m 234 -r /dev/ttyUSB0 -E 20" will work but "rigctl -m 234 -r /dev/ttyUSB0 -E 35" fails. I imagine a workaround would be for me to program something into channel 35 using Chirp (or directly from the radio), and that may fix that. I'll try that next but wanted you to be aware of the issue. I just got this radio but I imagine your V71a's have had many more channels previously programmed so you might not have seen this issue. It would seem that once the set memory index issue is fixed, the wlgw-check script should work. When I did run it I could see it was changing the V71a frequency and transmitting so I think we're really close.

Thanks,

Keith
KF7DRV

On Mon, Jun 3, 2019 at 11:50 AM Basil Gunn <basil@...> wrote:

> Building latest paclink-unix did the trick. Apparently, latest version
> fixes passwords with multicase and letter/number combinations.

Great! Congrats on getting paclink-unix working!

> Next step for me is to get the radio involved using auto-rmsgw-find.

I currently run the the wlgw-check.sh (Winlink Gateway Check) script
from a cron job 4 times a day.

I know the documentation is a little thin so if you have any problems at
all please don't hesitate to ask questions.

/Basil n7nix

> Thanks!
>
> Keith
> KF7DRV
>
>
> On Mon, Jun 3, 2019 at 10:17 AM Basil Gunn <basil@...> wrote:
>
>>
>> If your password has upper & lower case letters then you need to get the
>> latest version of paclink-unix.
>>
>> cd /usr/local/src/paclink-unix
>> git pull
>> ./build-all.sh




Re: Getting started with paclink-unix

Keith Williamson
 

Hi Nigel,

More headway but some hiccups. First the headway:

I edited the grid locator in gatewaylist.sh and ran "gatewaylist.sh -l". The list then showed that w7ecg-10 was closest to me. I successfully sent a message using "wl2kax25 -c w7ecg-10"! Woo hoo!

Now the hiccups:

1) I have a message that's stuck in the outbox (/usr/local/var/wl2k/outbox). Each time I run either wl2kax25 or wl2ktelnet, it's resent successfully to my gmail account. When I run "chk_perm.sh", I get "permissions OK: pi:mail" and "1 files in outbox". I originally created the message using Claws mail. Is it OK to just delete the file from /usr/local/var/wl2k/outbox? Don't want to do that if there is some meta data in another file tracking it. 

2) When I run "wlgw-check.sh -g CN88tu", I am seeing an error from rigctl for the set memory index command (E 35). If I run rigctl, I can do set memory index commands for any of the memory channels I have written to using Chirp but not memory channels that haven't been set to anything. So far, I programmed the first 20 memory channels with Chirp. So, "rigctl -m 234 -r /dev/ttyUSB0 -E 20" will work but "rigctl -m 234 -r /dev/ttyUSB0 -E 35" fails. I imagine a workaround would be for me to program something into channel 35 using Chirp (or directly from the radio), and that may fix that. I'll try that next but wanted you to be aware of the issue. I just got this radio but I imagine your V71a's have had many more channels previously programmed so you might not have seen this issue. It would seem that once the set memory index issue is fixed, the wlgw-check script should work. When I did run it I could see it was changing the V71a frequency and transmitting so I think we're really close.

Thanks,

Keith
KF7DRV


On Mon, Jun 3, 2019 at 11:50 AM Basil Gunn <basil@...> wrote:

> Building latest paclink-unix did the trick. Apparently, latest version
> fixes passwords with multicase and letter/number combinations.

Great! Congrats on getting paclink-unix working!

> Next step for me is to get the radio involved using auto-rmsgw-find.

I currently run the the wlgw-check.sh (Winlink Gateway Check) script
from a cron job 4 times a day.

I know the documentation is a little thin so if you have any problems at
all please don't hesitate to ask questions.

/Basil n7nix

> Thanks!
>
> Keith
> KF7DRV
>
>
> On Mon, Jun 3, 2019 at 10:17 AM Basil Gunn <basil@...> wrote:
>
>>
>> If your password has upper & lower case letters then you need to get the
>> latest version of paclink-unix.
>>
>> cd /usr/local/src/paclink-unix
>> git pull
>> ./build-all.sh