[OZAPRS] VK3 IGate / Zone system.

Ron Perry ronk at sunlinux.com.au
Tue Nov 7 23:07:56 EST 2006 

On Tue, 2006-11-07 at 22:09 +1100, Dion Bramich wrote:
> On Tue, 07 Nov 2006 21:54:25 +1100, Ron Perry <ronk at sunlinux.com.au>
wrote:
> 
> > On Tue, 2006-11-07 at 19:54 +1100, Mike Townsend wrote:
> >> Hypothetical question.
> >>
> >> I'm in Melbourne from Mildura on business driving around with APRS.
The  
> >> good
> >> lady at home is keeping an eye on my where abouts with an RF only
APRS
> >> setup. How do I  set my tracker so the beacons only go up the RF path

> >> to the
> >> Mildura region?
> >> Would using a designated ZONEn-n make this easier or complicate the  
> >> process?
> >>
> >>
> > How it happens now. Please note that VK3WRM is and has always been
apart
> > of the 145.175MHz APRS network...we just have to remember to change
> > frequencies when travelling south. :-/
> > Being a local, you would have your posits broadcast locally, via the
> > Igate,  VK3WRM. A Melbourne Igate would hear your posit directly or
> > indirectly. As there has been no demand, we currently don't broadcast
> > the whole state of Vic's traffic,  but I have in the past on request.
> >
> > If you used MILDn-n in Melbourne unless seen direct by an Igate, then
> > they would be ignored. (I suspect)
> > Would all the Igates broadcast it?
> >
> > The change in the Vic Frequency would not change the operation.
> >
> > Zonen-n packets I can see being used only by Igates and should be used
> > to limit the broadcast of Internet sourced data. I don't think there
is
> > a need for home stations to adopt Zonen-n, unless they were being
heard
> > by 2 RX Igates, and wanted a choice.
> >
> > Your thoughts?
> >
> 
> My thoughts, youve seen the light!  How is there another way you can  
> prevent I-Gate traffic from arriving here, NSW or VK5?  Simple path  
> limiting doesnt account for propagation, there is a path from Mt Barrow
to  
> many well sited digis in Victoria more often than not.  ZONE-ing doesnt

> have to be limited to I-Gates though, I will be using a ZONEd path here,
I  
> simply dont wish to be seen in Victoria via RF only.  One less packet of

> mine that traverses that path makes room for one more mobile or message.
> 
You didn't state Igate traffic only so I assumed all users. (Unless I
skimmed some posts)
However we can (and do locally) limit by using a direct path for
traffic.  

And by the way, while I was on Mt Hotham on Sunday I did see a VK7
packet..but I'll have to check the D700 on my bike for more info.  :-)

Ron


> Dion.
> 

> 
> > Regards,
> > Ron
> > vk3ecv
> >
> >
> >> ----- Original Message -----
> >> From: "Richard Hoskin" <vk3jfk at amsat.org>
> >> To: "'VK / ZL APRS Users'" <ozaprs at aprs.net.au>
> >> Sent: Tuesday, November 07, 2006 6:30 PM
> >> Subject: Re: [OZAPRS] VK3 IGate / Zone system.
> >>
> >>
> >> > Dion,
> >> >
> >> > This is a flexible system that uses the UI-Digi Pre-emptive  
> >> digipeating.
> >> >
> >> > Don't think of it in the terms that are being discussed here with
> >> > SSn-n/Zonen-n as it uses a different concept based on cells with an
> >> > Internet
> >> > backbone. It is a holistic coverage approach that minimises traffic

> >> while
> >> > providing all station with a full view of the network on RF.
> >> >
> >> > The system is transparent to the users, they only need to set a
path  
> >> of
> >> > RELAY,WIDE (or WIDE1-1,WIDE2-1) for mobiles and 'Their closest  
> >> digi',WIDE
> >> > for home stations. We've tried to used the KISS principle but for  
> >> those
> >> > that
> >> > need a little extra help with a local path they can visit
> >> > http://vk3.aprs.net.au/packet_path_guide.htm
> >> >
> >> > Once setup there is no additional maintenance required and some  
> >> redundancy
> >> > is built in.
> >> >
> >> > Cheers
> >> > Richard
> >> > VK3JFK
> >> >
> >> >
> >> >> -----Original Message-----
> >> >> From: ozaprs-bounces at aprs.net.au
[mailto:ozaprs-bounces at aprs.net.au]  
> >> On
> >> >> Behalf Of Dion Bramich
> >> >> Sent: Tuesday, 7 November 2006 5:22 PM
> >> >> To: VK / ZL APRS Users
> >> >> Subject: Re: [OZAPRS] VK3 IGate / Zone system.
> >> >>
> >> >> How do you limit traffic to one zone?  How do you do interzone  
> >> routing
> >> >> without involving other zones? How do you identify/define the
zones
> >> >> easily?  How do you explain in simple terms to a newcomer how to
> >> >> configure
> >> >> his path?  IMHO you have a unnecessarily high maintenance, hard to
> >> >> understand system.
> >> >>
> >> >> Dion.
> >> >>
> >> >>
> >> >> On Tue, 07 Nov 2006 17:04:22 +1100, Richard Hoskin
<vk3jfk at amsat.org>
> >> >> wrote:
> >> >>
> >> >> >
> >> >> > This is a brief explanation of the way IGates are zoned in VK3,
Mt
> >> >> > Gambier
> >> >> > (VK5) & southern NSW (VK2).
> >> >> >
> >> >> >
> >> >> >
> >> >> > Summary
> >> >> >
> >> >> >
> >> >> > To maintain high levels of efficiency and provide the widest  
> >> possible
> >> >> > mobile
> >> >> > coverage on the APRS Network it is important to have a  
> >> well-designed
> >> >> > network
> >> >> > based on a sound strategy. To this end the APRS network has been
> >> >> > divided
> >> >> > into Zones, which are linked together by the internet through  
> >> IGates.
> >> >> The
> >> >> > concept is similar to the GSM mobile phone network.
> >> >> >
> >> >> >
> >> >> > Details
> >> >> >
> >> >> > An IGate Zone is an area that is covered by a single RX Only  
> >> IGate. The
> >> >> > Zone
> >> >> > extends a maximum of 2 hops (Wide Digipeaters) from the RX Only

> >> IGate.
> >> >> > The
> >> >> > RX Only IGate is located as close as possible to the centre of
the
> >> >> > Zone.
> >> >> >
> >> >> >
> >> >> > The central TX IGate injects local internet APRS traffic into
the  
> >> RF
> >> >> > network
> >> >> > which propagates through the state's RF network. This reduces
the
> >> >> > possible
> >> >> > complications of hidden transmitters and timing issues allowing

> >> for a
> >> >> > more
> >> >> > efficient RF system. It also means that data entering the system

> >> from
> >> >> any
> >> >> > one of the zones RX Only IGates is propagated through all other

> >> zones
> >> >> via
> >> >> > the central TX IGate. This again reduces network traffic while
> >> >> > providing
> >> >> > a
> >> >> > mechanism which allows the APRS users data to propagate through

> >> the RF
> >> >> > Network.
> >> >> >
> >> >> >
> >> >> > An IGate Zone is defined in detail in the document 'APRS Network

> >> Design
> >> >> > for
> >> >> > VK3'. For an explanation on Wide Digipeaters read the document  
> >> 'APRS
> >> >> > New
> >> >> > User Path Information Guide'
> >> >> >
> >> >> >
> >> >> > Traffic levels are the greatest limiting factor in the size of
the
> >> >> > IGate
> >> >> > Zone.
> >> >> >
> >> >> >
> >> >> > To prevent packet duplication and network looping problems,
(that  
> >> very
> >> >> > quickly overload the local RF network) only one RX Only IGate
per  
> >> Zone
> >> >> is
> >> >> > used. It is also much more cost effective to have only one IGate

> >> in a
> >> >> > zone.
> >> >> >
> >> >> >
> >> >> > The RX Only IGates will also function as a local message gateway

> >> which
> >> >> RX
> >> >> > and TX local APRS messages for the area. The coverage area of
the  
> >> Local
> >> >> > message zone is considered to be a maximum of two hops from the

> >> local
> >> >> > RX
> >> >> > Only IGate. The local RX Only IGate shall have a path of APRS
via  
> >> "the
> >> >> > Local
> >> >> > Wide Digi",WIDE.
> >> >> >
> >> >> >
> >> >> > APRS 'Wide Digipeaters' are currently programmed to digipeat the
> >> >> > alias's
> >> >> > RELAY, WIDE, TRACE, INETZ[x], WIDEn-N, Tracen-N.
> >> >> >
> >> >> >
> >> >> > Victorian Zones
> >> >> >
> >> >> >
> >> >> > Victoria has been divided into 6 IGate Zones; 5 Zones operate RX

> >> Only
> >> >> > IGates
> >> >> > and 1 Zone is the main State TX IGate as well as the local RX
IGate
> >> >> >
> >> >> >
> >> >> > The IGate Zones are listed below.
> >> >> >
> >> >> >
> >> >> >
> >> >> > IGate Zone
> >> >> >
> >> >> > IGate Callsign
> >> >> >
> >> >> > Designation
> >> >> >
> >> >> > RX Coverage Area
> >> >> >
> >> >> > APRS Digipeaters Covering Area
> >> >> >
> >> >> >
> >> >> > 1
> >> >> >
> >> >> > VK3SB-1
> >> >> >
> >> >> > TX/RX
> >> >> >
> >> >> > Melbourne, Ballarat, Geelong
> >> >> >
> >> >> > VK3CV-1, VK3RMD-1, VK3RBU-1, VK3JFK-1 (VK3ROW-1)
> >> >> >
> >> >> >
> >> >> > 2
> >> >> >
> >> >> > VK3JTM-5
> >> >> >
> >> >> > RX Only
> >> >> >
> >> >> > Western Victoria, South Eastern South Australia,
> >> >> >
> >> >> > VK3RPG-2, VK3SSS-1, VK3RMK-1, VK5JFK-1, VK3KAY-1
> >> >> >
> >> >> >
> >> >> > 3
> >> >> >
> >> >> > VK3JFK
> >> >> >
> >> >> > RX Only
> >> >> >
> >> >> > (Backup TX)
> >> >> >
> >> >> > North Central Victoria, Southern NSW
> >> >> >
> >> >> > VK3RMG-1, VK3YWY-1, VK3RCV-1, VK3ECH-1
> >> >> >
> >> >> >
> >> >> > 4
> >> >> >
> >> >> > VK3VHF-1
> >> >> >
> >> >> > RX Only
> >> >> >
> >> >> > Gippsland
> >> >> >
> >> >> > VK3ZV-1, VK3RGI-1,VK3REB-1, VK3BLE-1, VK3VHF-1
> >> >> >
> >> >> >
> >> >> > 5
> >> >> >
> >> >> > VK3KAW
> >> >> >
> >> >> > RX Only
> >> >> >
> >> >> > North East Victoria, Southern NSW
> >> >> >
> >> >> > VK3RGR-1, VK3RAW-1, VK2RBY-1, VK3RLE-1, VK3HJQ-1
> >> >> >
> >> >> >
> >> >> > 6
> >> >> >
> >> >> > VK3WRM
> >> >> >
> >> >> > RX Only
> >> >> >
> >> >> > North West Victoria
> >> >> >
> >> >> > VK2RBX-1, VK3RON-1
> >> >> >
> >> >> >
> >> >> >
> >> >> > Cheers
> >> >> >
> >> >> > Richard
> >> >> >
> >> >> > VK3JFK
> >> >> >
> >> >> >
> >> >> > _______________________________________________
> >> >> > Ozaprs mailing list
> >> >> > Ozaprs at aprs.net.au
> >> >> > http://aprs.net.au/mailman/listinfo/ozaprs
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Using Opera's revolutionary e-mail client:
http://www.opera.com/mail/
> >> >> Send instant messages to your online friends
> >> >> http://au.messenger.yahoo.com
> >> >> _______________________________________________
> >> >> Ozaprs mailing list
> >> >> Ozaprs at aprs.net.au
> >> >> http://aprs.net.au/mailman/listinfo/ozaprs
> >> >
> >> > _______________________________________________
> >> > Ozaprs mailing list
> >> > Ozaprs at aprs.net.au
> >> > http://aprs.net.au/mailman/listinfo/ozaprs
> >> >
> >> >
> >> >
> >> > --
> >> > No virus found in this incoming message.
> >> > Checked by AVG Free Edition.
> >> > Version: 7.1.409 / Virus Database: 268.13.29/520 - Release Date:  
> >> 6/11/2006
> >> >
> >> >
> >>
> >> _______________________________________________
> >> Ozaprs mailing list
> >> Ozaprs at aprs.net.au
> >> http://aprs.net.au/mailman/listinfo/ozaprs
> >
> > _______________________________________________
> > Ozaprs mailing list
> > Ozaprs at aprs.net.au
> > http://aprs.net.au/mailman/listinfo/ozaprs
> 
> 
> 

_______________________________________________
Ozaprs mailing list
Ozaprs at aprs.net.au
http://aprs.net.au/mailman/listinfo/ozaprs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://second.aprs.net.au/pipermail/ozaprs/attachments/20061107/8bbb02e4/attachment.htm

More information about the Ozaprs mailing list