Order Tray | Contact Us | Home | SIG Lists

[aprssig] LinkN-N for dummies

Robert Bruninga bruninga at usna.edu
Thu Dec 23 15:42:40 UTC 2004


Wes,

Yes, why not just put a disclamer at the top of the page
saying

Notes:
1) "Short interstate LINKn-N systems are generally not needed.  
The intent of the LINKn-N system is to cover the long haul 
corridor's of interstate communications and population densities
as an alternative to WIDEn-N flooding in all directions.  Not
simply to have all interstates have LINKn-N systems

2) Not every digi along an interstate needs to be part of the
LINKn-N system, only enough to help packets propogate
linearly.  We don't need saturation coverage, just enough
to cover the link.  This lets some other digis be used for
other posibilities..

Or something like that...

Bob

>>> Wes Johnston <wes at kd4rdb.com> 12/22/04 1:46:19 PM >>>
I know what you mean about short Istates.... SC I-26 is one I consider
short
too... granted it is 220 miles long and just barely goes into NC, but
when I
think LNKn-n, I think I-95 and I-10.  However, I am not in a position
to know
about everyone's circumstance, so I included some that I wasn't sure
of... it's
the reason I listed the mileage in the table.  Perhaps a disclaimer is
due
regarding shorter stretches?

Wow, I had no idea there were so darned many interstates!

Wes
--



Quoting Robert Bruninga <bruninga at usna.edu>:

> Wes,
> On your page of interstate and digis settings, you mgiht
> want to add the ,30 to each of the UITRACE entries.
>
> Also, I did not plan to encourage LINKn-N's for short
> interstates. (example of 68, or I-97 in Maryland).
> becuase the entire length of 68 interstate can be covered
> with 3  digis or so, and also that remote area may better
> be covered by WIDEn-N.  For short interstates, it is un-likely
> that anyone would change their path just for that.
>
> Similarly I-97 is also too short and surrounded by other
> digis and paths.  Though if there are enough digis, it
> doesnt hurt, but just wanted to remind people that the
> objective was not neceaarliy to"cover" every numbered
>  interstate, but rather to cover the corridor's of travel and
> just conviently use the interstate number as a way to
> remember it.
>
> Glad to see others working on this plan
> thanks
> bob
>
> >>> 1schwab1 at tampabay.rr.com 12/21/04 10:58 PM >>>
> Hmm.. I thought you could digi through any assigned alias on the
TNC.
> What
> about utilizing mynode then?
>
> Chris
>
> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org 
> [mailto:aprssig-bounces at lists.tapr.org] 
> On Behalf Of Eric H. Christensen
> Sent: Tuesday, December 21, 2004 10:54 PM
> To: 'TAPR APRS Mailing List'; 'Wes Johnston'
> Subject: RE: [aprssig] LinkN-N for dummies
>
> The "mypbbs" alias is only for accessing the onboard mailbox and
will
> do nothing for APRS.
>
>
> 73s,
> Eric KF4OTN
> kf4otn at amsat.org 
>
> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org 
> [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Chris Schwab
> Sent: Tuesday, December 21, 2004 22:48
> To: 'Wes Johnston'; 'TAPR APRS Mailing List'
> Subject: RE: [aprssig] LinkN-N for dummies
>
>
> I thought of using the "mypbbs" alias and setting that to wide2-2.
> That plan covers almost every conceivable need in our area right
now.
>
> Chris
>
>
> -----Original Message-----
> From: Wes Johnston [mailto:wes at kd4rdb.com] 
> Sent: Tuesday, December 21, 2004 10:43 PM
> To: TAPR APRS Mailing List; Chris Schwab
> Subject: RE: [aprssig] LinkN-N for dummies
>
> Yes it makes sense... I didn't know what everyone would want to do
> with 2 extra aliases... so I made them WIDE2-2 and WIDE3-3... I can
> update FL to this if you wish.
>
> Wes
> --
>
>
>
> Quoting Chris Schwab <1schwab1 at tampabay.rr.com>:
>
> > Wes:
> >
> > One thought - I assume that if you're going to use the thought of
> > using
> your
> > ARRL section instead of the state, you'd change that correct?
> > (Actually, I know the answer, I'm just bringing it up).
> >
> > I've proposed the following to our local area:
> >
> > UIDIGI ON RELAY,WIDE,TBW,WCF (covers our section & weather service
> > office) UIFLOOD 75LNK,30,NOID UITRACE FL,30
> >
> > Does this make sense?
> >
> > 73,
> > Chris N4BSA
> >
> >
> > -----Original Message-----
> > From: aprssig-bounces at lists.tapr.org 
> [mailto:aprssig-bounces at lists.tapr.org] 
> > On Behalf Of Wes Johnston
> > Sent: Tuesday, December 21, 2004 9:22 PM
> > To: aprssig at lists.tapr.org 
> > Subject: [aprssig] LinkN-N for dummies
> >
> > Well, not quite.... Reading thru all the emails about linkN-N and
> > SSn-n on the
> > sig lately has surely confused some.   Here's a page that tells
the
> > preferred
> > setup for kpc3 digis in each state - including linking the
> > interstates.
> >
> > http://www.kd4rdb.com/aprs/istates.html 
> >
> > Wes
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at lists.tapr.org 
> > https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig 
> >
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at lists.tapr.org 
> > https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig 
> >
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org 
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig 
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org 
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig 
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>





More information about the aprssig mailing list