[aprssig] APRS routing strategies
schiers at netins.net
Tue Feb 22 19:43:43 CST 2005
I'm checking out the mods to uiview32.ini right now. It appears to be
working, but it's going to take a lot of observation to see if everything is
working as it should. Thanks for the ui-view tip!
Right now things are in a state of experimentation and transition. We have
ui-digi's that need to be edited (eventually reburned), a few kpc3's to
reprogram, and a bunch of ui-view32 systems to mod.
Haven't had time to play with trapping at this point. I assume entries like
WIDE7-7, down through WIDE4-4 in the ALIAS box in Digi Setup should do what
we were talking about. I've had a few thoughts of trying to trap the odd
WIDE5-3's that I see.
----- Original Message -----
From: "John Kraus" <jfkraus3 at cox.net>
To: "TAPR APRS Mailing List" <aprssig at lists.tapr.org>
Sent: Tuesday, February 22, 2005 9:07 AM
Subject: Re: [aprssig] APRS routing strategies
> At 09:41 AM 2/22/2005, you wrote:
>> >>> "hasan schiers" <schiers at netins.net> 2/18/05 8:25:03 PM >>>
>> >What makes WIDEn-N traceable? It hasn't been in the past.
>>By moving WIDEn-N from the UIFLOOD parameter in the
>>digis over to the UITRACE parameter.
>> >Are there changes to (in the case of UI-View32)
>> >the *.ini file that allow this to happen...
> Below is the pertinent section of UIVIEW32.INI found in the install
> directory for UI-VIEW32.
> I suspect that simply changing UIFLOOD=WIDE and UITRACE=TRACE to
> UITRACE=WIDE will let this happen. I simply don't have the time right now
> to test it.
> Off to finish the four papers that are due today and tomorrow.
> aprssig mailing list
> aprssig at lists.tapr.org
More information about the aprssig