[Xastir] IGATE

[Curt Mills, WE7U]

On Fri, 18 Jul 2003 wes at johnston.net wrote:

> You are right... never thought about it from an abuse standpoint.  I suppose I
> never considered that more than one station would be sending a packet intended
> for the same area...

It can be intended or unintended abuse, and the remote user has no
way to judge the channel activity, as you mentioned.


> That leads us right to a buffer to store a list of calls which have
> recently been GATED to RF and should not be gated again for x seconds, or a
> parm for a cap of max activity an IGATE can inject.  Boy does that add
> complexity.

It might get very tricky to do, and might have to be separate from
regular messaging to assure that messaging would get through in any
case.  Some of that could be critical messages in/out of a
devastated area.


> Given that we *can* do this w/o any additional buffers/counters, I cobbled up a
> simple IF THEN around the IGATE function with a fixed callsign of SMS in it.  I
> may play with it at home to see how it behaves.

You did the easy part.  Unless you've done X11 stuff before, it can
be very tricky.  Most people won't touch the GUI.  Segfaults galore
if you do it wrong, with little debugging info to tell you why.


> Man, this is the WONDERFUL
> thing... I can play and tweak and not depend on the Bros Sproul for yearly
> updates.  All's I gotta do now is find how a variable name can be define in the
> IGATE setup dialog box.

I get real upset now when I find something in a program I don't
like and I don't have the sources or a development system to change
it.

-- 
Curt Mills, WE7U                    hacker_NO_SPAM_ at tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto:    A tax on people who are bad at math!"
"Windows:  Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"