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
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
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
On Fri, Oct 19, 2012 at 12:32:18PM -0700, we recorded a bogon-computron
collision of the curt.w...@gmail.com 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
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
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
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
