Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why doesn Xastir digipeat packets sent to the RELAY or WIDE1-1 aliases?

April 26, 2017Aliases packets Relay sent xastir

0

Posted

Why doesn Xastir digipeat packets sent to the RELAY or WIDE1-1 aliases?

1 Answer

0

Posted

If you’re running serial-port connected TNC’s, the “tnc-startup.*” files that get installed in /usr/local/share/xastir/config should set up your TNC to respond to these packets. Select Interfaces->Properties, then select the interface, click Properties, then select the Setup and Shutdown files at the bottom of that dialog. When an interface is brought up the Setup file will be downloaded to the TNC. “myalias WIDE1-1” is the command most TNC’s accept for defining a digipeating alias. That command or similar should be in the Setup file that you use. Use “myalias WIDE1-1” with the new path scheme discussed on APRSSIG during early April, 2005: RELAY/WIDE/TRACE/TRACEn-n are deprecated (should not be used). If you’re running kernel AX.25 interfaces, then you’ll need to run another package to handle digipeating on these interfaces, perhaps digi_ned.