<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<font face="Arial">Scott,<br>
<br>
Not OT for me.<br>
<br>
Ray vk2tv<br>
</font><br>
<div class="moz-cite-prefix">On 20/12/19 11:10 pm, Scott Evans
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:BM1PR01MB3860ACC8F8DCA5649B0D5F72A62D0@BM1PR01MB3860.INDPRD01.PROD.OUTLOOK.COM">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black; ">
For the Tier2 servers T2TAS & T2SYDNEY(I'm the sysop of
T2TAS) they will reject all non verified stations. So if you
forget to include your pass code then you will be ignored by the
server for passing your traffic to the internet. I can't answer
on behalf of T2QLD or T2PERTH (is that still online?) and for
any of the ZL (New Zealand) based servers. Whereas I-Gates
generally don't do any filtering. Only exception to this would
be for RFONLY NOGATE to destinations.<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black; ">
I realise this is a little bit off the topic, but just wanted to
clarify the Tier2 internet side of things...<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black; ">
Cheers<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black; ">
VK7HSE Scott Evans <br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black; ">
<span id="OutlookSignature">
<div dir="auto" style="direction: ltr; margin: 0; padding: 0;
font-family: sans-serif; font-size: 11pt; color: black; ">
Get <a href="https://aka.ms/ghei36" moz-do-not-send="true">Outlook
for Android</a></div>
</span><br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b> OZAPRS
<a class="moz-txt-link-rfc2396E" href="mailto:ozaprs-bounces@aprs.net.au"><ozaprs-bounces@aprs.net.au></a> on behalf of Mark Jessop
<a class="moz-txt-link-rfc2396E" href="mailto:lenniethelemming@gmail.com"><lenniethelemming@gmail.com></a><br>
<b>Sent:</b> Friday, December 20, 2019 10:49:05 PM<br>
<b>To:</b> Australian APRS Users <a class="moz-txt-link-rfc2396E" href="mailto:ozaprs@aprs.net.au"><ozaprs@aprs.net.au></a><br>
<b>Subject:</b> Re: [OZAPRS] Foundation and RF APRS</font>
<div> </div>
</div>
<div>
<div dir="ltr">For positioning the use of an object is a good
way of having a valid foundation callsign show up on the
various mapping services. As you mention it still needs to be
sourced from an AX.25 compatible callsign when produced via
RF, but this could be a modified callsign as mentioned
previously. If the source callsign is valid from an AX.25
standpoint, then it should make its way through igates into
APRS-IS fine. Whether packets will make their way back *out*
of APRS-IS into RF is another good question - I'm not sure
what IS-RF filtering is used on the various TX-capable igates
around Australia.
<div>I'm not sure if any of the commonly available APRS
trackers (be it standalone devices like the
tinytrak/opentracker, or rigs like the various
kenwoods/yaesus) support emitting of objects instead of
position reports, so that will be a seriously limiting
factor.</div>
<div>Anyway, the above is a possible option for getting
packets out on RF that look show up nicely on a map or
APRS-capable device and don't require additional poking
around to find out the actual callsign. However, i suspect
finding trackers that will produce objects instead of
position reports may be difficult. (Hopefully I'm wrong on
that!)</div>
<div><br>
</div>
<div>As for the APRS-IS passcode, well there's also an online
calculator here: <a
href="https://apps.magicbug.co.uk/passcode/"
moz-do-not-send="true">https://apps.magicbug.co.uk/passcode/</a></div>
<div>It's just a hash function... I guess the original
designers of APRS-IS decided security-through-obscurity was
good enough :-/</div>
<div><br>
</div>
<div>73</div>
<div>Mark VK5QI</div>
</div>
<br>
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Fri, Dec 20, 2019 at
9:55 PM <<a href="mailto:vk7hse@gmail.com"
moz-do-not-send="true">vk7hse@gmail.com</a>> wrote:<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px
0.8ex; border-left:1px solid rgb(204,204,204);
padding-left:1ex">
<div lang="EN-AU">
<div class="x_gmail-m_-6672101710715272630WordSection1">
<p class="x_MsoNormal"><span>APRS also has the option to
add an object to a map, it is with this that you
could provide the Foundation callsign. In most cases
in the US where special event stations are in use
they are not using the primary ax25 mycall as a
station identifier but instead using the object to
place the operators valid callsign. Now this doesn’t
address the protocol layer restriction for ax25, as
that’s hard coded and restricted to XXNXXX (or
variations thereof) As Australian Foundation
callsigns (decided to be the better choice in 2005)
have the XXNXXXX suffix I believe this was chosen
with the intention to prevent foundation calls from
“accidently” trying to use packet radio, and if that
was the case then it was a bit silly. But it is what
it is and now that the foundation call is permitted
digital modes (something I feel they should have
always had access to) that decision in 2005 has come
back to bite them (whoever they were at the time!)
</span></p>
<p class="x_MsoNormal"><span> </span></p>
<p class="x_MsoNormal"><span>Granted I haven’t read the
determinations to the letter in recent months, but a
station ID is only required every “TEN” minutes, not
on “EVERY” transmission! Packet radio was always
overkill for that but it was logical that the
station ID be it’s callsign hence why the ax25
protocol has the limit of a 6 letter call.</span></p>
<p class="x_MsoNormal"><span> </span></p>
<p class="x_MsoNormal"><span>Now what can we agree upon
in the interim to be acceptable until the callsign
suffix for the foundation is resolved? Bearing in
mind that could take some time as there’s now 3
entities involved with the process (WIA, AMC &
ACMA)</span></p>
<p class="x_MsoNormal"><span> </span></p>
<p class="x_MsoNormal"><span>My take would be a tactical
name with the operator callsign in the status text
field (>VK7FABC John Citizen QE37pa) this would
work for all RF aprs clients but because of the use
of a tactical call it would be prohibited into the
APRS-IS side (unless you are sneaky and generate a
valid aprs pass code *the software for that is
available under GNU hint think Xastir)</span></p>
<p class="x_MsoNormal"><span> </span></p>
<p class="x_MsoNormal"><span>So that’s my initial
thoughts …</span></p>
<p class="x_MsoNormal"><span> </span></p>
<p class="x_MsoNormal"><span>Cheers…</span></p>
<p class="x_MsoNormal"><span> </span></p>
<p class="x_MsoNormal"><span>VK7HSE Scott Evans</span></p>
<p class="x_MsoNormal"><b><span lang="EN-US">From:</span></b><span
lang="EN-US"> OZAPRS <<a
href="mailto:ozaprs-bounces@aprs.net.au"
target="_blank" moz-do-not-send="true">ozaprs-bounces@aprs.net.au</a>>
<b>On Behalf Of </b>Jack Schultz<br>
<b>Sent:</b> Friday, 20 December 2019 12:45<br>
<b>To:</b> Australian APRS Users <<a
href="mailto:ozaprs@aprs.net.au" target="_blank"
moz-do-not-send="true">ozaprs@aprs.net.au</a>><br>
<b>Subject:</b> Re: [OZAPRS] Foundation and RF APRS</span></p>
<p class="x_MsoNormal"> </p>
<div>
<div>
<div>
<p class="x_MsoNormal">Hi Marcos (and Carlos),
interesting to read both your thoughts on the
topic.</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">Though my preference is
obviously to have a 'valid' callsign for AX.25,
what I use now is the best I could come up with.
Every packet contains my full callsign in the
comment, which I think works well for those that
use APRS through a PC interface, but not as
handy in a mobile rig or handheld where my full
call is hidden behind several screens.</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">My thinking is that while
transmitting my full callsign makes it a legal
transmission, I should try and fit as much as
possible in the designated callsign field, with
the lowest priority being the leftmost part of
the callsign since it is the least specific.</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">I hear a similar take on
local repeaters where there is a usual crowd
that chats to each other, often simply omitting
'VK' altogether when referring to each others
callsigns, or the callsign of a repeater for
example. In the world of APRS, I feel there is a
similar level of community in that aspect within
the local RF zone. I generally see a dozen or so
core users, so there is that immediate
recognition when I decode one of their packets.</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">In Melbourne I've also seen
VK3FSPD using APRS first as VKFSPD, then using
3FSPD. I prefer the latter form as it avoids
ambiguity when travelling interstate.</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<p class="x_MsoNormal">Regards,</p>
</div>
<div>
<p class="x_MsoNormal">Jack Schultz</p>
</div>
<div>
<p class="x_MsoNormal">VK3FJTS (3FJTS-7)</p>
</div>
</div>
</div>
</div>
_______________________________________________<br>
OZAPRS mailing list<br>
<a href="mailto:OZAPRS@aprs.net.au" target="_blank"
moz-do-not-send="true">OZAPRS@aprs.net.au</a><br>
<a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.aprs.net.au/mailman/listinfo/ozaprs</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OZAPRS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>
<a class="moz-txt-link-freetext" href="http://lists.aprs.net.au/mailman/listinfo/ozaprs">http://lists.aprs.net.au/mailman/listinfo/ozaprs</a>
</pre>
</blockquote>
<br>
</body>
</html>