[aprssig] Is Firenet Having Problems?
curt.we7u at gmail.com
Thu Nov 29 15:11:23 CST 2012
On Thu, 29 Nov 2012, Stephen H. Smith wrote:
> I am simply NOT seeing any NWS stuff in my incoming feed with the filter expression below.
> Has there been a recent change/update in the JavAPRS filter parser? I am sending the string
> filter b/WA8LMF/WA8LMF-2/WA8LMF-63 t/n s/: s//l -e/WXSVR-AU -q//i o/ISS*
> to the port 14580 of firenet, but I see this on the firenet:14501 status page for WA8LMF-13:
> filter b/WA8LMF-63/WA8LMF/WA8LMF-2 t/n s/:// s//l/ os/ISS* -e/WXSVR-AU -q/
> Why is the server rearranging the sequence of my budlist callsigns?
> What is the significance of the restructuring of the "s" option arguments?
> What is the significance of "o/ISS*" being replaced with "os/ISS*"
There was a change to the object filter and it broke earlier filters. That was changed later so that the "os" filter did it the new way, and the "o" filter retained the earlier functionality, so at that point (maybe a month back?) the "o" filter started working again for everyone.
I don't know of there were additional changes or why it rearranges things, but I've seen that as well. I suspect the "o" filter may just reformat and pass it on to the "os" filter, but I can't say for sure.
Your best bet would be to ask Pete. He may send you to the guy who wrote the filter code, or perhaps the filter code is now inside javAPRSSrvr... Don't recall.
Curt, WE7U. http://wetnet.net/~we7u
APRS Device Capabilities: http://wetnet.net/~we7u/aprs_device_capabilities.html
More information about the aprssig