Re: Filters. IS/RF RF/IS on various ports.
toggle quoted messageShow quoted text
The XML with a date extension is from the last upgrade. You should also have an EXE file with a date extension (the same date extensions). This is for the case where something doesn't work, you can quickly go back to the previous working version by deleting the newer, and removing the date extension.
I believe you are correct, you cannot filter RF received. Anything received on RF is handled (DIGI, etc.). However, you can use the to ignore or limit hops by changing the response to WIDEn-N requests as shown on the wiki: http://aprsisce.wikidot.com/doc:digipeating
I think the general philosophy is that if it came in on RF it is safe to send on RF. On the other hand, what you get from the internet, you need to ensure it meets amateur radio regulations.
Are you trying to filter RF data as in prevent your station from DIGI'ing a request just because of a callsign?
Most TOCALLs are ALTNETs or just an indication of the APRS app in use. Why would you block certain ones from being DIGI'ed?
From: "iulianp@... [aprsisce]"
Sent: Monday, June 25, 2018 4:08 PM
Subject: Re: [aprsisce] Filters. IS/RF RF/IS on various ports.
I had a bit of a 'revelation' this morning. I came across a couple of similar unanswered questions somewhere else on the net. I believe the filters only apply to the RF IS / IS RF traffic and they do not interfere at all with the RF digipeater function in the APRSIS32 program. In other words, if I used APRSIS32 as a WIDEn-N RF digipeater and wanted to block a certain TOCALL, for example, the filter -u/TOCALL won't have any effect on the digipeated packet. That TOCALL won't go though the RF IS though in my APRSIS32. I am yet to do some experiments on this.
RF IS IS RF vs APRS-IS disabled/enabled.
I also need to experiment with the RF IS tick boxes on the RF port and APRS-IS port (enabled and disabled). See the outcome.
Truly, I haven't seen many xml files in the programs folder! There is one more in my case. It has a date extension added to it. Probably another backup.
"Lynn's implementation of filters"
I have seen something in the manual, pg 38.
Any comments and suggestions on the above from pax who have already mastered APRSIS32, more than welcome.
73, J, YO3FCA M0IPU