<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY BGCOLOR="#ffffff">
This is the filter in question ...<BR>
<BR>
<B>saDefaultFilter14577=m/100 e/WXSVR-AU</B><BR>
<BR>
I've just selected 1/2 a dozen T2's to see there port listings and it kind of looks like there isn't a "set" standard! but that's not to say that there shouldn't be some consistency across the three T2's here in OC! However, there is a push to make all stations use port 14580 and roll there own filters! for some this can be a little off putting IMHO! Most would be unaware that there are individual state filters from 10142-10148 with the last digit being the state ID (VK1/2 are combined!)<BR>
<BR>
Here in VK7 a 100km radius really only leaves you covering yourself as the three main populated areas are greater than 100km apart! so wondering if the 100km should be bumped to 200km? its only one figure to change in the configuration file!<BR>
<BR>
So I'm agreeable with Tony on this! <IMG SRC="cid:1252803357.7661.26.camel@scott-desktop.vk7hse.hobby-site.org" ALIGN="middle" ALT=";)" BORDER="0"><BR>
<BR>
<BR>
On Sun, 2009-09-13 at 09:30 +0930, Tony Hunt wrote:
<BLOCKQUOTE TYPE=CITE>
Heres something for the Internet server operators to think about. I notice some inconsistencies in the Port functions. Also Ive got some sugestions for the Port settings in line with this.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
Looking at Port 14577 . On First and Second aprs.net.au this is a 100km radius filter. On Third aprs.net.au its a 200km filter. So if I use rotate.aprs.net.au:14577 then 2/3 of the time I get a 100km radius and 1/3 of the time I get a 200km filter.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
I actually like the 200km idea. In VK5 particularly in country areas 100km isnt a very long way and often does not get you to anywhere significant or prove overly useful. 200km is more useful. We are looking at the possibility of putting a remote Igate in the country area using something simple managable and stable.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
I realise we can use a custom filter on Port 14580 provided the software we use lets us set up a filter. Which takes me to aprsd. I see some folks are still using aprsd which is still being supported in a few operating systems via software repositries. Its a simple no fuss Igate solution. Not the greatest but its stable and tested. It wont do custom filtered logins though.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
You can doctor the source code and make it do a custom filtered login if you want to recompile it. Not overly easy for some and messy.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
So with all that heres my suggestion. Why not have a standard 100km radius filtered port and also a standard 200km filtered port on each of these servers ? If you want the rotate system to work sensibly then some co-ordination between them would be good. Each of the sysops must talk to each other in some way you would hope.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
It seems perhaps that there are different needs in different areas as demonstrated by the 200km port on third.aprs.net.au.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
So lets cover some of these possibilities I say.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
Tony Hunt VK5AH <A HREF="mailto:wavetel@internode.on.net">wavetel@internode.on.net</A><BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
_______________________________________________
OZAPRS mailing list
<A HREF="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</A>
<A HREF="http://lists.aprs.net.au/mailman/listinfo/ozaprs">http://lists.aprs.net.au/mailman/listinfo/ozaprs</A>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Scott Evans <<A HREF="mailto:scott@vk7hse.hobby-site.org">scott@vk7hse.hobby-site.org</A>>
</TD>
</TR>
</TABLE>
<br>
--
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately
by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified
that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
<br>
</BODY>
</HTML>