<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>RE: [Dxspider-support] Filtering Issues - Updated</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Hi,</FONT>
<BR><FONT SIZE=2>Found the reference to the usdb file, downloaded it off the dxcluster site, and built it up. Implemented a state-based filter on my own callsign as a test, presuming that if that worked ok for blocking spots from my screen, an appropriately installed input filter on the node I am connected to would do the same thing for all the incoming spots to my cluster. Have not had a chance to check it exhaustively, but seems to work. Upside is that it catches the 'out-of-call-area' callsigns correctly. The presumable down side would be that this file goes out of date periodically? I am guessing it would take quite a while for it to be enough out of date to matter, but just wondering if there is a mechanism to update this file periodically by downloaded an update and rebuilding it? Is that something that is supported on the dxcluster site, or is there an FCC site that has the file? Mostly just curious at this point.</FONT></P>
<P><FONT SIZE=2>Lastly, since state filtering appears to work, this is also a very low priority question, but wondering if there are any thoughts on the zone 4 filter being so 'wide' problem I started this thread with. Would a newer cty.dat file have any effect on this? Any other ideas?</FONT></P>
<P><FONT SIZE=2>Thanks,</FONT>
</P>
<P><FONT SIZE=2>ML</FONT>
</P>
<BR>
<BR>
<BR>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: charlie carroll [<A HREF="mailto:k1xx@ptcnh.net">mailto:k1xx@ptcnh.net</A>]</FONT>
<BR><FONT SIZE=2>Sent: Tuesday, February 18, 2003 4:10 PM</FONT>
<BR><FONT SIZE=2>To: The DXSpider Support list</FONT>
<BR><FONT SIZE=2>Subject: Re: [Dxspider-support] Filtering Issues</FONT>
</P>
<BR>
<P><FONT SIZE=2>Mike:</FONT>
<BR><FONT SIZE=2>The spots were not from me. However, I'm sure there may have been spots</FONT>
<BR><FONT SIZE=2>from my node. When you say spots from CA stations, are they from a CA</FONT>
<BR><FONT SIZE=2>user or a CA node? As I said previously, the filter is against the user</FONT>
<BR><FONT SIZE=2>and not the node.</FONT>
</P>
<P><FONT SIZE=2>I would not edit cty.dat. I think the issue is still one of</FONT>
<BR><FONT SIZE=2>configuration.</FONT>
</P>
<BR>
<P><FONT SIZE=2>73 charlie, k1xx</FONT>
<BR><FONT SIZE=2>The Changes file is located in the /spider directory.</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>Dxspider-support mailing list</FONT>
<BR><FONT SIZE=2>Dxspider-support@dxcluster.org</FONT>
<BR><FONT SIZE=2><A HREF="http://www.tobit.co.uk/mailman/listinfo/dxspider-support" TARGET="_blank">http://www.tobit.co.uk/mailman/listinfo/dxspider-support</A></FONT>
</P>
</BODY>
</HTML>