How to use Direwolf with multiple clients and multiple radios?
I've been using DW for some time now configured with a single channel and a single radio.? If I want to switch between APRS and WINLINK, I have to quit that application and change my radio frequency.
I would like to build/configure DW to have multiple channels with multiple radios attached, but operate independently.? I don't want APRS beacons to go out all channels and the same for WINLINK sessions.
How do I configure DW for such operation?
More importantly, how do I tell the client applications to use certain ports?
(I'm using DW 1.7b on a RPi 4 with a 7" LCD touch display.? Device 1 is an Alinco RIM-9600 and Device 2 is an Audio Injector Zero)
Any assistance would be greatly appreciated!
--73 de N1OBU
|
Re: RFI issues with RPi3B+
Hello Michael,
Personally, I believe the issue lies more with
Direwolf than it does with the Pi. When it comes to Direwolf and
USB devices, I have ALWAYS had so-called "RFI" issues. I always
get the descriptor read write errors and general failures.
I don't know what to say here.. no one else is seeing the issues
you're seeing.? When you see some of those errors, that means
Direwolf cannot communicate with the soundcard interface.? That's
not direwolf's responsibility.
I have many AllStar nodes that run on VHF and UHF with
more power than my APRS stations. With USB sound cards, I have
never had a single failure of any kind with the USB cards. I don't
know whether this is because of a soft reset written into other
programs or what.
While that's somewhat relivent, you're not running your Allstar
nodes on packet frequencies.? RF is a funny thing and you might very
well be only having issues on say 144.390Mhz.
I can literally swap the SD card on my AllStar nodes
and run Direwolf, and then get the usual errors. Despite nothing
being moved. No error with AllStar.
That's not a 100% comparison as you're also changing the frequency
of your radio.? Few other question here:
?? - Is the Allstar setup using the same sound card as you would use
for Direwolf?? Unless it is, this test doesn't count
?? - Does Allstar use ALSA directly or are you going through some
other sound service like PulseAudio, etc?
My fix, I exclusively use hat sound cards. Or where I
can't, like on one multi mode windows machine, I have it reboot
daily. My windows machine has the same issues as a Pi. If I run
Direwolf, error and failures. If I run VARA, no failures.
In your Windows scenario, this is obviously NOT running on the
Raspberry Pi and your not using a HAT-based sound card.? On your
Windows machine, are you using the same USB sound device (and same
connecting USB cables, hubs, etc) that you've attempted to use with
the Raspberry Pi?? Again.. RFI can be a funny thing and the RFI
might be getting in through the PCB of the computer itself, the
incoming power, etc.
I love Direwolf, and I only recommend it. But the one
issue makes a lot of new folks frustrated.
I'm 99% sure your issues are local to your setup and not Direwolf as
a general statement.
--David
KI6ZHD
|
Re: RFI issues with RPi3B+
Personally, I believe the issue lies more with Direwolf than it does with the Pi. When it comes to Direwolf and USB devices, I have ALWAYS had so-called "RFI" issues. I always get the descriptor read write errors and general failures.
I have many AllStar nodes that run on VHF and UHF with more power than my APRS stations. With USB sound cards, I have never had a single failure of any kind with the USB cards. I don't know whether this is because of a soft reset written into other programs or what.
I can literally swap the SD card on my AllStar nodes and run Direwolf, and then get the usual errors. Despite nothing being moved. No error with AllStar.
My fix, I exclusively use hat sound cards. Or where I can't, like on one multi mode windows machine, I have it reboot daily. My windows machine has the same issues as a Pi. If I run Direwolf, error and failures. If I run VARA, no failures.?
I love Direwolf, and I only recommend it. But the one issue makes a lot of new folks frustrated.
|
Also there is a 64-bit binary available among the beta downloads:
Actually there are two, but the one above is the later version.? This one works fine for me in Ubuntu 20.04 on a Celeron laptop.
Lee K5DAT
On Sat, Nov 13, 2021 at 12:26 PM John Kristian < jmkristian@...> wrote: Another way to run is to first install packages that support execution of 32-bit code on a 64-bit operating system:
dpkg --add-architecture i386
apt-get update
apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 qt5-default:i386
If that's insufficient, you might also try:?apt-get install multiarch-support
?
On Thu, Nov 11, 2021 at 04:48 PM, David Ranch wrote:
... follow the instructions and compile the program from scratch.
|
Another way to run is to first install packages that support execution of 32-bit code on a 64-bit operating system:
dpkg --add-architecture i386
apt-get update
apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 qt5-default:i386
If that's insufficient, you might also try:?apt-get install multiarch-support
?
On Thu, Nov 11, 2021 at 04:48 PM, David Ranch wrote:
... follow the instructions and compile the program from scratch.
|
Re: use cron and dw-start.sh to autostart two instances of Direwolf?
Start a terminal in your script with direwolf and its arguments as an argument to the terminal? (Can't test at the moment, but look at?)
Thanks guys,
Switched to the systemd method and it works fine.? Autostarts on boot, and restarts either instance when killing one.? Is there a method to keep the Direwolf terminal windows open on the desktop automatically, without needing to run a "screen" command?? Manually running the scripts keeps the terminals open on the desktop, but systemd runs them in the background.? I'm using VNC and like to see audio levels, etc. on decoded stations.? I've tried a few things in both the start-script and systemd files, but still runs in the background.
My "direwolf-VHF-start.sh" start-script:
#!/usr/bin/env bash
direwolf -c direwolf.conf -qd -T %H:%M:%S:
and systemd "dwVHF.service" file:
[Unit]
Description=Direwolf VHF
After=multi-user.target
[Service]
Type=idle
User=pi
ExecStart=/home/pi/direwolf-VHF-start.sh
Restart=always
[Install]
WantedBy=multi-user.target
-- John D. Hays
Kingston, WA K7VE / WRJT-215
|
Re: use cron and dw-start.sh to autostart two instances of Direwolf?
Thanks guys,
Switched to the systemd method and it works fine.? Autostarts on boot, and restarts either instance when killing one.? Is there a method to keep the Direwolf terminal windows open on the desktop automatically, without needing to run a "screen" command?? Manually running the scripts keeps the terminals open on the desktop, but systemd runs them in the background.? I'm using VNC and like to see audio levels, etc. on decoded stations.? I've tried a few things in both the start-script and systemd files, but still runs in the background.
My "direwolf-VHF-start.sh" start-script:
#!/usr/bin/env bash
direwolf -c direwolf.conf -qd -T %H:%M:%S:
and systemd "dwVHF.service" file:
[Unit]
Description=Direwolf VHF
After=multi-user.target
[Service]
Type=idle
User=pi
ExecStart=/home/pi/direwolf-VHF-start.sh
Restart=always
[Install]
WantedBy=multi-user.target
|
Re: IL2P header has reverse polarity
toggle quoted message
Show quoted text
On Nov 12, 2021, at 8:54 AM, WB2OSZ <wb2osz@...> wrote:
?That was a left over debug message from IL2P development.
It is harmless.
Ignore it.
It has been removed.
|
Re: IL2P header has reverse polarity
That was a left over debug message from IL2P development.
It is harmless.
Ignore it.
It has been removed.
|
Just compiled QTTerm and after some configuration it worked.
Fabulous!
Thanks all!
V.
|
Re: IL2P header has reverse polarity
When it happened, I was using V1.7b, just because I was doing nothing critical.
In my case, I was connected to Direwolf from APRSIS32 using AGW, and my app: only receives KISS packets from Direwolf, decodes them, and calculates Az-El between points.? It appeared to happen with certain messages, but I didn't pay very close attention to when it happened.
Rough Configuration: ?? APRSIS32 => connection to Direwolf through AGW (to send different formatted position reports with Altitude: Text, Compressed, and Mic-E) ????? Only connected to the internet to get more data
?? Direwolf => 2 devices configured through Nexus DR-X (separates left and right audio into 2 separate physical devices)
?? ??? Device 1 was left audio - as a mono device on 0 (so no 1) ?????? Device 2 was right audio - as a mono device on 2 (so no 3)
?? Personal App => connected to DireWolf through KISS over TCP/IP? for monitoring.
?????? Decode received packets, if call and SSID matched, use Lat, Lon, and Alt to calculate Az and El to point antennas
?????? Calculate and output AlfaSpid command to move antenna.
?????? This is intended to point a telescope or Satellite antenna at the balloon during flight.? We have an antenna to work with. ?????? The actual balloon will use Mic-E formatted data.
I started with just Direwolf, but the configured beacons did not seem to be sent to the configured KISS port.? It seemed to work at first, but then didn't.?
?? I used sendto=0 and sendto=2 to send to the different configured ports.
I don't think I changed anything, so I connected APRSIS32 to send the packets.?
?? I couldn't figure out how to force Direwolf to send compressed or Mic-E formats
On Thursday, November 11, 2021, 05:59:27 PM EST, David Ranch <direwolf-groupsio@...> wrote:
IL2P is brand new to Direwolf and still is very much
Alpha.? Are you trying to use it with another Direwolf or NINO TNC
or are you just seeing these errors when you start Direwolf?
--David
KI6ZHD
On 11/11/2021 11:37 AM, Rob Giuliano
via groups.io wrote:
I saw this as well, but was connecting through a
simple KISS TCP/IP port that I wrote code for.
-> I kind of thought it was something in my code, so wasn't
speaking up.
I was running Nexus version of RaspberryPi OS with Linux Kernel
5.10.63-V7+
Which I believe is based off Buster.
|
I wouldn't recommend to try running random binaries
on your system.? Too often, things just won't work and testing on
u20.04, I too see this error:
--
strace -f ./QtTermTCP
execve("./QtTermTCP", ["./QtTermTCP"], 0x7ffcd5bfa028 /* 50 vars
*/) = -1 ENOENT (No such file or directory)
strace: exec: No such file or directory
+++ exited with 1 +++
--
Instead, I would recommend to follow the instructions and compile
the program from scratch.? This exercise might not be suitable for
a new Linux user as most of G8BPQ's projects and documentation is
intended for expert users only.? He also often glosses over lots
of details like the requirements to install various development
libraries, etc.
??
?? --
?? If you need to run on other Linux or similar systems you may be
able to compile from source. Download
,
unzip and run qmake then make
?? The program uses the Qt Framework, so needs some runtime files.
?? --
--David
KI6ZHD
On 11/11/2021 04:13 PM, John Kristian
wrote:
toggle quoted message
Show quoted text
Can you help me run ? I downloaded the
file??and
installed?qt5-default, but no joy:
$ sudo apt-get install qt5-default
[snip]
$ ./QtTermTCP
bash: ./QtTermTCP: No such file or directory
$ ls -l QtTermTCP
-rwxrwxr-x 1 jmk jmk 237488 Nov 11 23:52
QtTermTCP
$ uname -a
Linux vm-jkristian 5.4.0-90-generic
#101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64
x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu
20.04.3 LTS
Release: 20.04
Codename: focal
QtTermTCP is a binary file. It contains the letters "ELF" near the
beginning.
On Wed, Nov 10, 2021 at 08:31 AM, David Ranch wrote:
For a GUI only option, check out John G8BPQ's
QtTermTCP multi-platform terminal program:
??
|
Re: IL2P header has reverse polarity
Hello Don,
I think you mean the "Master" branch which in Git parlance means
"bleeding edge" aka.. unstable.? Yes, you're right about the
current Master branch having the Bonjour/Avahi support but
personally, I find that stuff like this is bloat and creates
unnecessarily noise on the network but that's just my personal
opinion.? It might work today but if you need stuff to just work,
you should be using the v1.6 release as that's what's known stable,
tested, etc.
--David
KI6ZHD
On 11/11/2021 04:10 PM, Don Rolph
wrote:
toggle quoted message
Show quoted text
Unfortunately our deployments require functionality
of the 1.7 release.? My understanding?is that there is a main
branch of 1.7 which I was using.? I need the Bonjour DNS
announcement functionality?of the dev branch, and so am using
that at this time.
Unless you're trying to use IL2P, I would
just ignore those warnings.? Please also note that the
current production release of Direwolf is v1.6.?
Direwolf's development branch is currently labeled as v1.7
but parts of that code is very much a work in progress
(such as this IL2P).
--David
KI6ZHD
On 11/11/2021 03:17 PM, Don Rolph wrote:
I see these errors in the direwolf screen
entries.
I am running BullsEye with Dire Wolf 1.7.
IL2P is brand new to Direwolf and
still is very much Alpha.? Are you trying to use
it with another Direwolf or NINO TNC or are you
just seeing these errors when you start Direwolf?
--David
KI6ZHD
On 11/11/2021 11:37 AM, Rob Giuliano via wrote:
I saw this as well, but was
connecting through a simple KISS TCP/IP port that
I wrote code for.
-> I kind of thought it was something in my
code, so wasn't speaking up.
I was running Nexus version of RaspberryPi OS with
Linux Kernel 5.10.63-V7+
Which I believe is based off Buster.
--
--
|
Can you help me run ? I downloaded the file??and installed?qt5-default, but no joy: $ sudo apt-get install qt5-default[snip]
$ ./QtTermTCP
bash: ./QtTermTCP: No such file or directory
$ ls -l QtTermTCP
-rwxrwxr-x 1 jmk jmk 237488 Nov 11 23:52 QtTermTCP
$ uname -a
Linux vm-jkristian 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
QtTermTCP is a binary file. It contains the letters "ELF" near the beginning.
On Wed, Nov 10, 2021 at 08:31 AM, David Ranch wrote:
For a GUI only option, check out John G8BPQ's QtTermTCP multi-platform terminal program:
??
|
Re: IL2P header has reverse polarity
Unfortunately our deployments require functionality of the 1.7 release.? My understanding?is that there is a main branch of 1.7 which I was using.? I need the Bonjour DNS announcement functionality?of the dev branch, and so am using that at this time.
Unless you're trying to use IL2P, I would just
ignore those warnings.? Please also note that the current
production release of Direwolf is v1.6.? Direwolf's development
branch is currently labeled as v1.7 but parts of that code is very
much a work in progress (such as this IL2P).
--David
KI6ZHD
On 11/11/2021 03:17 PM, Don Rolph
wrote:
I see these errors in the direwolf screen entries.
I am running BullsEye with Dire Wolf 1.7.
IL2P is brand new to Direwolf and still is
very much Alpha.? Are you trying to use it with another
Direwolf or NINO TNC or are you just seeing these errors
when you start Direwolf?
--David
KI6ZHD
On 11/11/2021 11:37 AM, Rob Giuliano via wrote:
I saw this as well, but was
connecting through a simple KISS TCP/IP port that I wrote
code for.
-> I kind of thought it was something in my code, so
wasn't speaking up.
I was running Nexus version of RaspberryPi OS with Linux
Kernel 5.10.63-V7+
Which I believe is based off Buster.
--
|
Re: IL2P header has reverse polarity
Unless you're trying to use IL2P, I would just
ignore those warnings.? Please also note that the current
production release of Direwolf is v1.6.? Direwolf's development
branch is currently labeled as v1.7 but parts of that code is very
much a work in progress (such as this IL2P).
--David
KI6ZHD
On 11/11/2021 03:17 PM, Don Rolph
wrote:
toggle quoted message
Show quoted text
I see these errors in the direwolf screen entries.
I am running BullsEye with Dire Wolf 1.7.
IL2P is brand new to Direwolf and still is
very much Alpha.? Are you trying to use it with another
Direwolf or NINO TNC or are you just seeing these errors
when you start Direwolf?
--David
KI6ZHD
On 11/11/2021 11:37 AM, Rob Giuliano via wrote:
I saw this as well, but was
connecting through a simple KISS TCP/IP port that I wrote
code for.
-> I kind of thought it was something in my code, so
wasn't speaking up.
I was running Nexus version of RaspberryPi OS with Linux
Kernel 5.10.63-V7+
Which I believe is based off Buster.
--
|
Re: IL2P header has reverse polarity
I see these errors in the direwolf screen entries.
I am running BullsEye with Dire Wolf 1.7.
IL2P is brand new to Direwolf and still is very much
Alpha.? Are you trying to use it with another Direwolf or NINO TNC
or are you just seeing these errors when you start Direwolf?
--David
KI6ZHD
On 11/11/2021 11:37 AM, Rob Giuliano
via wrote:
I saw this as well, but was connecting through a
simple KISS TCP/IP port that I wrote code for.
-> I kind of thought it was something in my code, so wasn't
speaking up.
I was running Nexus version of RaspberryPi OS with Linux Kernel
5.10.63-V7+
Which I believe is based off Buster.
|
Re: IL2P header has reverse polarity
IL2P is brand new to Direwolf and still is very much
Alpha.? Are you trying to use it with another Direwolf or NINO TNC
or are you just seeing these errors when you start Direwolf?
--David
KI6ZHD
On 11/11/2021 11:37 AM, Rob Giuliano
via groups.io wrote:
toggle quoted message
Show quoted text
I saw this as well, but was connecting through a
simple KISS TCP/IP port that I wrote code for.
-> I kind of thought it was something in my code, so wasn't
speaking up.
I was running Nexus version of RaspberryPi OS with Linux Kernel
5.10.63-V7+
Which I believe is based off Buster.
|
Re: use cron and dw-start.sh to autostart two instances of Direwolf?
This might get you pointed in the right direction ...
It has the advantage of the predictability of systemd for
starting/stopping/restarting.? Modify as required if you don't need
the kissattach component.
Ray vk2tv
On 12/11/21 3:41 am, KP3FT via
groups.io wrote:
toggle quoted message
Show quoted text
I'm having a heck of a time getting this to work.? On bootup, I'd
like cron to autostart two instances of Direwolf, one for VHF on
one sound card, the other for HF on a second sound card, and
restart either one if one of them crashes.? Cron starts both
Direwolf instances on bootup and they work fine, apparently
because there's no pause between starting the two.? But the
problem is that if I close one of the instances, cron doesn't
restart that instance after one minute.
To get cron to start two instances, I made two bash-scripts, one
for VHF (direwolf-VHF-start.sh) and one for HF (direwolf-HF-start.sh).?
The VHF script uses the default "direwolf.conf"
file; the HF script uses "hf.conf", configured
for 300-baud.? I editing the default dw-start.sh script and
changed DIREWOLF="direwolf" to DIREWOLF="/home/pi/direwolf-VHF-start.sh".?
I also have an edited copy of the default "dw-start.sh"
which I renamed to "dwHF-start.sh" and which has
DIREWOLF="/home/pi/direwolf-HF-start.sh".? I also
changed that script to log to /var/tmp/dwHF-start.log.
I set cron to run both dw-start.sh and dwHF-start.sh.?
All scripts are executable.
Testing cron to run only the VHF start-script or the HF
start-script works... it restarts Direwolf after one minute if I
close Direwolf.
|
The original request was looking for AGW compatible programs.?
Neither Linpac or axcall offer that today.
--David
KI6ZHD
(Maintainer of Linpac)
On 11/10/2021 05:24 PM, Craig, KM6LYW
wrote:
toggle quoted message
Show quoted text
look into "linpac" and, of course, axcall.
??
-craig
KM6LYW
On 11/10/21 4:32 PM, Victor Denisov
wrote:
It looks like QtTerm is what I'm looking for. It can be curses
based, or graphical. Just something that would allow me to
connect to port 8000 of direwolf and talk to a bbs.
Thanks,
More ideas are welcome.
V.
|
John Kristian
John Hays - K7VE / WRJT-215
Jeff KP3FT