firenet.us issues (was: 2011/08/30 13.20)
- That probably had nothing to do with the upgrade, but everything to do with firenet.us. I'm assuming you are using firenet as your APRS-IS server? If not, let me know because the following does not apply.
Yesterday, firenet.us again had APRS-IS connectivity issues and was connected to the CWOP server as an upstream feed. When this happens, messaging from the APRS-IS core fails and many of the ham radio APRS stations fail to appear.
You can see this by visiting the firenet server status page at http://firenet.us:14501/ and scrolling down to the Outbound Connections section. If the Server to which it is connected says anything about CWOP, you'll be missing most of the APRS-IS stations and need to switch back to one of the tier 2 servers until firenet resolves itself, usually about 05:00 every morning Eastern time.
Another way you can tell is to double-click the APRS-IS OK pane and check the hourly traffic counts. When the packet rate changes dramatically, chances are firenet has changed feeds.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
PS. Here's what firenet.us says now and I suspect you're seeing the APRS-IS stations again:
Outbound Connections Server q Addr Verified Software Connected Packets
third.aprs.net/188.8.131.52:10152 92E5A2B6 Yes javAPRSSrvr 3.15b06 49m52.859s 105,089 2,479 9,376,814 229,224 25,071 612 00.024s 163 0
On 8/31/2011 12:50 AM, Adam Rozanski wrote:Lynn downloaded 2011/08/30 13.20 now all I get is the wx stations tryed the transmit trick but it will not work any help