TX-iGate Filters?
ab0tj
iGate. From my understanding of http://wiki.ham.fi/Aprx.en , I should
run with no "filter" statement in the <aprsis> section of my config,
and let aprx digipeat from APRSIS to RF because it will follow these
rules here http://www.aprs-is.net/IGateDetails.aspx
But, from watching the aprx-rf.log file, it seems that everything
coming in from APRSIS is being transmitted out the RF port.
How should I have this configured? I want my TX-iGate to follow the
rules outlined in the link above.
Thanks,
Alex/AB0TJ
LeeDB
On Jun 23, 3:44 pm, ab0tj <al91...@gmail.com> wrote:
> I want to set up my iGate running aprx-2.00 to act as a transmit
> and let aprx digipeat from APRSIS to RF because it will follow these
> But, from watching the aprx-rf.log file, it seems that everything
> coming in from APRSIS is being transmitted out the RF port.
>
> How should I have this configured? I want my TX-iGate to follow the
> rules outlined in the link above.
following the rules above for Tx, but it seemed to be transmitting
everything. I switched to running APRSIS32 under wine, and it appears
to be working fine, but I would rather use a smaller application like
aprx.
Regards,
Lee - K5DAT
OZ1EKD
I believe you can filter what to output on RF from APRSIS in the
digipeater section:
Here is my setup for my TX-Igate which only does what I want, on top of
that I have set a range filter in <aprsis> of some 20 Km to avoid info
from outside my tx range.
<aprsis>
server rotate.aprs.net 14580
filter m/20 # My-Range filter:
positions within 20 km from my location
<aprsis>
<source> # Adding APRSIS source
makes this tx-igate
source APRSIS
relay-type third-party # Must define this for
APRSIS source!
viscous-delay 5 # Recommendation: 5
seconds delay to give
# RF
delivery time make itself known.
#filter a/58/8/54/16 # example of geografic
range (disabled)
filter t/mos # messages
objects status
</source>
73 de OZ1EKD
ab0tj
I am running aprx on a Linksys WRT54G router, so unfortunately
APRSIS32 is not an option. It is a great program, though. And as for
the filters, I was hoping for aprx to be able to act intelligently
instead of just using static filters. The closest I've been able to
come up with to what's described on the aprs-is website is to no
assign any filter in the <aprsis> section and filter to just messages
in the <source> section. That bypasses a lot of the checks that the
aprs-is website describes, but the aprsis server will only send
packets pertaining to stations I have gated. That can become a lot of
packets pretty quick, so thats why I filter it down to only messages.
To the author of Aprx: I love the software, but is this planned
functionality to make the TX-igate behave as described in
http://www.google.com/url?sa=D&q=http://www.aprs-is.net/IGateDetails.aspx
?
Thanks again,
Alex
Ed
I just filter distance, and make it a really small area. My station is RX-Only though.
Ed
KI6PSP
Sent from my iPad
> --
> To unsubscribe from this group, send email to aprx-softwar...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/aprx-software
LeeDB
On Jul 5, 5:44 pm, Ed <ki6...@gmail.com> wrote:
> In my experience, you can't have more than 1 filter in this 2.00 version, unless that has been fixed. I used to be able to do it in the .99 version.
>
> I just filter distance, and make it a really small area. My station is RX-Only though.
>
> Ed
> KI6PSP
>
> Sent from my iPad
>
>
> > Thanks Lee and OZ1EKD from the replies.
side when I first tried out APRX as a Rx IGate that I thought I had
commented out. Once I eliminated the filter, the Tx IGate has
appeared to be fine. I don't think it has transmitted anything on RF
yet other than it's own beacon, but that's to be expected - messages I
expect to be few and far between plus I have a service area filter in
place.
Lee - K5DAT
LeeDB
> Hi,
>
> I believe you can filter what to output on RF from APRSIS in the
> digipeater section:
> Here is my setup for my TX-Igate which only does what I want, on top of
> that I have set a range filter in <aprsis> of some 20 Km to avoid info
> from outside my tx range.
>
> <aprsis>
> server rotate.aprs.net 14580
> filter m/20 # My-Range filter:
IGate. I have no filter there.
> positions within 20 km from my location
> <aprsis>
>
> <source> # Adding APRSIS source
> makes this tx-igate
> source APRSIS
> relay-type third-party # Must define this for
> APRSIS source!
> viscous-delay 5 # Recommendation: 5 seconds delay to give # RF delivery time make itself known.
> #filter a/58/8/54/16 # example of geografic range (disabled)
> filter t/mos # messages
the APRS-IS
area and limits IS to RF traffic to messages. I agree that the person
on v2.0
that is not seeing the expected behavior could try this. I am on
2.01, and with
no filter in the APRS-IS area, I am seeing the expected behavior.
Regards,
Lee - K5DAT
Matti Aarnio
>
> In my experience, you can't have more than 1 filter in this 2.00 version,
> unless that has been fixed. I used to be able to do it in the .99 version.
>
> I just filter distance, and make it a really small area.
> My station is RX-Only though.
Sure I can define multiple filters:
(At least since Summer 2010, and APRX1L, probably a lot longer)
<digipeater>
transmit NULL
ratelimit 300000 3000000
<source>
source $mycall
relay-type digipeat
filter t/m
filter a/60.0/24.5/60.5/25.5
</source>
<source>
source APRSIS
ratelimit 300000 3000000
relay-type third-party
filter t/m
filter a/60.0/24.5/60.5/25.5
</source>
</digipeater>
> Ed
> KI6PSP
I just checked that 2.03test2 is able to handle it.
Related source had its last modification at Summer 2010.
Running aprx with options: -dddvv -f aprx.conf will
let you to check at the configuration parse in great detail.
73 de Matti, OH2MQK