[Dxspider-support] Proper Setup of Filtering

[Dirk Koopman]

Mike

Filtering is 'simple', once you get your head around it :-)

The reason it doesn't work is because you are filtering your output, not
input.

acc/spot wr3d input by_zone 4

then (optionally, but it will save wr3d sending you stuff you don't
want) do:

rcmd wr3d acc/spot by_zone 4
 
Because users want to filter what is the 'output' of the node to them,
the syntax is as it is. What you want to do is to filter the 'input' to
your node. Only sysops need to do this. Hence the way around it is.

However, I believe what you actually want to do, to allow maximum
flexibility for your users is:-

clear/spots wr3d all
clear/spots wr3d input

acc/spots user_default by_zone 4

This will mean that your node continues to receive a full feed and (most
of / by default) your users will receive just spots generated by zone 4
people. To get both sides (ie by zone 4 people or to zone 4 people) do:

acc/spots user_default by_zone 4 or call_zone 4

If, at some future time, or they are looking for evidence of a call in
sh/dx they then have a full feed full of information available.

Dirk 

On Fri, 2003-02-14 at 15:53, Mike Lewis wrote:
> Hi,
> 
> I have finally gotten my Mandrake 9 hosted cluster running, and
> recently got setup to connect to the WR3D node. After a few problems
> that I think were self-induced, I have gotten my connect script
> working, and can now connect to the WR3D node. My problem is, however,
> that I would like to limit the spots that I receive (or at least the
> ones that get into my database) to a more local region than the entire
> world. I am thinking of setting up with a spot accept filter limiting
> spots on my cluster to just CQ zone 4. I have made some attempts to
> set this up myself, but after connecting to WR3D I always seem to be
> getting everything, so I guess I am asking for a bit of help in how to
> get this setup. My long term goal is to remain as just an
> 'end-of-the-line' node connected to WR3D, and to be able to filter my
> DX spot database so that any users (all of which will be connected
> ONLY over a local 2m link), will only see regional spots for zone 4 if
> they do a 'sh/dx' command. I may also like to experiment with
> restricting my VHF and above data more aggressively than this,
> possibly on a call area or even state basis, but I am not too
> concerned about those nuances yet. In reading the online docs, it
> seems to be strongly implied that this functionality is there, but I
> can't seem to make it work. I have tried the following approaches,
> logged in as sysop callsign and entering the following:
> 
> accept/spots node_default by_zone 4 => This produces a node_deafult.pl
> filter in the ../filter/spots directory, but has no filtering effect
> on which spots from WR3D get into my list
> 
> accept/route wr3d call_zone 4 => this produces a wr3d.pl filter in the
> spots subdirectory, but does not accomplish my goal either.
> 
> accept/spots wr3d by_zone 4 => updates the WR3D filter file wr3d.pl,
> but still no joy. 
> 
> My gut feeling is that I am totally misunderstanding how these filters
> are intended to be used. Can anyone out there de-mystify this for me? 
> 
> Thanks,
> 
> Mike
> 'Local' DXSpider node KE0MF-15
> 
> 
> 
> ______________________________________________________________________
> 
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://www.tobit.co.uk/mailman/listinfo/dxspider-support
-- 
Please Note: Some Quantum Physics Theories Suggest That When the
Consumer Is Not Directly Observing This Product, It May Cease to
Exist or Will Exist Only in a Vague and Undetermined State.