I don't believe this is going to get better or be resolved until a
serious open source project, with good architecture and management,
takes hold. There are many of us who would work on such a project,
but it seems all of the legitimate developers get spooked off of
publishing the information that would enable and accelerate it (Icom
controller to gateway protocol and full disclosure of the on air
packet structure, and optionally the G2 authentication and management
protocols - though I think G2 is not the right implementation).
Robin's code is subservient to G2 (or G4ULF's gateway) not an
integrated or peer piece of code.
On Aug 11, 2009, at 9:15 AM, k7ve wrote:
Remember Robin's code is not part of the gateway. It eavesdrops
(packet sniffs) the data going in to and out of the gateway daemons
to locate packets that it believes it needs deal with, then
transports them over a separate Internet port to other DPLUS based
systems, either reflectors, DV Dongles, or other DPLUS equipped
gateways and proxies (packet insertion) local delivery out to the
controller. DPLUS has no control over native D-STAR routing
(callsign) or Icom's gateway enhancements (/callsign and
multicasting). The only thing he can affect is DPLUS behavior,
Nate's solution is a good one and could be setup as a configurable
parameter.
- John, K7VE
John D. Hays
Amateur Radio Station K7VE
PO Box 1223
Edmonds, WA 98020-1223 VOIP/SIP: [email protected]
Email: [email protected]
