Order Tray | Contact Us | Home | SIG Lists

[aprssig] Re: The Ultimate New WIDEn-N Paradigm

Eric Christensen kf4otn at earthlink.net
Mon Feb 7 19:12:20 UTC 2005

I completely agree.  If I use all of those in my UIDIGI setting, then that leaves no room for the weather LANs that I have been implementing.

The weather LANs look like "WXMHX" and allow I-Gates to send weather bulletins to RF and keep them within a specific area of interest and no further.


-----Original Message-----
From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Wes Johnston
Sent: Monday, February 07, 2005 13:42
To: Robert Bruninga
Cc: aprssig at lists.tapr.org
Subject: [aprssig] Re: The Ultimate New WIDEn-N Paradigm

Quoting Robert Bruninga <bruninga at usna.edu>:

> ULTIMATE New n-N Paradigm:
> Paradigm.  It cuts off WIDEn-N completely but inserts WIDE2-2, 
> WIDE2-1, WIDE3-3, WIDE3-2 explicitly as local

If we use UIDIGI set to WIDE2-2,WIDE2-1,WIDE3-2,WIDE3-1 , we've used up all four slots.  Fine, but what about support for RELAY?  The hierarchy has always been that low stations respond to one alias (relay) and higher stations respond to the lower aliases and additional aliases.  Do we run RELAY as MYALIAS?  We'll run into dupe problems, but it'll work...

I just read http://www.ew.usna.edu/~bruninga/aprs/kpc3+WIDEnCUT.txt and it shows UIDIGI ON RELAY,WIDE2-2,WIDE2-1,WIDE3-3 , so looks like you forfeited WIDE3-2 in lieu of RELAY.

> Also, the ID <==> NOID has gone away.  In fact, if SSn-N
> is used as the new UIFLOOD parameter, then ID should
> be enabled!  This is because, since WIDEn-N will now be
> fully traced, we will always get the point of entry digi. Also, since 
> the old method of forcing the first digi to ID with the path of 
> WIDE,WIDEn-N generated extra dupes, we dont want to encourage that any 
> more.  Therefore UIFLOOD SS,30,ID will support the very effiicient 
> path of SSn-N and so we may as well let the LAST digipeater
> ID itself...

I'm glad NOID will go away... I've wanted to develop some sort of intelligent routing scheme, but without the digi's not knowing their neighbors, it was impossible.  One of the problems with TheNET routing was the tables getting transmitted every 10 minutes got in the way of traffic.  If we can trace each packet, the digipeaters can passively learn their neighbors w/o any additional network load.  And, yes I recongnize that some RF links are asymetric.


aprssig mailing list
aprssig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig

More information about the aprssig mailing list