David Lowry <email@example.com> writes:
Here, specifically is what I'm getting while following the "Testing
AX.25" section of the "Verifying" step of Getting Started. I don't
understand why these commands are not giving any response.
No response from netstat --ax25 is a configuration error.
output of mheard from the tail command for direwolf?
No. mheard displays ax.25 data.
type: man mheard for more info.
The stuff up at
the top is the output of the tail command.
The following looks ok but I would expect to see more packets.
Apr 13 16:37:12 ke7rgpi direwolf: Digipeater MISION audio level = 11(12/6) [NONE] ::|||||:_
Apr 13 16:37:12 ke7rgpi direwolf: [0.3] NB7O-11>APOT21,WA2WA,WIDE1,MISION*,WIDE2-1:/233726h4541.09N/11854.59Wk295/054/A=001605charging the batteries
Apr 13 16:37:12 ke7rgpi direwolf: Position with time, truck, Open Track
Apr 13 16:37:12 ke7rgpi direwolf: N 45 41.0900, W 118 54.5900, 62 MPH, course 295, alt 1605 ft
Apr 13 16:37:12 ke7rgpi direwolf: charging the batteries
The following looks ok.
pi@ke7rgpi:~ $ ax25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: RUNNING and ENABLED
Status for ax25d.service: RUNNING and ENABLED
AX.25 device: ax0 successfully configured with ip: 192.168.255.2
AX.25 device: ax1 successfully configured with ip: 192.168.255.3
This does NOT look ok.
pi@ke7rgpi:~ $ netstat --ax25
Active AX.25 sockets
Dest Source Device State Vr/Vs Send-Q Recv-Q
pi@ke7rgpi:~ $ mheard
Callsign Port Packets Last Heard
mheard will not work until the ax.25 configuration is fixed.
Waiting on requested console output from showudrc.sh and ax25-status -d