[aprssig] APRS-IS vs. FireNet
Pete Loveall AE5PL Lists
hamlists at ametx.com
Wed Jun 25 07:04:33 CDT 2014
You are trying to use Firenet for an IGate and the Firenet servers specifically do not support IGates. This is due to the intent of the Firenet vs. APRS-IS. The APRS-IS primary purpose today is to interconnect amateur radio RF APRS networks. This means it is expected that -any- and -all- packets seen in the APRS-IS network may end up on RF somewhere in the world. Firenet, on the other hand, is an experimental subnet without that restriction and encourages experimentation with higher activity feeds than what APRS-IS is designed for. Because of this, APRS-IS servers support "recently heard" lists to support IGates running on filtered feeds; Firenet servers do not support "recently heard" lists so people do not connect IGates to their servers, only GUI clients, database collectors, or other non-RF application.
APRS-IS=RF support; Firenet=Internet-only clients. Firenet does fully support messaging to/from APRS-IS for the directly connected clients but not for clients beyond the directly connected client (gated by an IGate).
Hope this helps.
Pete Loveall AE5PL
pete at ae5pl dot net
> -----Original Message-----
> From: Max Harper
> Sent: Tuesday, June 24, 2014 9:07 PM
> Since switching to FireNet from the APRS-IS to get more NWS data I have
> noticed that I no longer receive any messages nor do I get any packets from
> once heard stations. I connect using APRX (no display) with a filter of
> "p/BMX/HUN". Is there a filter that is needed to get messages from Firenet
> that wasn't needed with the APRS-IS?
> Max KG4PID
More information about the aprssig