Re: #ax25 #direwolf system failing suggested checks #direwolf #ax25

Ryan Matthew Headley

Thanks for the quick response. I will give it shot tomorrow.

On Tue, 26 Nov 2019, 19:49 Basil Gunn, <basil@...> wrote:

If you are using the left hand mDin6 connector, you should be using port udr0
 - verify these files for udr0:
    /usr/local/etc/wl2k.conf  ax25port=udr0

From previous post by Dave Christensen
> The clue to fix the problem was in your message 3722 where you noted this:
> " Verify that the connector used, the port in ax25port= in /usr/local/etc/wl2k.conf and portname in /etc/ax25/axports match. ie. left port is udr0, right is udr1"

- Include the output of both of these console commands

ax25-status -d

Also what does this command return:
cd n7nix/debug
./ -P udr1

You should not have to change direwolf.conf
Be sure to use the latest scripts:
cd n7nix
git pull

/Basil n7nix

Ryan Matthew Headley <headley.ryan@...> writes:

> I am on my third install of the DRAWS image. I have followed the instructions on this site to the letter each time. I now have gps working properly, and paclink-unix is running as expected.
> Now I have moved on to direwolf and ax25 for APRS and more general packet, and I have this problem:
> I can monitor incoming traffic, but cannot transmit. So I went back to the guide and ran this test:
> d
> cd n7nix/debug
> sudo su
> # Test left channel
> ./ -P udr0
> # Test right channel
> ./ -P udr1
> # To see all the options available
> ./ -h
> './ -P udr0' returns:
> 'beacon: invalid AX.25 port setting - udr0
> Beacon command failed.'
> I have configured AX.25 and direwolf on own before, and what is residing in /etc/ax25/ is not what I am used to.
> Any advice?

Join to automatically receive all group messages.