I learned something new today! I was not aware of the "State" option in the path statements. Good to know. Thank You Tom.
On 06/12/2014 11:16 AM, Tom Russo wrote: > On Thu, Jun 12, 2014 at 07:37:55AM -0700, we recorded a bogon-computron > collision of the <[email protected]> flavor, containing: >> HI Dave, >> >> I will look into that thank you . This is all running on a raspberry pi. I >> believe its running 2.0.0 version of xastir > 2.0.0 is ancient. You should definitely upgrade. > >> I live in Virginia and all 4 of my Digipeaters use VA in place of WIDE.? I >> know some of the Maryland Digi's use MD >> >> ? >> I wouldn't have thought that running VA1-1,VA2-2 would have been treated any >> more different than WIDE1-1,WIDE2-2. but Xastir seems to think there is a >> issue. > David is mistaken. Xastir is OK with the VA paths, it is merely warning you > about it appearing to be too long. It is wrong to do that -- if you did > VA3-3 it wouldn't complain. There's something broken in the logic in > util.c's > "check_unproto_path". > > Since it's unlikely that your local fill-in digis are using VA1-1 the way > WIDE1-1 is used, it is unnecessary for you to do VA1-1, VA2-2 to get a > three-hop path. You're probably better off doing WIDE1-1,VA2-2 if you're > hoping to access fill-ins, or just VA3-3 if you aren't in need of fill-in > digis. > > I just checked, and if I do WIDE1-1,NM2-2 here, Xastir doesn't complain, but > NM1-1,NM2-2 does get the "Dubious path" warning. > -- David A Aitcheson [email protected] Go Green! Print this email only when necessary. _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
