[aprssig] APRS-IS vs. FireNet

[Pete Loveall AE5PL Lists]

This has been hashed and rehashed.  And, contrary to your statement, there are many places including here where it has been said that FireNet servers do not support IGates on filtered feeds.

The weather server you are thinking of has been offline for years.  You are incorrect in your statement that you cannot transmit NWS warnings.  They are on APRS-IS but only immediate warnings as determined by the NWS because to do otherwise would make the local RF frequency unusable during heightened weather activity in an area.  Again, FireNet is great for Internet-connected clients where you have high bandwidth; APRS-IS is for RF networks.  Don't try to mix the 2 as you will cause more problems than help.  That is why conscientious authors limit your connection capabilities to a single server at a time.  Otherwise, you introduce loops, excess data load, etc. into APRS-IS.

73,

Pete Loveall AE5PL
pete at ae5pl dot net



> -----Original Message-----
> From: Max Harper
> Sent: Wednesday, June 25, 2014 10:39 AM
> 
> 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 ......
> 
> 
> A. APRS-IS I get full igate support but can't get the extra NWS watches and
> advisories..
> B. FireNet I can get the NWS watches, warnings and advisories (and other
> stuff if I want it) but limited igate support.
> 
> 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.