Hello
everyone.
I'm
trying to use Direwolf using ax.25 to connect to my packet
bbs over RF. The packet bbs is bpq32 and I can get
everything to work when I connect locally. It's running on
a Windows 10 machine.
Direwolf
is running on my Linux box and was being used as an iGate
with no issues. I removed all of the aprs/igate from the
config so it wouldn't beacon at the moment, everything else
stayed the same. I run "direwolf -p -t 0" first, then use
kissattach to attache to the /dev/pts/? port. From there I
run "call VE6CPU CICNOD v VE6CIC-14" to try and connect to
my bbs. It says it sends a packet but I don't hear one and
it doesn't key the transmitter. After a few seconds it
tries sending again and it does actually tx this time. On
the third tx it gives the following. I've included all out
put from the time I start direwolf.
Dire Wolf DEVELOPMENT version 1.7 E (Mar 3 2022)
Includes optional support for:
gpsd hamlib cm108-ptt dns-sd
Reading config file direwolf.conf
Audio device for both receive and
transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200
& 2200 Hz, A+, 44100 sample rate.
Note: PTT not configured for
channel 0. (Ignore this if using VOX.)
Ready to accept AGW client
application 0 on port 8000 ...
Ready to accept KISS TCP client
application 0 on port 8001 ...
DNS-SD: Avahi: Announcing KISS TCP
on port 8001 as 'Dire Wolf on Zues'
Virtual KISS TNC is available on
/dev/pts/4
Created symlink /tmp/kisstnc ->
/dev/pts/4
DNS-SD: Avahi: Service 'Dire Wolf
on Zues' successfully registered.
Invalid transmit channel 8 from
KISS client app.
Are you using AX.25 for Linux? It
might be trying to use a modified
version of KISS which uses the
channel field differently than the
original KISS protocol
specification. The solution might be to use
a command like "kissparms -c 1 -p
radio" to set CRC none mode.
Another way of doing this is
pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss
crc_force=1
<<< Data frame from KISS
client application, port 8, total length = 25
000: 80 86 92 86 9c 9e 88 e0 ac
8a 6c 86 a0 aa 62 ac ..........l...b.
010: 8a 6c 86 92 86 7d 3f 04 a6
.l...}?..
Invalid transmit channel 2 from
KISS client app.
Are you using AX.25 for Linux? It
might be trying to use a modified
version of KISS which uses the
channel field differently than the
original KISS protocol
specification. The solution might be to use
a command like "kissparms -c 1 -p
radio" to set CRC none mode.
Another way of doing this is
pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss
crc_force=1
<<< Data frame from KISS
client application, port 2, total length = 25
000: 20 86 92 86 9c 9e 88 e0 ac
8a 6c 86 a0 aa 62 ac .........l...b.
010: 8a 6c 86 92 86 7d 3f da 0c
.l...}?..
[0L]
VE6CPU-1>CICNOD,VE6CIC-14:(SABM cmd, p=1)
Audio output start error.
Bad address
Error preparing after bad state:
Bad address
Error preparing after bad state:
Bad address
Error preparing after bad state:
Bad address
Error preparing after bad state:
Bad address
Error preparing after bad state:
Bad address
Error preparing after bad state:
Bad address
Error preparing after bad state:
Bad address
Error preparing after bad state:
Bad address
Error preparing after bad state:
Bad address
Error preparing after bad state:
Bad address
Audio write error retry count
exceeded.
Audio output start error.
Bad address
The
above errors repeats at least a dozen times and will repeat
everytime it tries to send a packet. Should also mention it
does actually send that packet and bpq32/soundmodem on the
other machine sees the packet.
I
did try modprobing mkiss with the suggested paramaters
(after rmmod), but the same message comes up. Any idea
what's happening?
Thanks
for the help.
