Okay, excellent, so THAT was the question I needed to ask. Yes, that MIGHT be the thing then. Here in the Bay Area there's soooo many digis around that the likelihood of hearing a WIDE1-1 is pretty low.
Okay, so that wasn't terribly clear I guess but glad it is now. This does still work for me, since what I actually want is a fill-in anyways, so I'll just have to get a little more tactical about my testing... see if I can get my buddy to bring his Jeep and radio over to hit me with some WIDE1-1 packets. Thanks Curt, et al!! ---- Aaron Vogel 818-268-3981 [email protected] ----- On Thu, Jan 18, 2018 at 10:12 AM, Curt, WE7U <[email protected]> wrote: > On Thu, 18 Jan 2018, Aaron Vogel wrote: > > I guess I have another, perhaps more fundamental question: how do I control >> _what_ gets digipeated? For example, if I want it to act as a fill-in and >> only digipeat WIDE1-1... where would I tell it to do this? If I wanted it >> to digipeat everything... where would I tell it to do this? >> > > You don't. Xastir was not designed to be a wide-area digipeater. It can > only function as a fill-in digipeater, digi'ing only on WIDE1-1. > > If you're seeing packets come in that already have been digipeated on the > WIDE1-1 path, Xastir won't digipeat them again. > > If you want full control over digipeating and want to do something more > than what Xastir does, you'll probably want to run Digi_ned to do that. You > can run Digi_ned and Xastir at the same time. > > -- > Curt, WE7U. http://we7u.wetnet.net > "The world DOES revolve around me: I picked the coordinate system!" > Coordinate Converter (Android): http://www.sarguydigital.com > > _______________________________________________ > Xastir mailing list > [email protected] > http://xastir.org/mailman/listinfo/xastir > _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
