[aprssig] Designating HOME Igates

Robert Bruninga bruninga at usna.edu
Fri Jun 17 16:39:48 CDT 2005

Designating a HOME IGATE:

I proposed that back in 1994 or so.  I called it level-4
routing.  And when IGates came out, I called it "HOME"
routing and  proposed it again to the IGate writers.

It is a VERY simple conecpt and very simple to 

1) Everyone that travels, choses his LOCAL IGate
    as where he wants his position to go to RF.

2) His IGate then will always send his position from
the internet to RF whenever his position is received
from the interenet AND it is more than X miles from
the IGate.


Problem is, to do it with existing software requires one-
for-one listing by the IGate operator of every local who
wants to travel, and thus a maintenance nightmare
for said IGate operator.  This never works in HAM
radio.  Eventually the operator gets tired of all
the work and just drops the whole thing.

So my proposal was to let the USER send a
message to the IGATE with something like:
"You are my HOME IGATE beyond 100 miles.
 please Gate me to RF"
or words to that effect, like maybe abbreviated
to "HOME > 100".

Then when someone is traveling they just pull
out their HT, enter the "HOME" message to
the call of the local IGate and it is DONE.

PART-2.  BUT, for safety, too, the IGATE must
watch ALL requests for HOME from all stations
and so whenever anyone asks for another 
IGate to "HOME" him, then ALL IGates seeing
that message will REMOVE this station from
their HOME lists.

Thus, users dont have to remember where they
homed before, but can just send out a new HOME
message and all prior entries will be canceled and
only the new HOME Igate will pick it up.

Done.  Automatic,  Initiated by end user.
All it takes is a little IGate code.


>>> w2pi at optonline.net 06/17/05 2:46 PM >>>
This raises an intesting point - as I understand it, if you want to track one station (the traveller) from another (home) that are more than a hop or two apart, you have two choices:

1. Use a long path that generates QRM over a wide radius, or

2. Use a short path to reach an Igate from the "traveller", then track the traveller from "home" via the internet.

If you don't have access to the internet from "home", for whatever reason, option 2 doesn't work.

Is there an existing path mechanism that would route data over the air from a "traveller" to a nearby Igate, then back to the airwaves from a specific Igate close to "home".

Perhaps something like W1-1, W1-2, [home Igate callsign]?

This would use the internet like a wormhole to get the data off the air where it isn't needed, but put it back on the air in a specific region. This way the only packets that would be on the air would be those right around the "traveller" and those close enough to "home" to be monitored.

Just my ramblings...

Paul , W2PI

----- Original Message -----
From: n4qwf at ntelos.net 
Date: Friday, June 17, 2005 1:36 pm
Subject: Re: RE: [aprssig] Universal digi path

> Thanks for the info. I sure was wondering there what had happened. 
> Guessthe sensitivity might be the problem. I never had any trouble 
> from the
> high rise at Oregan Inlet till this trip.
> I hope at some point a digi path that will work anywhere will be 
> resolvedfrom all the changes that have been made. Concerns over 
> congestion seems
> to have disrupted the travelers ability to get back to home area. 
> Well, we
> will see what comes of it all after things have a chance to settle 
> down. I
> would hope that at some point the traveler will be able to set a 
> path and
> be seen anywhere. Again thanks for the help. 73's << John
> > Just to let you know that the digi that covers the outer banks does
> > support WIDEn-N and SSn-N but is having some antenna problems. A 
> local> Igate also  supports RELAY and, WIDE1-1. If you go far 
> south on the outer
> > banks there is no APRS coverage. Also the digis that had WIDEn-N 
> removed> it has been put back in.
> >
> > John
> > KE4TZN
> >>
> >> From: "Cap Pennell" <cap at cruzio.com>
> >> Date: 2005/06/16 Thu PM 10:57:46 EDT
> >> To: "TAPR APRS Mailing List" <aprssig at lists.tapr.org>
> >> Subject: RE: [aprssig] Universal digi path
> >>
> >> Have you tried plain WIDE2-2 ?  I see stations nearby you using it
> >> successfully.  Good luck.
> >> Some digis "cut-off" WIDE3-3 as too broad, but allow WIDE2-2 (or
> >> WIDE1-1,WIDE2-1).
> >> 73, Cap KE6AFE
> >>
> >> > -----Original Message-----
> >> > From: aprssig-bounces at lists.tapr.org 
> >> > [aprssig-bounces at lists.tapr.org]On Behalf Of n4qwf at ntelos.net 
> >> > Sent: Thursday, June 16, 2005 17:09 PM
> >> > To: aprssig at lists.tapr.org 
> >> > Subject: [aprssig] Universal digi path
> >> >
> >> >
> >> > Here I am on the outer banks of North Carolina. I was here 
> two weeks
> >> ago
> >> > and enjoyed seeing my position reported on Findu without any 
> problem.>> I
> >> > was using the Tiny track and Kenwood V7A in my wifes car 
> then. I am
> >> sure
> >> > the Proto path was set to Wide3-3. While I have been here 
> this week
> >> using
> >> > my D700 and the same path I don't see my position digipeated. 
> I see
> >> other
> >> > stations on my screen without any trouble and the node shows 
> up all ok
> >> but
> >> > no ack of my postion. I setup my D7 HT and monitored my 
> transmissions>> and
> >> > I showed up on my Winaprs map here at the house so I know I 
> am sending
> >> a
> >> > good positions. When I left home the Wide 3-3 worked just 
> fine till I
> >> got
> >> > to Currituck and then it stopped working. My question is has 
> the alias
> >> of
> >> > the path been changed or something. I have tried the call of 
> the node,
> >> > Wide, Wide1-1, Wide3-3, relay, NC1-1 among many proto paths 
> without>> any
> >> > lucky. I would think there should be a path setting that 
> should work
> >> > regardless of where you travel. If that is not the case what 
> is a
> >> fellow
> >> > to do while on the road. After all that is what APRS was 
> supposed to
> >> be
> >> > about I thought. Well maybe someone can clue me in on what gives.
> >> Thanks
> >> > for any help! 73's << John
> >> >
> >>
> >>
> >>
> >> _______________________________________________
> >> 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 

aprssig mailing list
aprssig at lists.tapr.org 

More information about the aprssig mailing list