Re: [Xastir] Filters
On 20/10/2012 4:27 p.m., xastir-requ...@lists.xastir.org wrote: Send Xastir mailing list submissions to xastir@lists.xastir.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir or, via email, send a message with subject or body 'help' to xastir-requ...@lists.xastir.org You can reach the person managing the list at xastir-ow...@lists.xastir.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Xastir digest..." Today's Topics: 1. javAPRSSrvr Filter Strings (Curt, WE7U) ... Aha! So that's the most likely cause. Stoked up this morning and got the whole world streaming in. I have 2 servers defined: first.aprs.net.nz, and second.aprs.net.nz, both port 14578 which should be a nz-only feed requiring no filter. At one point I quieted it by downing one or other, then it settled with both up - must have learned something, or the admins did :) Meanwhile, an interesting effect. Seeing the whole world was coming in anyway I zoomed out to take a peek. Major gap India/Sri Lanka, but some either side and North. Any reason? 73 de ZL2DEX ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] javAPRSSrvr Filter Strings
So if I have " t/n e/WE7U-WX " in a interface is it still going to work? On 10/19/2012 03:32 PM, Curt, WE7U wrote: > > Anyone messing with one of the (three) Firenet servers to get their > connection: We've converted to javAPRSSrvr 4.x, which does filtering > differently. A difference I just ran across: > > I just got caught by a change in how javAPRSSrvr interprets the filter > string. > > I was using this filter in Xastir, connected to Firenet-3 and not > seeing the "STEAM" object come through: > > m/800 o/STEAM/UP844 t/n e/WE7U-WX > > I had to change to this: > >m/800 o/STEAM/UP844 t/n e/WE7U-WX > > Notice the extra spaces after "STEAM" and "UP844" to make a > 9-character object name. I think for other S/W you have to prefix the > string with "filter " but Xastir adds it for you behind the scenes. > > Now I'm seeing the steam train happily steaming along heading towards > Shreveport, LA, with a Firenet connection to Xastir! Unfortunately > the "t/n e/WE7U-WX" filters don't work. > > Even more fun: Pete says the Object filter must be last on the filter > line. Try that in Xastir and it will trim off the trailing spaces. > > "m/800 t/n e/WE7U-WX o/STEAM/UP844" > > becomes: > > "m/800 t/n e/WE7U-WX o/STEAM/UP844" > > Which means the "UP844" part of the filter above won't work. I'm > waiting for "STEAM" to start moving again to see if that part works. > > Yep. That part worked. Then reversed the two like this to test STEAM > as the last element: > > "m/800 t/n e/WE7U-WX o/UP844/STEAM" > > Xastir chopped off the last four chars and STEAM stopped working. > Then went to this and got everything working again: > > "m/800 t/n e/WE7U-WX o/UP844/STEAM/" > > So... If using Xastir and filtering against a javAPRSSrvr4.x server > (Firenet-1/2/3), you'll have to move the Object portion to the end, > put in a trailing slash, and count spaces. There should be nine chars > total in an Object name. > > Having to count spaces is ridiculous. It requires the user to have > some familiarity with the APRS spec and/or to read the filter docs > VERY carefully. Existing filter strings that have worked for years > may be broken now and there's no indication of this to the user. I'm > talking to Pete to see if this can't be resolved in a better manner > than having every user change their filter strings. > > At least now you're informed. > -- David A Aitcheson david.aitche...@gmail.com Go Green! Print this email only when necessary. ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] javAPRSSrvr Filter Strings
If you can pass it along, firenet.us port 10152 isn't accepting inbound connections. Also, I placed my vote for reverting the o/ filter to the old behavior as proposed by Pete in the javaprssrvr group. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 10/19/2012 6:05 PM, Curt, WE7U wrote: On Fri, 19 Oct 2012, Lynn W. Deffenbaugh (Mr) wrote: Personally, I just recommend that any use of the o/ filter user the *. It may mean that additional objects are received, but the following should work for you. o/STEAM*/UP844* And where did you find documented that the o/ filter term needs to be last? I completely missed that one but it might explain some wierdness that I've seen. I believe it's a javAPRSSrvr 4.x new feature. Heard it direct from Pete today. Gerry, Pete, and I have been working on getting Firenet 1/2/3 set up properly with version 4.x. I'll switch to your syntax 'cuz I like it better. ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] javAPRSSrvr Filter Strings
On Fri, 19 Oct 2012, Lynn W. Deffenbaugh (Mr) wrote: Personally, I just recommend that any use of the o/ filter user the *. It may mean that additional objects are received, but the following should work for you. o/STEAM*/UP844* And where did you find documented that the o/ filter term needs to be last? I completely missed that one but it might explain some wierdness that I've seen. I believe it's a javAPRSSrvr 4.x new feature. Heard it direct from Pete today. Gerry, Pete, and I have been working on getting Firenet 1/2/3 set up properly with version 4.x. I'll switch to your syntax 'cuz I like it better. -- Curt, WE7U.http://wetnet.net/~we7u U.S. Weather Alerts: Firenet.us, port 14580, filter "t/n e/WE7U-WX" ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] javAPRSSrvr Filter Strings
On Fri, Oct 19, 2012 at 12:32:18PM -0700, we recorded a bogon-computron collision of the flavor, containing: [...counting spaces in javAPRSSrvr 4.x filters on object names...] > "m/800 t/n e/WE7U-WX o/UP844/STEAM/" > > So... If using Xastir and filtering against a javAPRSSrvr4.x server > (Firenet-1/2/3), you'll have to move the Object portion to the end, put in a > trailing slash, and count spaces. There should be nine chars total in an > Object name. > > Having to count spaces is ridiculous. It requires the user to have some > familiarity with the APRS spec and/or to read the filter docs VERY carefully. > Existing filter strings that have worked for years may be broken now and > there's no indication of this to the user. I'm talking to Pete to see if > this can't be resolved in a better manner than having every user change their > filter strings. Ick. That really is a change for the worse. Hope Pete changes it. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236http://kevan.org/brain.cgi?DDTNM "And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit!" --- The Tick ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] javAPRSSrvr Filter Strings
Personally, I just recommend that any use of the o/ filter user the *. It may mean that additional objects are received, but the following should work for you. o/STEAM*/UP844* And where did you find documented that the o/ filter term needs to be last? I completely missed that one but it might explain some wierdness that I've seen. Lynn (D) - KJ4ERJ -Author of APRSISCE for Windows Mobile and Win32 PS. Any specification that uses blanks as delimiters between terms AND as part of the terms is just plain busted IMHO. On 10/19/2012 3:32 PM, Curt, WE7U wrote: Anyone messing with one of the (three) Firenet servers to get their connection: We've converted to javAPRSSrvr 4.x, which does filtering differently. A difference I just ran across: I just got caught by a change in how javAPRSSrvr interprets the filter string. I was using this filter in Xastir, connected to Firenet-3 and not seeing the "STEAM" object come through: m/800 o/STEAM/UP844 t/n e/WE7U-WX I had to change to this: m/800 o/STEAM/UP844 t/n e/WE7U-WX Notice the extra spaces after "STEAM" and "UP844" to make a 9-character object name. I think for other S/W you have to prefix the string with "filter " but Xastir adds it for you behind the scenes. Now I'm seeing the steam train happily steaming along heading towards Shreveport, LA, with a Firenet connection to Xastir! Unfortunately the "t/n e/WE7U-WX" filters don't work. Even more fun: Pete says the Object filter must be last on the filter line. Try that in Xastir and it will trim off the trailing spaces. "m/800 t/n e/WE7U-WX o/STEAM/UP844" becomes: "m/800 t/n e/WE7U-WX o/STEAM/UP844" Which means the "UP844" part of the filter above won't work. I'm waiting for "STEAM" to start moving again to see if that part works. Yep. That part worked. Then reversed the two like this to test STEAM as the last element: "m/800 t/n e/WE7U-WX o/UP844/STEAM" Xastir chopped off the last four chars and STEAM stopped working. Then went to this and got everything working again: "m/800 t/n e/WE7U-WX o/UP844/STEAM/" So... If using Xastir and filtering against a javAPRSSrvr4.x server (Firenet-1/2/3), you'll have to move the Object portion to the end, put in a trailing slash, and count spaces. There should be nine chars total in an Object name. Having to count spaces is ridiculous. It requires the user to have some familiarity with the APRS spec and/or to read the filter docs VERY carefully. Existing filter strings that have worked for years may be broken now and there's no indication of this to the user. I'm talking to Pete to see if this can't be resolved in a better manner than having every user change their filter strings. At least now you're informed. ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] javAPRSSrvr Filter Strings
On Fri, 19 Oct 2012, Curt, WE7U wrote: "m/800 t/n e/WE7U-WX o/UP844/STEAM/" BTW: Anyone in/near Shreveport, LA: There's a steam train headed your way. -- Curt, WE7U.http://wetnet.net/~we7u Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
[Xastir] javAPRSSrvr Filter Strings
Anyone messing with one of the (three) Firenet servers to get their connection: We've converted to javAPRSSrvr 4.x, which does filtering differently. A difference I just ran across: I just got caught by a change in how javAPRSSrvr interprets the filter string. I was using this filter in Xastir, connected to Firenet-3 and not seeing the "STEAM" object come through: m/800 o/STEAM/UP844 t/n e/WE7U-WX I had to change to this: m/800 o/STEAM/UP844 t/n e/WE7U-WX Notice the extra spaces after "STEAM" and "UP844" to make a 9-character object name. I think for other S/W you have to prefix the string with "filter " but Xastir adds it for you behind the scenes. Now I'm seeing the steam train happily steaming along heading towards Shreveport, LA, with a Firenet connection to Xastir! Unfortunately the "t/n e/WE7U-WX" filters don't work. Even more fun: Pete says the Object filter must be last on the filter line. Try that in Xastir and it will trim off the trailing spaces. "m/800 t/n e/WE7U-WX o/STEAM/UP844" becomes: "m/800 t/n e/WE7U-WX o/STEAM/UP844" Which means the "UP844" part of the filter above won't work. I'm waiting for "STEAM" to start moving again to see if that part works. Yep. That part worked. Then reversed the two like this to test STEAM as the last element: "m/800 t/n e/WE7U-WX o/UP844/STEAM" Xastir chopped off the last four chars and STEAM stopped working. Then went to this and got everything working again: "m/800 t/n e/WE7U-WX o/UP844/STEAM/" So... If using Xastir and filtering against a javAPRSSrvr4.x server (Firenet-1/2/3), you'll have to move the Object portion to the end, put in a trailing slash, and count spaces. There should be nine chars total in an Object name. Having to count spaces is ridiculous. It requires the user to have some familiarity with the APRS spec and/or to read the filter docs VERY carefully. Existing filter strings that have worked for years may be broken now and there's no indication of this to the user. I'm talking to Pete to see if this can't be resolved in a better manner than having every user change their filter strings. At least now you're informed. -- Curt, WE7U.http://wetnet.net/~we7u U.S. Weather Alerts: Firenet.us, port 14580, filter "t/n e/WE7U-WX" ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
