[OZAPRS] QRM

Robert Bruninga bruninga at usna.edu
Mon Nov 13 06:27:20 EST 2006


> The point I'm  making is if they were ZONEd then I 
> wouldn't see them!  Simple as that.  If a sysop  
> running a IGate cant get thier head around ZONEing, 
> then they shouldnt be  Gating, IMO.  Its a simple concept.

It is a new idea, and so far, my hesitation is due to it being a
different application of the SSn-N concept which is valuable in
the USA, because it matches our ARRL community and disaster
communication organizations.  I have made numerous mention of
this in the OZ emails, but so far no one has given me any
insight into how amateur Radio public and emergency
communicaitons response nets are organized.  Maybe this means
that there is no such organization, hence, there are not
"communications" zones, hence, that is why my concepts are
falling on deaf ears.

If that is the case, then maybe it does make sense to use SSn-N
around Igates... In your area.  But until I knew for sure that
there was no organized amateur Radio Communications nets and
response organizations which needed their section communicaitons
on APRS, I would be hesitant to support the usurping of this
powerful capability for simply defining Igates. The problem is,
that most digis only support one type o SSn-N alias, so if you
use it for something trivial like Igates, then you prevent it
from ever being used for anything else...

Bob, Wb4APR


  If we want to see what theyre  
> currently forcing us too see at the moment, then we can 
> optionally IGate  
> it ourselves?  At the moment, average peak frames from 
> Victoria is 1 per  
> second, if that makes sense?  I have UISS alarm set to alert 
> me when a  
> match is found on a callsign, the callsign being VK3RGI-1.  
> Its not the  
> only digi RAA is hearing, and the voice in UISS cant speak 
> fast enough  
> sometimes!
> 
> Dion.
> 
> On Sat, 11 Nov 2006 23:31:33 +1100, Bob Bruninga  
> <bruninga at usna.edu>  
> wrote:
> 
> >> What are we going to do about this QRM??
> >> I and many others dont want to see this,
> >> its wasting VK7RAA's time.
> >
> > The packets appear to be IGate traffic.  In my opinion,
IGates in  
> > populated areas should not use any path longer than ONE (1) 
> hop to the  
> > nearest digipeaters.  This makes them an "own backyard" 
> problem.  If  
> > they still cause problems, then the problem is local and 
> can be fixed  
> > local.  But having IGate traffic go 2 hops polutes into 
> someone else's  
> > backyard where they have no control.
> >
> > But if VHF-1 IGate does need to use 2 hops and users in the 
> area of the  
> > RAA digi do not want to see it, then they can have the RAA 
> digi ignore  
> > packets from VHF-1...  Bob, WB4APR
> >
> > Fm VK3VHF-1 To APU25N Via VK3RGI-1,VK7RAA,WIDE2* <UI pid=F0
Len=95
> >> [22:37:43]
> > }VK3TSW>APU25N,TCPIP,VK3VHF-1*:=2335.02S/14852.19E-steve
@blackwater
> > swood at bkb.net.au {UIV32N}
> >
> > Fm VK3VHF-1 To APU25N Via VK3RGI-1,VK7RAA,WIDE2* <UI pid=F0
Len=103
> >> [22:37:47]
> > }VK3MY-4>APRS,TCPIP,VK3VHF-1*:)30m-GATE!3751.54SG14518.28E& 
> APRS HF To  
> > VHF
> > Gateway On 10.147.60Mhz USB
> >
> > Fm VK3VHF-1 To APU25N Via VK3RGI-1,VK7RAA,WIDE2* <UI pid=F0
Len=96
> >> [22:38:45]
> > }VK3TBN-10>APU25N,TCPIP,VK3VHF-1*:>201046z439.100MHZ IGATE 
> & DX Cluster
> > Greensborough Melbourne
> >
> > Fm VK3VHF-1 To APU25N Via VK3RGI-1,VK7RAA,WIDE2* <UI pid=F0
Len=54
> >> [22:38:46]
> > }VK3MR>APU25N,TCPIP,VK3VHF-1*:>110635zUI-View32 V2.03
> >
> >
> >
> > Dion.
> >
> 
> 
> 
> -- 
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://second.aprs.net.au/pipermail/ozaprs/attachments/20061113/d010d77a/attachment.htm 


More information about the Ozaprs mailing list