[Xastir] Digipeating

J. Lance Cotton joe at lightningflash.net
Wed Sep 1 12:56:51 EDT 2004


Curt, WE7U wrote:

> Another method would be to run digi_ned and aprsd on the Linux box,
> then connect all the APRS clients to the aprsd instance.  The later
> versions of aprsd allow using the AX.25 networking ports to talk to
> the TNC's, so aprsd and digi_ned should be able to co-exist.

The above method is the one described in the DIGI_NED documentation as a way 
to run both a client and DIGI_NED or to run an igate and DIGI_NED.

The idea is that aprsd is the master controller and it talks to:
1) DIGI_NED through a pty (pseudo-tty: a loopback type of connection)
2) An APRS-IS server through the normal aprsd method
3) A client such as Xastir through either a pty or a Inet port

Or something like that. From DIGI_NED's point of view, it has 2 ports: one 
is the AX.25 device and the other is the aprsd messaging port. If something 
needs to be igated, aprsd spits it over to DIGI_NED who then takes care to 
pack it in third-party format and dumps it to the radio port with the proper 
paths for your area (meaning you can have third party messages go out with 
0, 1, 2, whatever number of hops)

DIGI_NED would also be configured to digipeat EVERYTHING from the radio port 
to the aprsd port.

Xastir connects to a full-feed port on aprsd, where it sees data from the 
incoming bit of the DIGI_NED<->aprsd link, plus any Inet data from aprsd's 
APRS-IS connection. Xastir would have ALL igating and relay digipeating 
turned off.

The one downside to this, other than the complexity, is that Xastir can no 
longer tell you which packets were heard via TNC or Inet.

-Lance KJ5O
-- 
J. Lance Cotton, KJ5O
http://map.findu.com/kj5o-12
joe at lightningflash.net



More information about the Xastir mailing list