[Dxspider-support] rejecting digital modes on whole DXspider node (not client)

[Dirk Koopman]

The answer is to use input filters from any feeds that supply this new 
node. BUT you have to accept that some of these may get through 
regardless and also will miss SSB+CW spots that may be running out of 
band plan. Remember also that you can filter on the 'info' or comment 
field in spots but you need to brush up on your perl 'regex' skills  
filter out stuff you don't want (that are also working out of band plan).

This is a simplified and rather glib answer to what could turn out to be 
quite complicated to get exactly what you want. But if you already have 
client side filters that work "well enough" for you then you can simply 
use the same filters as "input" filters on your new node's cluster feed(s).

73 Dirk G1TLH

On 13/04/2019 10:40, dd5xx--- via Dxspider-support wrote:
> Hello all,
>   
> I am aware about the filtering possibilities on client side and I use them successfully. But my goal is: I want to create a secondary instance of DXspider running on my server (running on another dedicated port) which shows *ONLY* ssb and cw spots. It should reject all digital modes like ft8, rtty, jt, psk, etc. How can I configure my DXspider node to reject such incoming spots? I want my users connect to this dedicated DXspider node and receive only SSB+CW spots without the need to configure any local logbook software filtering or sending any DXcluster specific commands.
>   
> Any help appreciated. Thank you
> Saki, DD5XX
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support