<div dir="ltr">Hi Dirk,<br>Then it does what you have actually programmed.<br>Perhaps it would be convenient (for me) when using several sessions not to use callsign without ssid and remove all filters from callsign without ssid, nor enable rbn, and configure the filters in which they have ssid.<br><br><div>I appreciate your explanation, it has been very clear and evident.</div><div><br></div><div>73 de Kin</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El mié, 8 dic 2021 a las 18:42, Dirk Koopman via Dxspider-support (<<a href="mailto:dxspider-support@tobit.co.uk">dxspider-support@tobit.co.uk</a>>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div>
    <div>Pardon me for laying out some code
      here, but this is logic employed on startup for filtering...<br>
      <br>
      if $call eq 'G1TLH-2' then $nossid = 'G1TLH'<br>
      <br>
          $self->{spotsfilter} = Filter::read_in('spots', $call, 0) <br>
              || Filter::read_in('spots', $nossid, 0)<br>
                  || Filter::read_in('spots', 'user_default', 0);<br>
      <br>
      which means that if I login as -2, I would get a G1TLH-2 filter if
      (and only if) I have defined one. If I haven't defined a filter
      for -2, but G1TLH (nossid) has one, then I get that and, if none
      of these applies then I get the user_default - assuming there is
      one.<br>
      <br>
      NOTE: there is NO difference between the master and mojo branches
      in this logic. <br>
      <br>
      What show/filter does: is to show you the filter is defined
      (just/only) for the callsiign that you logged in with. Meaning
      that in this example it would show the filters for G1TLH-2. It
      does NOT show you the filters that you might be using. Just for
      completeness, filters do not build up from some base or one
      another (e.g user_default + nossid + call). You get just one
      filter for each class of thing (spot, announce, rbn etc). <br>
      <br>
      Now, you *could* say to me that this is confusing or even
      inadequate, but that is how it has worked for (about) the last 25
      years.<br>
      <br>
      Dirk G1TLH<br>
      <br>
      On 08/12/2021 10:38, Joaquin . via Dxspider-support wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">
        <div>
          <div><font size="2"><span lang="en"><span><span>Hi,</span></span></span></font></div>
          <div><font size="2"><span lang="en"><span><span>I am running
                    version 1.57 build 345 and I see that if I login as
                    EA3CV, configure filters and activate RBN, when I
                    login as EA3CV- * (any SSID) and do sh/filter, the
                    system tells me that I have no filter, but the
                    filters that I defined</span></span> <span><span>as EA3CV and
                    the RBN points apply to EA3CV- *</span></span><span><span> <br>
                  </span></span></span></font></div>
          <div><font size="2"><span lang="en"><span><span>The question
                    is if the EA3CV configuration is inherited for any
                    EA3CV with SSID.</span></span> <span><span>But if so, why
                    is it not seen when sh/filter is run?</span></span><br>
              </span></font></div>
          <div><font size="2"><span lang="en"><span><span><br>
                  </span></span></span></font></div>
          <div><font size="2"><span lang="en"><span><span>Wouldn't it be
                    more correct if there was no inheritance between the
                    callsign and its different SSIDs? <span lang="en"><span><span>Because
                          it causes misinterpretation and limits the
                          functionality of SSID usage.</span></span></span>
                  </span></span></span></font></div>
          <div><font size="2"><span lang="en"><span><span><br>
                  </span></span></span></font></div>
          <div><font size="2"><span lang="en"><span><span>The same is
                    true for build 366.</span></span></span></font> </div>
          <font size="2"><br>
          </font></div>
        <div><font size="2">73 de Kin</font></div>
        <div><font size="2">EA3CV-2</font></div>
        <div><font size="2">EA4URE-5</font><br>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
Dxspider-support mailing list
<a href="mailto:Dxspider-support@tobit.co.uk" target="_blank">Dxspider-support@tobit.co.uk</a>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" target="_blank">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
    </blockquote>
    <br>
  </div>

_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@tobit.co.uk" target="_blank">Dxspider-support@tobit.co.uk</a><br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer" target="_blank">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</blockquote></div>