Infrastructure Config, was Re: [aprssig] RE: Not Receiving Messages from APRS-IS (Pete Loveall AE5PL Lists)
jmaslak-aprs at antelope.net
Tue May 20 07:42:51 CDT 2008
On May 19, 2008, at 10:00 PM, Jeff Kunce wrote:
> I talked to a couple of nearby IGATE operators - they both control
> their internet-to-rf messages by a "white list" of calls allowed to
> receive messages from the internet. Both offered to add me to their
> list, and both are of the notion that "that is the way it should be
> set up." But both were open to other suggestions from the experts on
> the TAPR list.
They should generally use the basic IGate algorithm, no white or
black lists. That is, if the IGate hears a station on RF in the last
half hour or so (can't remember the exact time), and sees a message
on the internet stream with that station as a destination, it
automatically gates it.
That lets travelers use the network and keeps people from adding
another IGate to solve what they think is a problem with a broken IGate.
I've seen a bunch of very strangely configured infrastructure lately
- for instance, digis set with aliases of WIDE2-2, so they *only*
digipeated paths with WIDE2-2 (not WIDE2-1 or WIDE1-1!). This kind
of thing breaks the network, although I'm sure it isn't done
intentionally to break things - it just happens to.
It would be great if there were some basic how-tos on configuring
digis and IGates. I know Bob has a bunch of info on his site, but it
is hard to find and just covers digis (I think) and doesn't include
UIView (which seems to me to be the most commonly misconfigured IGate
More information about the aprssig