<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt"><div><span>That answers most of my questions. But I had never read anything like that before and I have searched for info many times. I've been igateing packets through FireNet for months now and the only things that don't work is messages and the recently heard list just like you said, but igateing INTO FireNet works fine. So if I connect to ......</span></div><div style="color: rgb(0, 0, 0); font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13.33px; font-style: normal; background-color: transparent;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13.33px; font-style: normal; background-color: transparent;"><span>A. APRS-IS I
get full igate support but can't get the extra NWS watches and advisories..</span></div><div style="color: rgb(0, 0, 0); font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13.33px; font-style: normal; background-color: transparent;"><span>B. FireNet I can get the NWS watches, warnings and advisories (and other stuff if I want it) but limited igate support.</span></div><div><br></div><div>So there is no way to have an igate with full messaging capability AND transmit NWS watches, warnings and advisories, Is that correct. Why don't we have an option C anymore? Most clients can only connect to one server. Who was it that used to inject all the NWS data into the APRS-IS? It's been a few years ago. I liked that much better.</div><div><br></div><div>Max KG4PID</div><div><br></div> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size:
10pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <div style="margin: 5px 0px; padding: 0px; border: 1px solid rgb(204, 204, 204); border-image: none; height: 0px; line-height: 0; font-size: 0px;" contenteditable="false" readonly="true"></div> <font face="Arial" size="2"> <b><span style="font-weight: bold;">From:</span></b> Pete Loveall AE5PL Lists <hamlists@ametx.com><br> <b><span style="font-weight: bold;">To:</span></b> TAPR APRS Mailing List <aprssig@tapr.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Wednesday, June 25, 2014 7:04 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [aprssig] APRS-IS vs. FireNet<br> </font> </div> <div><br>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.<br clear="none"><br clear="none">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).<br clear="none"><br
clear="none">Hope this helps.<br clear="none"><br clear="none">73,<br clear="none"><br clear="none">Pete Loveall AE5PL<br clear="none">pete at ae5pl dot net<br clear="none"><br clear="none"><br clear="none"><div id="yqtfd28118"><br clear="none">> -----Original Message-----<br clear="none">> From: Max Harper<br clear="none">> Sent: Tuesday, June 24, 2014 9:07 PM<br clear="none">> <br clear="none">> Since switching to FireNet from the APRS-IS to get more NWS data I have<br clear="none">> noticed that I no longer receive any messages nor do I get any packets from<br clear="none">> once heard stations. I connect using APRX (no display) with a filter of<br clear="none">> "p/BMX/HUN". Is there a filter that is needed to get messages from Firenet<br clear="none">> that wasn't needed with the APRS-IS?<br clear="none">> <br clear="none">> Max KG4PID</div><br clear="none"><br
clear="none">_______________________________________________<br clear="none">aprssig mailing list<br clear="none"><a href="mailto:aprssig@tapr.org" shape="rect" ymailto="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br clear="none"><a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank" shape="rect">http://www.tapr.org/mailman/listinfo/aprssig</a><div id="yqtfd26679"><br clear="none"></div><br><br></div> </div> </div> </div></body></html>