you shouldn't be running suid root. they put that in ther to work around a permissions issue which is what is the underlying factor.
toggle quoted messageShow quoted text
i'm not at home right now (omw to hamcation) to check mine, but as long as the devices and the program are in the same user group you can 775 them and there shouldn't be an issue with permissions.
I have all my stuff in a "radio" group along with the users and have no issues.
On 2/7/2020 7:34 PM, firstname.lastname@example.org wrote:
I tried the first, setuid solution. Also worked like a charm.
As always, many thanks for your support.
On Fri, Feb 7, 2020 at 4:04 PM Basil Gunn <email@example.com> wrote:
First it is mentioned in the Xastir INSTALL file and in their FAQ
that to use AX.25 the xastir run time file must be setuid.
chmod u+s xastir
After the xastir binary permissions should look like this:
-rwsr-xr-x 1 root root 1178192 Jan 6 13:34 xastir
Also you could try using Xaster interface AGWPE localhost:8000.
I will add this to the Xastir install script.
Basil,DRAWS via Interface Control:
Now with XASTIR running I am attempting to set up the interface with
Interface type AX25 TNC, and AX.25 Device Name udr0.moving the radio (FT-817) mini-DIN connector to the DRAWS right mini-DIN
Interface START has no effect, the interface remains DOWN. I have tried
and set the AX.25 Device Name to udr1. This interface also does not START.
I have checked that./var/log/direwolf/direwolf.log)
1. Direwolf and AX25 are running (ax25-status)
2. APRS packets are being received successfully (tail -f
3. APRS position beacon sent ok (verified with aprsfi).interface setup with earlier versions of the Compass image.
Again, I have had XASTIR operating successfully using the same XASTIR
I wonder if there is some other parameter(s) that I have forgotten about.