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

570RE: [tracker2] Firmware build 53875

Expand Messages
  • Cap Pennell
    May 30, 2006
    • 0 Attachment
      FB, thanks.  It doesn't hurt to do that (insert the "*" after the WIDEn after the last hop is used up), but it's only _necessary_ after the WIDE1 to allow the next hop with a mobile user's WIDE1-1,WIDE2-1 path.  It may be desireable after "SSn-N" (or TEMPn-N) is used up too.
      73, Cap KE6AFE
      -----Original Message-----
      From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com]On Behalf Of scott@...
      Sent: Tuesday, May 30, 2006 09:36 AM
      To: tracker2@yahoogroups.com
      Subject: RE: [tracker2] Firmware build 53875

      It'll do the first one... should the replacement that you show happen any time a WIDEn-N is used up?
       
      Scott


      From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Cap Pennell
      Sent: Saturday, May 27, 2006 9:09 PM
      To: tracker2@yahoogroups.com
      Subject: RE: [tracker2] Firmware build 53875

      Does
      ALIAS WIDE, HOPLIMIT 1, DIGIID ON: APRS via WIDE1-1,WIDE2-1 become APRS via MYCALL, WIDE1*,WIDE2-1
      (with the "*" after WIDE1)  ?
      Or become APRS via MYCALL*,WIDE2-1 (or something like that, to allow the second hop from that next digi down the road) ?  Hope so.
      73, Cap KE6AFE
    • Show all 12 messages in this topic