Loading ...
Sorry, an error occurred while loading the content.

RE: [aprsisce] Need to block invalid format digi site?

Expand Messages
  • Fred Hillhouse
    It looks like the site is not digipeating anything along with sending a valid position. The last valid position was 55 days ago. In which case, blacklisting
    Message 1 of 20 , Jun 12, 2013
    • 0 Attachment
      It looks like the site is not digipeating anything along with sending a valid position. The last valid position was 55 days ago. In which case, blacklisting won't solve the problem. And the local network still has a hole. At least that is what it looks like from clear across the country.
       
      You have a definite challenge ahead.
       
      How does one convince another to change anything?
       
      How would I or anyone else convince you to change your equipment or operation mode just because I said it was wrong?
       
      I sometimes try to meet over something brewed, coffee is a good starter. Do the eyeball. Be friendly. Maybe then he may be interested in seeing your data. And then maybe he will start to trust, if that is the issue. Once you are over the initial hurdles, plan to drive to the site with him. If his health is not so good then someone else doing the driving may be a big help. Even donating hardware can help. Free stuff gets many people's attention. Spend sometime learning about his particular hardware. Most seem to never really learn more than what it takes to get it on the air. Your knowledge and his hardware can be a blessing and maybe the beginning of a new radio partnership. Since you already help on that hill, this should be a breeze!
       
      On another issue, I noticed on the topo maps that the site is a big communication site. That usually presents another set of problems. The site owner/coordinator may be very particular about who is on site and when and they may have to be there as well. This may not be the case if his digipeater is in the same room. Personally, I have some equipment on a similar hill and I only have access to a very small box/room and I cannot take a guest, ever, unless the box/room owner is present.
       
      There may be other issues as well, but the first step is to start a friendly face to face dialog. Going "third party" never works in my experience. And blacklisting will only make it all the more challenging and potentially unfixable.
       
      The best of luck and times to you!
       
      Best regards,
      Fred N7FMH
       
       
       


      From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Jerry Wyatt, n7qvu
      Sent: Wednesday, June 12, 2013 12:26
      To: aprsisce@yahoogroups.com
      Subject: Re: [aprsisce] Need to block invalid format digi site?

       

      Like I said, I thought this "filter issue" had been kicked around before.
       
      The bigger problem is to get this wide area digi fixed(MFJ1274) or get it off the network!
       
      I've been in contact with him via a 3rd party, but discussion for over a month hasn't helped. I support other repeaters on that mountain, but he seems distrustful of any ham offer for help.
       
      Arizona really needs this site to be operational for the network.
       
      73s
      Jerry - N7QVU
       
      From: Fred Hillhouse <fmhillhouse@...>
      To: aprsisce@yahoogroups.com
      Sent: Wednesday, June 12, 2013 9:16 AM
      Subject: RE: [aprsisce] Need to block invalid format digi site?
       
      Are you asking if you can keep a received packets from I-Gating?
      And, the reason you want to do this is because the digipeater is not sending its own beacon properly?
       
      Basically, I-Gates passes every thing upstream to the APRS-IS. There is no filter to block this action.
       
      Best regards,
      Fred N7FMH
       
       
      From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Jerry Wyatt, n7qvu
      Sent: Wednesday, June 12, 2013 11:48
      To: APRSIS
      Subject: [aprsisce] Need to block invalid format digi site?
       
      I think this question has come up before:
       
      Is there any way I can block my iGates from this 10,500' mountain site digi(GRNSAZ)?
       
      Several folks have tried to assist this ham with his digi, but he is not willing and his health doesn't allow him to travel to the mountain site. He doesn't reply to most calls or e-mails! Also because the posits are invalid, he doesn't show on most maps and therefore most folks think the site is down...
       
      73s
      Jerry Wyatt - N7QVU-11
      Overgaard, AZ
       
      ******
       
      His QRZ.com info:

      DONALD W LETCHER, W7OTA PO BOX 1556 SHOW LOW, AZ 85901
       
      APRS.fi raw data logs:
       
      2013-06-12 03:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 04:18:08 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 04:33:43 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 04:58:08 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 05:03:40 PDT: GRNSAZ>APNU19,WIDE2-2,qAR,N7QVU-11:!3406.70NS1893<:45G#QHG47#8.W4,AZn/W<0xb7>OTA-14 UIDIGI GzedN3 PeAk,AZ  [Invalid uncompressed location]2013-06-12 05:29:20 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 05:38:10 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 05:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 06:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 06:53:47 PDT: GRNSAZ>APNU19,WIDE2-2,qAR,N7QVU-11:!3406.70NS1893<:45G#QHG47#8.W4,AZn/W<0xb7>OTA-14 UIDIGI GzedN3 PeAk,AZ  [Invalid uncompressed location]2013-06-12 06:58:13 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 07:20:34 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 07:38:14 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 07:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 08:16:11 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 08:18:16 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]

    • Lynn W Deffenbaugh (Mr)
      I am definitely NOT condoning the following behavior but my chaotic tendencies have been over-active recently... If you really want to help out the local APRS
      Message 2 of 20 , Jun 12, 2013
      • 0 Attachment
        I am definitely NOT condoning the following behavior but my chaotic tendencies have been over-active recently...

        If you really want to help out the local APRS situation, at least by "hiding" this particular problem, why not locate his particular coax, cut it, and splice in a dummy load (so as not to blow his transmitter).  That'd serve 3 purposes:  1) keep his packets out of your IGate, 2) keep his packets out of the APRS-IS, and 3) keep his packets off the local RF freeing that precious shared resource (unless, of course, you're APRS receiver is located within a few feet of the dummy load!).

        The OO suggestion is probably the safest approach unless you can befriend one of his/her close friends and use that to bridge the third-party gap.

        Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

        On 6/12/2013 1:01 PM, Fred Hillhouse wrote:
        It looks like the site is not digipeating anything along with sending a valid position. The last valid position was 55 days ago. In which case, blacklisting won't solve the problem. And the local network still has a hole. At least that is what it looks like from clear across the country.
         
        You have a definite challenge ahead.
         
        How does one convince another to change anything?
         
        How would I or anyone else convince you to change your equipment or operation mode just because I said it was wrong?
         
        I sometimes try to meet over something brewed, coffee is a good starter. Do the eyeball. Be friendly. Maybe then he may be interested in seeing your data. And then maybe he will start to trust, if that is the issue. Once you are over the initial hurdles, plan to drive to the site with him. If his health is not so good then someone else doing the driving may be a big help. Even donating hardware can help. Free stuff gets many people's attention. Spend sometime learning about his particular hardware. Most seem to never really learn more than what it takes to get it on the air. Your knowledge and his hardware can be a blessing and maybe the beginning of a new radio partnership. Since you already help on that hill, this should be a breeze!
         
        On another issue, I noticed on the topo maps that the site is a big communication site. That usually presents another set of problems. The site owner/coordinator may be very particular about who is on site and when and they may have to be there as well. This may not be the case if his digipeater is in the same room. Personally, I have some equipment on a similar hill and I only have access to a very small box/room and I cannot take a guest, ever, unless the box/room owner is present.
         
        There may be other issues as well, but the first step is to start a friendly face to face dialog. Going "third party" never works in my experience. And blacklisting will only make it all the more challenging and potentially unfixable.
         
        The best of luck and times to you!
         
        Best regards,
        Fred N7FMH
         
         
         


        From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Jerry Wyatt, n7qvu
        Sent: Wednesday, June 12, 2013 12:26
        To: aprsisce@yahoogroups.com
        Subject: Re: [aprsisce] Need to block invalid format digi site?

         

        Like I said, I thought this "filter issue" had been kicked around before.
         
        The bigger problem is to get this wide area digi fixed(MFJ1274) or get it off the network!
         
        I've been in contact with him via a 3rd party, but discussion for over a month hasn't helped. I support other repeaters on that mountain, but he seems distrustful of any ham offer for help.
         
        Arizona really needs this site to be operational for the network.
         
        73s
        Jerry - N7QVU
         
        From: Fred Hillhouse <fmhillhouse@...>
        To: aprsisce@yahoogroups.com
        Sent: Wednesday, June 12, 2013 9:16 AM
        Subject: RE: [aprsisce] Need to block invalid format digi site?
         
        Are you asking if you can keep a received packets from I-Gating?
        And, the reason you want to do this is because the digipeater is not sending its own beacon properly?
         
        Basically, I-Gates passes every thing upstream to the APRS-IS. There is no filter to block this action.
         
        Best regards,
        Fred N7FMH
         
         
        From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Jerry Wyatt, n7qvu
        Sent: Wednesday, June 12, 2013 11:48
        To: APRSIS
        Subject: [aprsisce] Need to block invalid format digi site?
         
        I think this question has come up before:
         
        Is there any way I can block my iGates from this 10,500' mountain site digi(GRNSAZ)?
         
        Several folks have tried to assist this ham with his digi, but he is not willing and his health doesn't allow him to travel to the mountain site. He doesn't reply to most calls or e-mails! Also because the posits are invalid, he doesn't show on most maps and therefore most folks think the site is down...
         
        73s
        Jerry Wyatt - N7QVU-11
        Overgaard, AZ
         
        ******
         
        His QRZ.com info:

        DONALD W LETCHER, W7OTA PO BOX 1556 SHOW LOW, AZ 85901
         
        APRS.fi raw data logs:
         
        2013-06-12 03:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 04:18:08 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 04:33:43 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 04:58:08 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 05:03:40 PDT: GRNSAZ>APNU19,WIDE2-2,qAR,N7QVU-11:!3406.70NS1893<:45G#QHG47#8.W4,AZn/W<0xb7>OTA-14 UIDIGI GzedN3 PeAk,AZ  [Invalid uncompressed location]2013-06-12 05:29:20 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 05:38:10 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 05:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 06:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 06:53:47 PDT: GRNSAZ>APNU19,WIDE2-2,qAR,N7QVU-11:!3406.70NS1893<:45G#QHG47#8.W4,AZn/W<0xb7>OTA-14 UIDIGI GzedN3 PeAk,AZ  [Invalid uncompressed location]2013-06-12 06:58:13 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 07:20:34 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 07:38:14 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 07:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 08:16:11 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 08:18:16 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]

      • Fred Hillhouse
        If it is like the site I am on, the digipeater is probably in another locked building altogether and behind a locked gate. Many of these sites have multiple
        Message 3 of 20 , Jun 12, 2013
        • 0 Attachment
          If it is like the site I am on, the digipeater is probably in another locked building altogether and behind a locked gate. Many of these sites have multiple areas and all behind their own gates. You might to cut a lot of coax before finding the offender. That probably would elevate one's status to terrorist.
           
          I still think a coffee or beer can provide a lot of grease.
           
          Best regards,
          Fred N7FMH
           
           


          From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Lynn W Deffenbaugh (Mr)
          Sent: Wednesday, June 12, 2013 13:10
          To: aprsisce@yahoogroups.com
          Subject: Re: [aprsisce] Need to block invalid format digi site?

           

          I am definitely NOT condoning the following behavior but my chaotic tendencies have been over-active recently...

          If you really want to help out the local APRS situation, at least by "hiding" this particular problem, why not locate his particular coax, cut it, and splice in a dummy load (so as not to blow his transmitter).  That'd serve 3 purposes:  1) keep his packets out of your IGate, 2) keep his packets out of the APRS-IS, and 3) keep his packets off the local RF freeing that precious shared resource (unless, of course, you're APRS receiver is located within a few feet of the dummy load!).

          The OO suggestion is probably the safest approach unless you can befriend one of his/her close friends and use that to bridge the third-party gap.

          Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

          On 6/12/2013 1:01 PM, Fred Hillhouse wrote:
          It looks like the site is not digipeating anything along with sending a valid position. The last valid position was 55 days ago. In which case, blacklisting won't solve the problem. And the local network still has a hole. At least that is what it looks like from clear across the country.
           
          You have a definite challenge ahead.
           
          How does one convince another to change anything?
           
          How would I or anyone else convince you to change your equipment or operation mode just because I said it was wrong?
           
          I sometimes try to meet over something brewed, coffee is a good starter. Do the eyeball. Be friendly. Maybe then he may be interested in seeing your data. And then maybe he will start to trust, if that is the issue. Once you are over the initial hurdles, plan to drive to the site with him. If his health is not so good then someone else doing the driving may be a big help. Even donating hardware can help. Free stuff gets many people's attention. Spend sometime learning about his particular hardware. Most seem to never really learn more than what it takes to get it on the air. Your knowledge and his hardware can be a blessing and maybe the beginning of a new radio partnership. Since you already help on that hill, this should be a breeze!
           
          On another issue, I noticed on the topo maps that the site is a big communication site. That usually presents another set of problems. The site owner/coordinator may be very particular about who is on site and when and they may have to be there as well. This may not be the case if his digipeater is in the same room. Personally, I have some equipment on a similar hill and I only have access to a very small box/room and I cannot take a guest, ever, unless the box/room owner is present.
           
          There may be other issues as well, but the first step is to start a friendly face to face dialog. Going "third party" never works in my experience. And blacklisting will only make it all the more challenging and potentially unfixable.
           
          The best of luck and times to you!
           
          Best regards,
          Fred N7FMH
           
           
           


          From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Jerry Wyatt, n7qvu
          Sent: Wednesday, June 12, 2013 12:26
          To: aprsisce@yahoogroups.com
          Subject: Re: [aprsisce] Need to block invalid format digi site?

           

          Like I said, I thought this "filter issue" had been kicked around before.
           
          The bigger problem is to get this wide area digi fixed(MFJ1274) or get it off the network!
           
          I've been in contact with him via a 3rd party, but discussion for over a month hasn't helped. I support other repeaters on that mountain, but he seems distrustful of any ham offer for help.
           
          Arizona really needs this site to be operational for the network.
           
          73s
          Jerry - N7QVU
           
          From: Fred Hillhouse <fmhillhouse@...>
          To: aprsisce@yahoogroups.com
          Sent: Wednesday, June 12, 2013 9:16 AM
          Subject: RE: [aprsisce] Need to block invalid format digi site?
           
          Are you asking if you can keep a received packets from I-Gating?
          And, the reason you want to do this is because the digipeater is not sending its own beacon properly?
           
          Basically, I-Gates passes every thing upstream to the APRS-IS. There is no filter to block this action.
           
          Best regards,
          Fred N7FMH
           
           
          From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Jerry Wyatt, n7qvu
          Sent: Wednesday, June 12, 2013 11:48
          To: APRSIS
          Subject: [aprsisce] Need to block invalid format digi site?
           
          I think this question has come up before:
           
          Is there any way I can block my iGates from this 10,500' mountain site digi(GRNSAZ)?
           
          Several folks have tried to assist this ham with his digi, but he is not willing and his health doesn't allow him to travel to the mountain site. He doesn't reply to most calls or e-mails! Also because the posits are invalid, he doesn't show on most maps and therefore most folks think the site is down...
           
          73s
          Jerry Wyatt - N7QVU-11
          Overgaard, AZ
           
          ******
           
          His QRZ.com info:

          DONALD W LETCHER, W7OTA PO BOX 1556 SHOW LOW, AZ 85901
           
          APRS.fi raw data logs:
           
          2013-06-12 03:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 04:18:08 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 04:33:43 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 04:58:08 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 05:03:40 PDT: GRNSAZ>APNU19,WIDE2-2,qAR,N7QVU-11:!3406.70NS1893<:45G#QHG47#8.W4,AZn/W<0xb7>OTA-14 UIDIGI GzedN3 PeAk,AZ  [Invalid uncompressed location]2013-06-12 05:29:20 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 05:38:10 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 05:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 06:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 06:53:47 PDT: GRNSAZ>APNU19,WIDE2-2,qAR,N7QVU-11:!3406.70NS1893<:45G#QHG47#8.W4,AZn/W<0xb7>OTA-14 UIDIGI GzedN3 PeAk,AZ  [Invalid uncompressed location]2013-06-12 06:58:13 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 07:20:34 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 07:38:14 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]2013-06-12 07:51:51 PDT: GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.92013-06-12 08:16:11 PDT: GRNSAZ>APNU19,qAR,N7QVU-11:!s406&31NS14914.45W#PHW4<0xb7>30%W4,AZn/W7OTA-14 UIDIGI Gz%en3 [Invalid packet]2013-06-12 08:18:16 PDT: GRNSAZ>APNU19,SIDE2-3,qAR,N7QVU-11:!342&.70NS<0x11>0934.45S#PHGt330/W4,AZn/W7ODA-14 UI@IGI Gzeans Pe<0xe1>k,AZ  [Invalid uncompressed location]

        • Lynn W Deffenbaugh (Mr)
          ... I added a b/GRNSAZ filter test to my APRSISCE/32 RF monitor instance and have only seen: 2013-06-12T16:51:52.114 IS[APRS-IS](Hit(b/GRNSAZ))
          Message 4 of 20 , Jun 12, 2013
          • 0 Attachment
            On 6/12/2013 1:26 PM, Fred Hillhouse wrote:
            Are you able to see any of the packets in question?
             
            The only thing I can see anything with is APRS.FI.


            I added a b/GRNSAZ filter test to my APRSISCE/32 RF monitor instance and have only seen:

            2013-06-12T16:51:52.114 IS[APRS-IS](Hit(b/GRNSAZ)) [0]GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.9

            Asking it for the traffic counts, APRSISCE/32 IGates have only been receiving one per hour, but skipped two recent hours (the I: line below):

            UIDIGI 1.9

            Sym: Red Dot (//)
            Packet(45m46s):GRNSAZ NW 7382mi N7QVU-11
            I: 0 1 0 1 1 1 1 1
            FromME: 5649mi E (94º)
            GridSquare: JJ00aa
            0000.00N 00000.00E
            2013-06-12 16:51:52 (45m41s)
            AltNet: UIDIGI
            RemRF

            But now that I've said that, I wonder if it counts parse-failed packets?  I suspect it doesn't because it's not even sure if it can trust the source callsign.  Even my FilterTest probably won't pick it up because ParseFailed packets are dropped pretty early in the packet processing.

            Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


          • Heikki Hannikainen
            ... Having a few bad packets on the Internet (aprs.fi / APRS-IS) doesn t do much harm to anyone, especially if the digi only damages its own position packets.
            Message 5 of 20 , Jun 13, 2013
            • 0 Attachment
              On Wed, Jun 12, 2013 at 7:48 PM, Jerry Wyatt, n7qvu <n7qvu@...> wrote:
              I understand the official position, but its been discussed here many times certain needs to block packets/users 'behaving' badly.

              Having a few bad packets on the Internet (aprs.fi / APRS-IS) doesn't do much harm to anyone, especially if the digi only damages its own position packets. It'd be worse if the digi retransmitted corrupted versions of packets sent by other stations, but apparently that's not happening in this case.

              In general, I think it's better to have these bad packets go through the igates and to aprs.fi, so that we know about them, and that they're archived for everyone to see. It probably encourages fixing problems better than if we just started to ignore the problem. If we hide bad received packets on the igates, they don't magically disappear from RF.

              The problem needs to be fixed at the source, and not just hidden from one view. I'd much rather increase the visibility of bad configurations and increase the peer pressure to get them fixed.

              - Hessu, OH7LZB (aprs.fi)
               
            • Jerry Wyatt, n7qvu
              Just heard that GRNSAZ digi was shutdown yesterday. I checked APRS.FI and confirmed that it doesn t seem to be beaconing.   Last beacon(RIP): 2013-06-12
              Message 6 of 20 , Jun 13, 2013
              • 0 Attachment
                Just heard that GRNSAZ digi was shutdown yesterday. I checked APRS.FI and confirmed that it doesn't seem to be beaconing.
                 
                Last beacon(RIP):
                2013-06-12 14:58:32 PDT: GRNSAZ>
                 
                Thanks to the AZ Freq Coordinators for quick action,
                 
                Jerry Wyatt - N7QVU
                Overgaard, AZ
                ps: The invalid raw packet listing from APRS.FI sealed it...

                From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
                To: aprsisce@yahoogroups.com
                Sent: Wednesday, June 12, 2013 10:41 AM
                Subject: Re: [aprsisce] Need to block invalid format digi site?
                 
                On 6/12/2013 1:26 PM, Fred Hillhouse wrote:
                Are you able to see any of the packets in question?
                 
                The only thing I can see anything with is APRS.FI.

                I added a b/GRNSAZ filter test to my APRSISCE/32 RF monitor instance and have only seen: 2013-06-12T16:51:52.114 IS[APRS-IS](Hit(b/GRNSAZ)) [0]GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.9 Asking it for the traffic counts, APRSISCE/32 IGates have only been receiving one per hour, but skipped two recent hours (the I: line below):
                UIDIGI 1.9

                Sym: Red Dot (//)
                Packet(45m46s):GRNSAZ NW 7382mi N7QVU-11
                I: 0 1 0 1 1 1 1 1
                FromME: 5649mi E (94º)
                GridSquare: JJ00aa
                0000.00N 00000.00E
                2013-06-12 16:51:52 (45m41s)
                AltNet: UIDIGI
                RemRF
                But now that I've said that, I wonder if it counts parse-failed packets?  I suspect it doesn't because it's not even sure if it can trust the source callsign.  Even my FilterTest probably won't pick it up because ParseFailed packets are dropped pretty early in the packet processing. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
              • Steve Daniels
                Is that not a bit cutting off your nose to spite your face? It might have been sending itÆs own location incorrectly, but now everyone has lost a well sited
                Message 7 of 20 , Jun 13, 2013
                • 0 Attachment

                  Is that not a bit cutting off your nose to spite your face? It might have been sending it’s own location incorrectly, but now everyone has lost a well sited digi.

                  If I read correctly it was digipeating fine, and you said it was needed.

                   

                   

                  Steve Daniels

                  Amateur Radio Callsign G6UIM

                  Torbay Freecycle  Owner

                  http://uk.groups.yahoo.com/group/torbay_freecycle

                  APRSISCE/32 Beta tester and WIKI editor http://aprsisce.wikidot.com

                   


                  From: aprsisce@yahoogroups.com [mailto: aprsisce@yahoogroups.com ] On Behalf Of Jerry Wyatt, n7qvu
                  Sent: 13 June 2013 18:54
                  To: aprsisce@yahoogroups.com
                  Subject: Re: [aprsisce] Need to block invalid format digi site?

                   

                   

                  Just heard that GRNSAZ digi was shutdown yesterday. I checked APRS.FI and confirmed that it doesn't seem to be beaconing.

                   

                  Last beacon(RIP):

                  2013-06-12 14:58:32 PDT: GRNSAZ>

                   

                  Thanks to the AZ Freq Coordinators for quick action,

                   

                  Jerry Wyatt - N7QVU

                  Overgaard, AZ

                  ps: The invalid raw packet listing from APRS.FI sealed it...

                   

                  From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
                  To: aprsisce@yahoogroups.com
                  Sent: Wednesday, June 12, 2013 10:41 AM
                  Subject: Re: [aprsisce] Need to block invalid format digi site?

                   

                  On 6/12/2013 1:26 PM, Fred Hillhouse wrote:

                  Are you able to see any of the packets in question?

                   

                  The only thing I can see anything with is APRS.FI.

                   

                  I added a b/GRNSAZ filter test to my APRSISCE/32 RF monitor instance and have only seen: 2013-06-12T16:51:52.114 IS[APRS-IS](Hit(b/GRNSAZ)) [0]GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.9 Asking it for the traffic counts, APRSISCE/32 IGates have only been receiving one per hour, but skipped two recent hours (the I: line below):

                  UIDIGI 1.9

                  Sym: Red Dot (//)
                  Packet(45m46s):GRNSAZ NW 7382mi N7QVU-11
                  I: 0 1 0 1 1 1 1 1
                  FromME: 5649mi E (94º)
                  GridSquare: JJ00aa
                  0000.00N 00000.00E
                  2013-06-12 16:51:52 (45m41s)
                  AltNet: UIDIGI
                  RemRF

                  But now that I've said that, I wonder if it counts parse-failed packets?  I suspect it doesn't because it's not even sure if it can trust the source callsign.  Even my FilterTest probably won't pick it up because ParseFailed packets are dropped pretty early in the packet processing. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

                • James Ewen
                  Tossing out the baby with the bathwater is sometimes the only solution you can get. If they were able to remotely disable the digipeater, they should have been
                  Message 8 of 20 , Jun 13, 2013
                  • 0 Attachment
                    Tossing out the baby with the bathwater is sometimes the only solution
                    you can get.

                    If they were able to remotely disable the digipeater, they should have
                    been able to remotely correct the error as well.

                    If they made a trip up to the digipeater, there too was an opportunity
                    to correct the issue.

                    Sometimes people would rather just pull the plug than fix the issue.
                    There's less work involved.

                    It's amazing how often there are communications issues in a hobby that
                    is all about communicating.


                    On 6/13/13, Steve Daniels <steve@...> wrote:
                    > Is that not a bit cutting off your nose to spite your face? It might have
                    > been sending it’s own location incorrectly, but now everyone has lost a
                    > well
                    > sited digi.
                    >
                    > If I read correctly it was digipeating fine, and you said it was needed.
                    >
                    >
                    >
                    >
                    >
                    > Steve Daniels
                    >
                    > Amateur Radio Callsign G6UIM
                    >
                    > Torbay Freecycle Owner
                    >
                    > http://uk.groups.yahoo.com/group/torbay_freecycle
                    >
                    > APRSISCE/32 Beta tester and WIKI editor http://aprsisce.wikidot.com
                    >
                    >
                    >
                    > _____
                    >
                    > From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf
                    > Of Jerry Wyatt, n7qvu
                    > Sent: 13 June 2013 18:54
                    > To: aprsisce@yahoogroups.com
                    > Subject: Re: [aprsisce] Need to block invalid format digi site?
                    >
                    >
                    >
                    >
                    >
                    > Just heard that GRNSAZ digi was shutdown yesterday. I checked APRS.FI and
                    > confirmed that it doesn't seem to be beaconing.
                    >
                    >
                    >
                    > Last beacon(RIP):
                    >
                    > 2013-06-12 14:58:32 PDT: <http://aprs.fi/?c=raw&limit=&call=GRNSAZ>
                    > GRNSAZ>
                    >
                    >
                    >
                    > Thanks to the AZ Freq Coordinators for quick action,
                    >
                    >
                    >
                    > Jerry Wyatt - N7QVU
                    >
                    > Overgaard, AZ
                    >
                    > ps: The invalid raw packet listing from APRS.FI sealed it...
                    >
                    >
                    >
                    > From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
                    > To: aprsisce@yahoogroups.com
                    > Sent: Wednesday, June 12, 2013 10:41 AM
                    > Subject: Re: [aprsisce] Need to block invalid format digi site?
                    >
                    >
                    >
                    >
                    >
                    > On 6/12/2013 1:26 PM, Fred Hillhouse wrote:
                    >
                    > Are you able to see any of the packets in question?
                    >
                    >
                    >
                    > The only thing I can see anything with is APRS.FI.
                    >
                    >
                    >
                    > I added a b/GRNSAZ filter test to my APRSISCE/32 RF monitor instance and
                    > have only seen: 2013-06-12T16:51:52.114 IS[APRS-IS](Hit(b/GRNSAZ))
                    > [0]GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.9 Asking it for the traffic counts,
                    > APRSISCE/32 IGates have only been receiving one per hour, but skipped two
                    > recent hours (the I: line below):
                    >
                    > UIDIGI 1.9
                    >
                    > Sym: Red Dot (//)
                    > Packet(45m46s):GRNSAZ NW 7382mi N7QVU-11
                    > I: 0 1 0 1 1 1 1 1
                    > FromME: 5649mi E (94º)
                    > GridSquare: JJ00aa
                    > 0000.00N 00000.00E
                    > 2013-06-12 16:51:52 (45m41s)
                    > AltNet: UIDIGI
                    > RemRF
                    >
                    > But now that I've said that, I wonder if it counts parse-failed packets? I
                    > suspect it doesn't because it's not even sure if it can trust the source
                    > callsign. Even my FilterTest probably won't pick it up because ParseFailed
                    > packets are dropped pretty early in the packet processing. Lynn (D) -
                    > KJ4ERJ
                    > - Author of APRSISCE for Windows Mobile and Win32
                    >
                    >
                    >
                    >

                    --
                    Sent from my mobile device

                    James
                    VE6SRV
                  • Fred Hillhouse
                    There will still be a digipeater but that that one. _____ From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Steve Daniels Sent:
                    Message 9 of 20 , Jun 13, 2013
                    • 0 Attachment
                      There will still be a digipeater but that that one.


                      From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf Of Steve Daniels
                      Sent: Thursday, June 13, 2013 16:13
                      To: aprsisce@yahoogroups.com
                      Subject: RE: [aprsisce] Need to block invalid format digi site?

                       

                      Is that not a bit cutting off your nose to spite your face? It might have been sending it’s own location incorrectly, but now everyone has lost a well sited digi.

                      If I read correctly it was digipeating fine, and you said it was needed.

                      Steve Daniels

                      Amateur Radio Callsign G6UIM

                      Torbay Freecycle  Owner

                      http://uk.groups.yahoo.com/group/torbay_freecycle

                      APRSISCE/32 Beta tester and WIKI editor http://aprsisce.wikidot.com


                      From: aprsisce@yahoogroups.com [mailto: aprsisce@yahoogroups.com ] On Behalf Of Jerry Wyatt, n7qvu
                      Sent: 13 June 2013 18:54
                      To: aprsisce@yahoogroups.com
                      Subject: Re: [aprsisce] Need to block invalid format digi site?

                       

                      Just heard that GRNSAZ digi was shutdown yesterday. I checked APRS.FI and confirmed that it doesn't seem to be beaconing.

                      Last beacon(RIP):

                      2013-06-12 14:58:32 PDT: GRNSAZ>

                      Thanks to the AZ Freq Coordinators for quick action,

                      Jerry Wyatt - N7QVU

                      Overgaard, AZ

                      ps: The invalid raw packet listing from APRS.FI sealed it...

                      From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
                      To: aprsisce@yahoogroups.com
                      Sent: Wednesday, June 12, 2013 10:41 AM
                      Subject: Re: [aprsisce] Need to block invalid format digi site?

                       

                      On 6/12/2013 1:26 PM, Fred Hillhouse wrote:

                      Are you able to see any of the packets in question?

                      The only thing I can see anything with is APRS.FI.

                      I added a b/GRNSAZ filter test to my APRSISCE/32 RF monitor instance and have only seen: 2013-06-12T16:51:52.114 IS[APRS-IS](Hit(b/GRNSAZ)) [0]GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.9 Asking it for the traffic counts, APRSISCE/32 IGates have only been receiving one per hour, but skipped two recent hours (the I: line below):

                      UIDIGI 1.9

                      Sym: Red Dot (//)
                      Packet(45m46s):GRNSAZ NW 7382mi N7QVU-11
                      I: 0 1 0 1 1 1 1 1
                      FromME: 5649mi E (94º)
                      GridSquare: JJ00aa
                      0000.00N 00000.00E
                      2013-06-12 16:51:52 (45m41s)
                      AltNet: UIDIGI
                      RemRF

                      But now that I've said that, I wonder if it counts parse-failed packets?  I suspect it doesn't because it's not even sure if it can trust the source callsign.  Even my FilterTest probably won't pick it up because ParseFailed packets are dropped pretty early in the packet processing. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

                    • Fred Hillhouse
                      There is a coordination group working on this problem. And it looks likes it is getting rectified. And that will mean a new functioning properly functioning
                      Message 10 of 20 , Jun 13, 2013
                      • 0 Attachment
                        There is a coordination group working on this problem. And it looks likes it
                        is getting rectified. And that will mean a new functioning properly
                        functioning digi. So this is really actually good news.

                        Best regards,
                        Fred N7FMH


                        > -----Original Message-----
                        > From: aprsisce@yahoogroups.com
                        > [mailto:aprsisce@yahoogroups.com] On Behalf Of James Ewen
                        > Sent: Thursday, June 13, 2013 16:59
                        > To: aprsisce@yahoogroups.com
                        > Subject: Re: [aprsisce] Need to block invalid format digi site?
                        >
                        > Tossing out the baby with the bathwater is sometimes the only
                        > solution you can get.
                        >
                        > If they were able to remotely disable the digipeater, they
                        > should have been able to remotely correct the error as well.
                        >
                        > If they made a trip up to the digipeater, there too was an
                        > opportunity to correct the issue.
                        >
                        > Sometimes people would rather just pull the plug than fix the issue.
                        > There's less work involved.
                        >
                        > It's amazing how often there are communications issues in a
                        > hobby that is all about communicating.
                        >
                        >
                        > On 6/13/13, Steve Daniels <steve@...> wrote:
                        > > Is that not a bit cutting off your nose to spite your face?
                        > It might
                        > > have been sending it’s own location incorrectly, but now
                        > everyone has
                        > > lost a well sited digi.
                        > >
                        > > If I read correctly it was digipeating fine, and you said
                        > it was needed.
                        > >
                        > >
                        > >
                        > >
                        > >
                        > > Steve Daniels
                        > >
                        > > Amateur Radio Callsign G6UIM
                        > >
                        > > Torbay Freecycle Owner
                        > >
                        > > http://uk.groups.yahoo.com/group/torbay_freecycle
                        > >
                        > > APRSISCE/32 Beta tester and WIKI editor http://aprsisce.wikidot.com
                        > >
                        > >
                        > >
                        > > _____
                        > >
                        > > From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On
                        > > Behalf Of Jerry Wyatt, n7qvu
                        > > Sent: 13 June 2013 18:54
                        > > To: aprsisce@yahoogroups.com
                        > > Subject: Re: [aprsisce] Need to block invalid format digi site?
                        > >
                        > >
                        > >
                        > >
                        > >
                        > > Just heard that GRNSAZ digi was shutdown yesterday. I
                        > checked APRS.FI
                        > > and confirmed that it doesn't seem to be beaconing.
                        > >
                        > >
                        > >
                        > > Last beacon(RIP):
                        > >
                        > > 2013-06-12 14:58:32 PDT: <http://aprs.fi/?c=raw&limit=&call=GRNSAZ>
                        > > GRNSAZ>
                        > >
                        > >
                        > >
                        > > Thanks to the AZ Freq Coordinators for quick action,
                        > >
                        > >
                        > >
                        > > Jerry Wyatt - N7QVU
                        > >
                        > > Overgaard, AZ
                        > >
                        > > ps: The invalid raw packet listing from APRS.FI sealed it...
                        > >
                        > >
                        > >
                        > > From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
                        > > To: aprsisce@yahoogroups.com
                        > > Sent: Wednesday, June 12, 2013 10:41 AM
                        > > Subject: Re: [aprsisce] Need to block invalid format digi site?
                        > >
                        > >
                        > >
                        > >
                        > >
                        > > On 6/12/2013 1:26 PM, Fred Hillhouse wrote:
                        > >
                        > > Are you able to see any of the packets in question?
                        > >
                        > >
                        > >
                        > > The only thing I can see anything with is APRS.FI.
                        > >
                        > >
                        > >
                        > > I added a b/GRNSAZ filter test to my APRSISCE/32 RF monitor
                        > instance
                        > > and have only seen: 2013-06-12T16:51:52.114
                        > IS[APRS-IS](Hit(b/GRNSAZ))
                        > > [0]GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.9 Asking it for the traffic
                        > > counts,
                        > > APRSISCE/32 IGates have only been receiving one per hour,
                        > but skipped
                        > > two recent hours (the I: line below):
                        > >
                        > > UIDIGI 1.9
                        > >
                        > > Sym: Red Dot (//)
                        > > Packet(45m46s):GRNSAZ NW 7382mi N7QVU-11
                        > > I: 0 1 0 1 1 1 1 1
                        > > FromME: 5649mi E (94º)
                        > > GridSquare: JJ00aa
                        > > 0000.00N 00000.00E
                        > > 2013-06-12 16:51:52 (45m41s)
                        > > AltNet: UIDIGI
                        > > RemRF
                        > >
                        > > But now that I've said that, I wonder if it counts parse-failed
                        > > packets? I suspect it doesn't because it's not even sure if it can
                        > > trust the source callsign. Even my FilterTest probably
                        > won't pick it
                        > > up because ParseFailed packets are dropped pretty early in
                        > the packet
                        > > processing. Lynn (D) - KJ4ERJ
                        > > - Author of APRSISCE for Windows Mobile and Win32
                        > >
                        > >
                        > >
                        > >
                        >
                        > --
                        > Sent from my mobile device
                        >
                        > James
                        > VE6SRV
                        >
                        >
                        > ------------------------------------
                        >
                        > Yahoo! Groups Links
                        >
                        >
                        >
                      • Jerry Wyatt, n7qvu
                        The site(GRNSAZ) was taken down mainly because the owner would not maintain it nor let anyone else. It had not been digi-ing for many months. Most everybody
                        Message 11 of 20 , Jun 13, 2013
                        • 0 Attachment
                          The site(GRNSAZ) was taken down mainly because the owner would not maintain it nor let anyone else. It had not been digi-ing for many months. Most everybody thought it had died, until I showed them via APRS.fi it was beaconing every 30 minutes. Info I obtained about the owner was that he just allowed a friend to install it in his building site and friend is gone now!
                           
                          I anticipate a new digi will be operation by end of this month on the same mountain(10,500') but at a different building site. There has been a large hole in the network here w/o that site.
                           
                          I don't care who owns the active digi on that great site in NE Arizona, just that there is one and its maintained.
                           
                          Thanks again,
                          Jerry - N7QVU
                            

                          From: Steve Daniels <steve@...>
                          To: aprsisce@yahoogroups.com
                          Sent: Thursday, June 13, 2013 1:13 PM
                          Subject: RE: [aprsisce] Need to block invalid format digi site?
                           
                          Is that not a bit cutting off your nose to spite your face? It might have been sending it’s own location incorrectly, but now everyone has lost a well sited digi.
                          If I read correctly it was digipeating fine, and you said it was needed.
                           
                           
                          Steve Daniels
                          Amateur Radio Callsign G6UIM
                          Torbay Freecycle  Owner
                          APRSISCE/32 Beta tester and WIKI editor http://aprsisce.wikidot.com/
                           
                          From: aprsisce@yahoogroups.com [mailto: aprsisce@yahoogroups.com ] On Behalf Of Jerry Wyatt, n7qvu
                          Sent: 13 June 2013 18:54
                          To: aprsisce@yahoogroups.com
                          Subject: Re: [aprsisce] Need to block invalid format digi site?
                           
                           
                          Just heard that GRNSAZ digi was shutdown yesterday. I checked APRS.FI and confirmed that it doesn't seem to be beaconing.
                           
                          Last beacon(RIP):
                          2013-06-12 14:58:32 PDT: GRNSAZ>
                           
                          Thanks to the AZ Freq Coordinators for quick action,
                           
                          Jerry Wyatt - N7QVU
                          Overgaard, AZ
                          ps: The invalid raw packet listing from APRS.FI sealed it...
                           
                          From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
                          To: aprsisce@yahoogroups.com
                          Sent: Wednesday, June 12, 2013 10:41 AM
                          Subject: Re: [aprsisce] Need to block invalid format digi site?
                           
                          On 6/12/2013 1:26 PM, Fred Hillhouse wrote:
                          Are you able to see any of the packets in question?
                           
                          The only thing I can see anything with is APRS.FI.
                           
                          I added a b/GRNSAZ filter test to my APRSISCE/32 RF monitor instance and have only seen: 2013-06-12T16:51:52.114 IS[APRS-IS](Hit(b/GRNSAZ)) [0]GRNSAZ>UIDIGI,qAR,N7QVU-11:UIDIGI 1.9 Asking it for the traffic counts, APRSISCE/32 IGates have only been receiving one per hour, but skipped two recent hours (the I: line below):
                          UIDIGI 1.9

                          Sym: Red Dot (//)
                          Packet(45m46s):GRNSAZ NW 7382mi N7QVU-11
                          I: 0 1 0 1 1 1 1 1
                          FromME: 5649mi E (94º)
                          GridSquare: JJ00aa
                          0000.00N 00000.00E
                          2013-06-12 16:51:52 (45m41s)
                          AltNet: UIDIGI
                          RemRF
                          But now that I've said that, I wonder if it counts parse-failed packets?  I suspect it doesn't because it's not even sure if it can trust the source callsign.  Even my FilterTest probably won't pick it up because ParseFailed packets are dropped pretty early in the packet processing. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
                        • Robert Bruninga
                          Remember, a fully functioning digi also includes local DIRECT beacons of recommended FREQ objects in the area. see: http://aprs.org/localinfo.html thanks Bob,
                          Message 12 of 20 , Jun 13, 2013
                          • 0 Attachment
                            Remember, a fully functioning digi also includes local DIRECT beacons
                            of recommended FREQ objects in the area. see:
                            http://aprs.org/localinfo.html

                            thanks
                            Bob, WB4APR

                            > There is a coordination group working on this problem. And it looks likes it
                            > is getting rectified. And that will mean a new functioning properly
                            > functioning digi. So this is really actually good news.
                          Your message has been successfully submitted and would be delivered to recipients shortly.