What I would LOVE to see would be to take one of the unused flag bits in the DV Header and use it to indicate of the transmission was initiated by the end user pressing their PTT, or if it is an automatic DPRS beacon transmission. Then, an enhancement to the G2 software (open gateway, etc.) could make a decision if that automatic DPRS beacon should be forwarded on to any linked D-Star servers.
It would be great to be able to drive around with my 2820 beaconing out DPRS packets without having them forwarded beyond the gateway. Mark (KB9KHM --- In [email protected], John Hays <j...@...> wrote: > > If the controller firmware would pass "ALL TRAFFIC" to the gateway the > whole "G" port thing could go away. A smarter piece of gateway > software could determine what needed relayed somewhere else and what > is just local repeater traffic. > > I have been thinking about the whole D-STAR routing paradigm and the > world would be much better if: > > A) Radios (RF) on D-STAR did not need to register - let the gateways > just update current location into a dynamic, distributed data store. > (FIlters at the gateway could manage who could and could not use a > given gateway - and callsign pattern matching, e.g. regex, could > filter out most bogus callsigns) > B) Only register "network devices" such as gateways, reflectors, > dongles, etc. and have things like dv dongles, autopatches, cross > service links (e.g. IRLP), run through servers that present them to > the D-STAR network. Redundant "trust servers" could maintain this > registry to remove the single point of failure. > > This would facilitate such things as mobile D-STAR stations moving > from repeater-to-repeater or port to port in real time. > Enable addressing services (reflectors, dv dongle type devices, nets, > etc.) directly in "UR" field. > > RPT2 could be used to route to a different repeater/port and eliminate > the whole "/repeater" syntax. > > -- John > > > On May 14, 2009, at 6:27 AM, Evans F. Mitchell KD4EFM wrote: > > > > From: Evans F. Mitchell KD4EFM [mailto:kd4e...@...] > > Sent: Thursday, May 14, 2009 9:11 AM > > To: '[email protected]' > > Subject: RE: 880 vs 800 (was: Re: [DSTAR_DIGITAL] Signal Distance) > > > > Any idea when the JARL will allow you all to install D-Plus??? > > > > As far as the R2 goes, > > > > DPLUS: with R2 ON, this will tell the RP2C to pass your data stream > > to the > > gw. > > If you where on a dongle, you connect to a US gw, if we DO NOT have R2 > > enabled or ON, > > you will not hear our transmission. When you omit R2 your data > > stream goes > > from > > the receiver to the RP2C, and right back out, with out any > > information going > > to > > a connected gateway. R2 set to the local gw callsign and G, the RP2C > > will > > send > > that data stream to the gw software, thus traffic can be heard from > > the > > repeater. > > > > > > D-PRS (APRS); with R2 ON, this will send your position data to the > > gw, and > > the > > DPRS program will then send it out to the aprs-is server stream and > > show > > your > > position on an aprs viewing program, jfindU, or other like program > > (including dstarusers.org) > > > > With D-PRS, yes, you will get the RPT? every transmission, that is > > because > > the RP2C > > has not been updated to understand the even though URCALL is CQCQCQ, > > the > > data > > stream is still meant for the gateway. Once there is a RP2C firmware > > update, > > things > > can be adjusted correctly then... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > John Hays > Amateur Radio: K7VE > j...@... > > > > [Non-text portions of this message have been removed] >
