Date   

Re: Pac-Link vs WL2k Peer to Peer

Ed Bloom, KD9FRQ
 

Basil,

Thank you for the beacon script offer. I accept.

I would like to beacon "KD9FRQ on air and monitoring"

73, Ed, KD9FRQ

On 6/1/2020 9:53 AM, Basil Gunn wrote:
Is Pac-Link always able to receive a message via a Peer-to-Peer
connection like the PC-based WinLink when it is set in Peer-to-Peer mode?
Correct. Note that paclink-unix is ALWAYS listening for someone doing a
Peer-to-Peer connection to your call sign. You don't have to manually
set the mode "like the Windows based WinLink Express".

If you want to verify which call sign, SSIDs that AX.25 is listening on, run
this in a console.

netstat --ax25

The "<your_callsign>-0" entry also listens for "<your_callsign>" with no
SSID.

If I am not xmitting how do others know I am on line and able to take mail?
If you send me the text that you would like to beacon I will send you a
script that will use the beacon command to send out a "beacon"
periodically using cron.

Take a look at the beacmin.sh & btest.sh scripts in n7nix/debug.
They are more complicated than you will require because they pull your
lat/lon from gpsd. Scroll to the bottom of the script & look for
variable "beacon_msg" to get some idea how it works.

/Basil


Re: Pac-Link vs WL2k Peer to Peer

Basil Gunn
 

Is Pac-Link always able to receive a message via a Peer-to-Peer
connection like the PC-based WinLink when it is set in Peer-to-Peer mode?
Correct. Note that paclink-unix is ALWAYS listening for someone doing a
Peer-to-Peer connection to your call sign. You don't have to manually
set the mode "like the Windows based WinLink Express".

If you want to verify which call sign, SSIDs that AX.25 is listening on, run
this in a console.

netstat --ax25

The "<your_callsign>-0" entry also listens for "<your_callsign>" with no
SSID.

If I am not xmitting how do others know I am on line and able to take mail?
If you send me the text that you would like to beacon I will send you a
script that will use the beacon command to send out a "beacon"
periodically using cron.

Take a look at the beacmin.sh & btest.sh scripts in n7nix/debug.
They are more complicated than you will require because they pull your
lat/lon from gpsd. Scroll to the bottom of the script & look for
variable "beacon_msg" to get some idea how it works.

/Basil


Pac-Link vs WL2k Peer to Peer

Ed Bloom, KD9FRQ
 

Is Pac-Link always able to receive a message via a Peer-to-Peer connection like the PC-based WinLink when it is set in Peer-to-Peer mode?

If I am not xmitting how do others know I am on line and able to take mail?

Ed, KD9FRQ


Re: "Lost" Claws Mail

Ed Bloom, KD9FRQ
 

Thank you.

I edited the file to make the email address correct per your note.

That corrected to problem.T

On 6/1/2020 12:47 AM, Basil Gunn wrote:
Ed,

It seems the script ran fine but defaulted to telnet and did not use the
radio to send the message.
Correct it is meant to ONLY verify your email configuration, postfix, dovecot
& some mail client so doesn't require a radio. It allows me to take a
look at some of your config files.

I notice in file: /usr/local/etc/wl2k.conf that you have
email=kd9frq@winlink.org

it should be:
email=pi@localhost

which confuses me because the config script sets that.


May 31 18:31:33 MyDrawsPi postfix/qmgr[843]: 17E07161335: from=<pi@MyDrawsPi.localhost>, size=477, nrcpt=1 (queue active)

Just trying to figure out where the mail goes on the Pi once it is
picked up via radio and how to get it route to the Claws inbox.
You are running a local imap server so that's were all mail ends up
until you retrieve it with your mail client which will store your mail
in the /home/pi/Mail directory.

I wonder if it has to do with being on udr1 instead of udr0? Just
wondering.
Nope. That has nothing to do with email.

Ed

On 5/31/2020 2:59 PM, Basil Gunn wrote:
If you are setting up Claws-mail, make sure that you follow the
Claws-mail setup instructions exactly as described here:

https://github.com/nwdigitalradio/n7nix/blob/master/email/claws/README.md

If you continue to have problems try using mutt, which should already be
installed & configured to verify that the dovecot imap server is
configured properly.

In n7nix/debug directory there is a script, chk_mail.sh that will verify
your configuration & send a wl2k message to me automatically.

/Basil


Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> writes:

Since I finally got a second antenna up and the second 2m rig, I now
have my DRAWS running APRS on udr0 and wl2kax25 sending and receiving on
udr1.

Claws Mail is properly sending mail out and wl2kax25 sees it ans sends
it on. Wl2kax25 is also picking up the mail.

However, once picked up, it is not getting routed in the pi@localhost to
Claws Mail.

What conf file(s) and setting should I check?

Thanks, Ed, KD9FRQ


Re: "Lost" Claws Mail

Basil Gunn
 

Ed,

It seems the script ran fine but defaulted to telnet and did not use the
radio to send the message.
Correct it is meant to ONLY verify your email configuration, postfix, dovecot
& some mail client so doesn't require a radio. It allows me to take a
look at some of your config files.

I notice in file: /usr/local/etc/wl2k.conf that you have
email=kd9frq@winlink.org

it should be:
email=pi@localhost

which confuses me because the config script sets that.


May 31 18:31:33 MyDrawsPi postfix/qmgr[843]: 17E07161335: from=<pi@MyDrawsPi.localhost>, size=477, nrcpt=1 (queue active)

Just trying to figure out where the mail goes on the Pi once it is
picked up via radio and how to get it route to the Claws inbox.
You are running a local imap server so that's were all mail ends up
until you retrieve it with your mail client which will store your mail
in the /home/pi/Mail directory.

I wonder if it has to do with being on udr1 instead of udr0? Just
wondering.
Nope. That has nothing to do with email.

Ed

On 5/31/2020 2:59 PM, Basil Gunn wrote:
If you are setting up Claws-mail, make sure that you follow the
Claws-mail setup instructions exactly as described here:

https://github.com/nwdigitalradio/n7nix/blob/master/email/claws/README.md

If you continue to have problems try using mutt, which should already be
installed & configured to verify that the dovecot imap server is
configured properly.

In n7nix/debug directory there is a script, chk_mail.sh that will verify
your configuration & send a wl2k message to me automatically.

/Basil


Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> writes:

Since I finally got a second antenna up and the second 2m rig, I now
have my DRAWS running APRS on udr0 and wl2kax25 sending and receiving on
udr1.

Claws Mail is properly sending mail out and wl2kax25 sees it ans sends
it on. Wl2kax25 is also picking up the mail.

However, once picked up, it is not getting routed in the pi@localhost to
Claws Mail.

What conf file(s) and setting should I check?

Thanks, Ed, KD9FRQ


Re: "Lost" Claws Mail

Ed Bloom, KD9FRQ
 

Following the Readme, everything seems to be in order.  Claws sends out to pi@localhost and whereever the wl2kax25 program needs to have outbox data.

It seems the script ran fine but defaulted to telnet and did not use the radio to send the message. It sent a copy to my Claws Inbox.

Just trying to figure out where the mail goes on the Pi once it is picked up via radio and how to get it route to the Claws inbox.

I wonder if it has to do with being on udr1 instead of udr0?  Just wondering.

Ed

On 5/31/2020 2:59 PM, Basil Gunn wrote:
If you are setting up Claws-mail, make sure that you follow the
Claws-mail setup instructions exactly as described here:

https://github.com/nwdigitalradio/n7nix/blob/master/email/claws/README.md

If you continue to have problems try using mutt, which should already be
installed & configured to verify that the dovecot imap server is
configured properly.

In n7nix/debug directory there is a script, chk_mail.sh that will verify
your configuration & send a wl2k message to me automatically.

/Basil


Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> writes:

Since I finally got a second antenna up and the second 2m rig, I now
have my DRAWS running APRS on udr0 and wl2kax25 sending and receiving on
udr1.

Claws Mail is properly sending mail out and wl2kax25 sees it ans sends
it on. Wl2kax25 is also picking up the mail.

However, once picked up, it is not getting routed in the pi@localhost to
Claws Mail.

What conf file(s) and setting should I check?

Thanks, Ed, KD9FRQ


Re: "Lost" Claws Mail

Basil Gunn
 

If you are setting up Claws-mail, make sure that you follow the
Claws-mail setup instructions exactly as described here:

https://github.com/nwdigitalradio/n7nix/blob/master/email/claws/README.md

If you continue to have problems try using mutt, which should already be
installed & configured to verify that the dovecot imap server is
configured properly.

In n7nix/debug directory there is a script, chk_mail.sh that will verify
your configuration & send a wl2k message to me automatically.

/Basil


Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> writes:

Since I finally got a second antenna up and the second 2m rig, I now
have my DRAWS running APRS on udr0 and wl2kax25 sending and receiving on
udr1.

Claws Mail is properly sending mail out and wl2kax25 sees it ans sends
it on. Wl2kax25 is also picking up the mail.

However, once picked up, it is not getting routed in the pi@localhost to
Claws Mail.

What conf file(s) and setting should I check?

Thanks, Ed, KD9FRQ


"Lost" Claws Mail

Ed Bloom, KD9FRQ
 

Since I finally got a second antenna up and the second 2m rig, I now have my DRAWS running APRS on udr0 and wl2kax25 sending and receiving on udr1.

Claws Mail is properly sending mail out and wl2kax25 sees it ans sends it on. Wl2kax25 is also picking up the mail.

However, once picked up, it is not getting routed in the pi@localhost to Claws Mail.

What conf file(s) and setting should I check?

Thanks, Ed, KD9FRQ


Re: Chromium issue...

Basil Gunn
 

Yup did the same procedure and it worked on my old install.
Great to hear Mike.


Re: Chromium issue...

Mike B
 

Yup did the same procedure and it worked on my old install.

Mike


Re: Chromium issue...

Basil Gunn
 

I did a reboot, and launched Chromium, and no drama...so as far as I
can tell...it is completely fixed...now I need to fix my old
install....
On your old install should be able to refresh your files

cd
cd n7nix
git pull
cd config
./bin_refresh.sh

and run the iptable-check.sh script

iptable-check.sh


Re: Chromium issue...

Mike B
 

This is on the new image that I listed above...I didn't burn a new one...(in my case ax25 was already running by now)

I did not need delete the lines.

This a completely different output than what I had seen before...even while trying to fix my other install

I did a reboot, and launched Chromium, and no drama...so as far as I can tell...it is completely fixed...now I need to fix my old install....

pi@draws:~/n7nix/config $ iptable-check.sh
set sudo
== List current iptables rules
Chain INPUT (policy ACCEPT 3490 packets, 513926 bytes)
    pkts      bytes target     prot opt in     out     source               destination        

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
    pkts      bytes target     prot opt in     out     source               destination        

Chain OUTPUT (policy ACCEPT 2686 packets, 663992 bytes)
    pkts      bytes target     prot opt in     out     source               destination        

Number of ax25 iptables rules found: 0
iptables file: /etc/iptables/rules.ipv4.ax25 exists
iptables file: /lib/dhcpcd/dhcpcd-hooks/70-ipv4.ax25 exists
Stopping firewall and allowing everyone...

== setup iptables
Number of ax25 rules now: 6
pi@draws:~/n7nix/config $


Re: Chromium issue...

Basil Gunn
 

Thanks for the console output.

The raspbian distro version of iptables has recently changed and no
longer allows setting iptables rules without the ax.25 interface(s)
being up. That means the place where iptables was previously config'ed
in './app_config.sh core' no longer works. I have made some changes to a
number of scripts and need to do more verification but running the new
iptable-check.sh script should fix your problem.

# First start the ax25 interfaces if you haven't already done that

ax25-start

# Then refresh the n7nix repo on your RPi

cd
cd n7nix
git pull
cd config
./bin_refresh.sh

# Now run the new iptable-check.sh script and verify

iptable-check.sh

I would appreciate seeing all the console output from this script.

If the above doesn't work then delete the following two files:

/etc/iptables/rules.ipv4.ax25
/lib/dhcpcd/dhcpcd-hooks/70-ipv4.ax25

and run iptable-check.sh again.

/Basil


Mike B <kf5dey@gmail.com> writes:

Ok gave up on other fixes..downloaded the fresh Draws version 16, wrote it to a new unused sd card...

...started from new on the 'Getting Started' https://nw-digital-radio.groups.io/g/udrc/wiki/8921

cd
cd n7nix
git pull

sudo su
apt-get update
apt-get dist-upgrade

(BTW at this point you need to 'exit' root in order to do the next two steps)

cd
cd n7nix/config
# Become root (again)
sudo su
./app_config.sh core

During that ./app_config.sh core I get the following messages...

*== setup iptables*
*iptables v1.8.2 (nf_tables): RULE_APPEND failed (No such file or directory): rule in chain OUTPUT*
*iptables v1.8.2 (nf_tables): Couldn't load match `udp':No such file or directory*

*Try `iptables -h' or 'iptables --help' for more information.*
*iptables v1.8.2 (nf_tables): Couldn't load match `udp':No such file or directory*

*Try `iptables -h' or 'iptables --help' for more information.*
*iptables v1.8.2 (nf_tables): RULE_APPEND failed (No such file or directory): rule in chain OUTPUT*
*iptables v1.8.2 (nf_tables): Couldn't load match `udp':No such file or directory*

*Try `iptables -h' or 'iptables --help' for more information.*
*iptables v1.8.2 (nf_tables): Couldn't load match `udp':No such file or directory*

*Try `iptables -h' or 'iptables --help' for more information.*

*2020 05 30 09:52:45 PDT: iptable_install.sh: iptables install/config script FINISHED*

I rebooted as directed and guess what... Chromium still attempts to ride on UDR0:

*udr0: fm KF5DEY-10 to QST ctl UI pid=CC(IP) len 195*
*IP: len 195 192.168.255.2->239.255.255.250 ihl 20 ttl 1 DF prot UDP*
*UDP: len 175 57908->1900 Data 167*

Again, this was a brand new sd card, fresh download of draws version16, ran./app_config.sh core as described...

Something is wrong somewhere...


Re: Chromium issue...

Mike B
 

Ok gave up on other fixes..downloaded the fresh Draws version 16, wrote it to a new unused sd card...

...started from new on the 'Getting Started' https://nw-digital-radio.groups.io/g/udrc/wiki/8921

cd
cd n7nix
git pull

sudo su
apt-get update
apt-get dist-upgrade


(BTW at this point you need to 'exit' root in order to do the next two steps)

cd
cd n7nix/config
# Become root   (again)
sudo su
./app_config.sh core

During that ./app_config.sh core   I get the following messages...

== setup iptables
iptables v1.8.2 (nf_tables):  RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
iptables v1.8.2 (nf_tables): Couldn't load match `udp':No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.8.2 (nf_tables): Couldn't load match `udp':No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.8.2 (nf_tables):  RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
iptables v1.8.2 (nf_tables): Couldn't load match `udp':No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.8.2 (nf_tables): Couldn't load match `udp':No such file or directory

Try `iptables -h' or 'iptables --help' for more information.

2020 05 30 09:52:45 PDT: iptable_install.sh: iptables install/config script FINISHED


I rebooted as directed and guess what... Chromium still attempts to ride on UDR0:

udr0: fm KF5DEY-10 to QST ctl UI pid=CC(IP) len 195
IP: len 195 192.168.255.2->239.255.255.250 ihl 20 ttl 1 DF prot UDP
UDP: len 175 57908->1900 Data 167


Again, this was a brand new sd card, fresh download of draws version16, ran ./app_config.sh core
as described...

Something is wrong somewhere...

Mike


Re: Teamviewer install on Raspberry PI

Mike B
 

Basil,

You are busy enough handling my dumb questions! :)

Sent through two tin cans on a string.

On May 30, 2020, at 12:49, Basil Gunn <basil@pacabunga.com> wrote:


J P,

Thanks for providing detailed instructions on teamviewer. Not that
teamviewer isn't an effective tool but really all I need is to
ssh into an RPi. <The rest of this message is a rant>

Having said that, I REALLY DO NOT want to be the Linux support guy at
that level. If you do not enjoy trying to figure things out then using
an RPi for HAM radio may not be your thing. To quote Bruce Perens from a
number of years ago: "Well, let's just say, 'if your VCR is still
blinking 12:00, you don't want Linux.'”

I've tried to make a set of scripts that will work consistently
installing & configuring packet & HF modes. If you use them & follow
instructions they will work. If you decide to be creative & do something
else then by all means post your problems to the forum but don't expect
me to respond.

I can take the NWDR image, burn it to an mSD card & configure some HAM
digital mode in around 1/2 hour. I provide everything on github that
would allow you to do the same. If you find that useful, great.


J P Watters via groups.io <kc9kko=mac.com@groups.io> writes:

Rather than HIJACK another thread, I recommend the installing
Teamviwer on Buster to be able to remotely assist others with issues.


Re: Teamviewer install on Raspberry PI

Basil Gunn
 

J P,

Thanks for providing detailed instructions on teamviewer. Not that
teamviewer isn't an effective tool but really all I need is to
ssh into an RPi. <The rest of this message is a rant>

Having said that, I REALLY DO NOT want to be the Linux support guy at
that level. If you do not enjoy trying to figure things out then using
an RPi for HAM radio may not be your thing. To quote Bruce Perens from a
number of years ago: "Well, let's just say, 'if your VCR is still
blinking 12:00, you don't want Linux.'”

I've tried to make a set of scripts that will work consistently
installing & configuring packet & HF modes. If you use them & follow
instructions they will work. If you decide to be creative & do something
else then by all means post your problems to the forum but don't expect
me to respond.

I can take the NWDR image, burn it to an mSD card & configure some HAM
digital mode in around 1/2 hour. I provide everything on github that
would allow you to do the same. If you find that useful, great.


J P Watters via groups.io <kc9kko=mac.com@groups.io> writes:

Rather than HIJACK another thread, I recommend the installing
Teamviwer on Buster to be able to remotely assist others with issues.


Teamviewer install on Raspberry PI

J P Watters <kc9kko@...>
 

Basil,

Rather than HIJACK another thread, I recommend the installing Teamviwer on Buster to be able to remotely assist others with issues.

  • Install Teamviewer

# install teamviewer for virtual remote desktop access

cd  /home/pi/Downloads

mkdir teamviewer 

cd teamviewer
I currently use version 15 so I don't encounter too new of software the forces upgrading the client.

wget http://download.teamviewer.com/download/linux/version_15x/teamviewer-host_armhf.deb

 

sudo dpkg -i teamviewer-host_armhf.deb

 

Installing teamviewer often results in missing dependancies.

after teamviewer install fails run sudo apt --fix-broken install -y

 

sudo apt --fix-broken install -y

 

grep -i eula /opt/teamviewer/config/global.conf

# Should result in finding a line containing [int32] EulaAccepted = 1

#

# edit the /opt/teamviewer/config/global.conf 

# insure that there is a line EulaAccepted = 1 in the file.

#

# [bin  ] EnterpriseUIState = 

# [int32] EulaAccepted = 1

# [int32] IPC_Port_Service = 5942

#

 

#get teamviewer id

teamviewer info

 

#set a Teamviewer password 

# sudo teamviewer passwd [password]

# ie. sudo teamviewer passwd itisasecret  

 

sudo teamviewer passwd whateveryoutypeherebecomsethepassword

 

# restart the Teamviewer service      

sudo systemctl restart teamviewerd





Then from your TEAMVIEWER platform of choice, connect the the id.


Re: Chromium issue...

Basil Gunn
 

I would like to point out that I was running an image, did the
appropriate updates etc...for a few months... then probably something
I did broke the iptables...
I know passing emails back & forth is not very satisfying when trying to
fix problems. If I was in front of your RPi I could fix your problem
in short order so it is a little frustrating for both of us.

...so I can start over (the equivalent of reinstalling windows) but
chances are good I will successfully break iptables again.
I would like to know how you do that so I could make the configure
scripts more robust.

I am not saying it is your fault...Chromium is the issue...but
iptables is the weakness that Chromium is exploiting.
iptables is the solution to fixing a Chromium problem that binds to all
network interfaces.

I will work on what you wrote, and see if I can work around this...
Try running the iptable_install.sh script by itself. Then look for
this file:

/lib/dhcpcd/dhcpcd-hooks/70-ipv4.ax25

It needs to have the following line in it that will allow iptables rules
to be loaded at boot time.

iptables-restore < /etc/iptables/rules.ipv4.ax25


Re: Chromium issue...

Mike B
 

I would like to point out that I was running an image, did the appropriate updates etc...for a few months... then probably something I did broke the iptables...

...so I can start over (the equivalent of reinstalling windows) but chances are good I will successfully break iptables again.

I am not saying it is your fault...Chromium is the issue...but iptables is the weakness that Chromium is exploiting.

I will work on what you wrote, and see if I can work around this...

Mike


Re: #wl2kax25 #wl2kax25

Basil Gunn
 

Hi Ed,

Does the /usr/local/etc/wl2k.conf need to stay as udr0 or can I change
it since I am wanting to use udr1 for EMAIL and leave urd0 for APRS as
the frequesncies are different?
Yes that is exactly right. Change 'ax25port=' to which ever port you
will be using for Winlink messaging, then you will not have to bother
with setting that argument on the command line.

Ed, KD9FRQ

On 5/29/2020 11:33 PM, Basil Gunn wrote:
wl2kax25 -a udr1 -c n7nix-10

1161 - 1180 of 5976