[aprssig] Definitive digipeater specification?
Phillip B. Pacier ad6nh at arrl.netMon Feb 27 22:59:54 UTC 2006
- Previous message: [aprssig] Definitive digipeater specification?
- Next message: [aprssig] Definitive digipeater specification?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
X it is. You might want to also add the "A" to your description list as well, as that is where I got my information initially. Thanks. 73 Phil - AD6NH Robert Bruninga wrote: >>>>ad6nh at arrl.net 02/27/06 5:24 PM >>> >>>> >>>> >>A few of us are experimenting with AX.25 digipeating, >>using NSR... we are proposing to use the "A" >>overlay on these digis >> >> > >Actually, we are using the "A" overlay >for all ALT-INPUT digis that had the +600 >alternate input on 144.99. Maybe you could use >the X overlay for aX25? > >And you know I am opposed to NSR routing unless >it allows DIGI1,DIGI2,DIGIn... routing. >Remember, the 3 hop path above gets a packet >from point A to the desired Point B with only >3 copies And is the most efficient on-freq >method possible. This is FAR LESS load on the network >than even a WIDE2-2 packet which can generate >16 copies in some areas. > >There just is no on-freq digipeating method more efficient >for getting a packet from A to B then the directed >path. Unless you go to tunneling, gateways, backbones >and level 4 and of course, then it is not "digipeating" and >therefore not part of the argument. > >My position is that only the ORIGINATOR of a packet >knows where HE needs to communicate at any particular >instance. NSR is an attempt to give SYSOPS total >control and force all users into a one-size fits >all definition of what APRS and the users are (tracking >for example)... And that just kills the flexibility of the >system to respond to what a USER may need at any >given instant. > >In otherwords, NSR is a solution for the flooding >problem we used to have but so is New-N, and >New-N has significanly solved that problem everywhere >it is used. But New-N does not prohibit the very efficient >point-to-point intellligent use of the network when needed. >And New-N does not need re-configuration and detailed >SYSOP management at all digis each time a new digi >comes or goes. > >Good luck.... keep me posted on what you >learn and anything that we can learn from the >experiment. > >Bob, WB4APR > > >Robert Bruninga wrote: > > > >>Scott, >>use my New-N Paradigm as the "official" digipeating >>guide for APRS these days. >>http://www.ew.usna.edu/~bruninga/aprs/fix14439.html >> >>Bob, WB4APR >> >> >> >> >> >>>>>scott at opentrac.org 02/27/06 4:17 PM >>> >>>>> >>>>> >>>>> >>>>> >>Is there any 'official' explanation of exactly how a modern APRS digipeater is supposed to function? The AX.25 spec just covers the conventional digipeating. I think I have a pretty good handle on it, but I know there's been some inconsistency out there. Just want to make sure I'm working from the best source material available. >> >>A flow chart or state diagram would be great... >> >>Scott >>N1VG >> >> >>_______________________________________________ >>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 > > > > >
- Previous message: [aprssig] Definitive digipeater specification?
- Next message: [aprssig] Definitive digipeater specification?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
