<html><head></head><body><div>It is working now with the commas...spoke to soon. Not sure why it didn't work on the first few attempts but verified working now..</div><div><br></div><div>Thanks for the response...</div><div><br></div><div>73</div><div><br></div><div><br></div><div>On Fri, 2017-11-10 at 17:22 -0500, Dan Srebnick wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Thread seems to have fallen off the list, looping the list back in...</div><div><br></div><div>It didn't work with commas, that was the first method I attempted.</div><div><br></div><div>On Fri, 2017-11-10 at 13:17 -0800, Kenneth Finnegan wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="auto">I'm actually out at a conference all weekend without a laptop, so I can't say off the top of my head, but I'd expect aprx to support a multihop path just by listing them with commas? Maybe someone else in front of a computer will chime in before I get back. <br><br><div data-smartmail="gmail_signature">Kenneth Finnegan</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Nov 10, 2017 10:59, "Dan Srebnick" <<a href="mailto:k2dls@k2dls.net">k2dls@k2dls.net</a>> wrote:<br type="attribution"><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><div><div>Kevin, does aprx support multiple via paths on a single beacon? I tried a few syntactical variants and it doesn't not seem to work:</div><div><br></div><div>beacon via DIGI1,DIGI2</div><div>beacon via DIGI1 via DIGI2</div><div><br></div><div>The question does not seem to be addressed anywhere in the documentation.</div><div><br></div><div>73,</div><div><br></div><div>Dan</div><div><br></div></div><div>On Fri, 2017-11-10 at 08:07 -0800, Kenneth Finnegan wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="auto"><div>If you're only interested in a specific two digis, you could instead generate two packets with specific paths of "DIGIA" and "DIGIB" or one packet with "DIGIA,DIGIB" to elliminate the need to get buy-in and continued support from other operators. </div><div dir="auto"><br></div><div dir="auto">Depends if they happen to have digipeating on their own call turned on. <br><br><div data-smartmail="gmail_signature" dir="auto">Kenneth Finnegan</div><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On Nov 10, 2017 07:34, "Dan Srebnick" <<a href="mailto:k2dls@k2dls.net" target="_blank">k2dls@k2dls.net</a>> wrote:<br type="attribution"><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">I live near the NJ shore and send wx alerts via RF that relate to<br>
coastal waters. There is no need to propagate these alerts inland.<br>
There are a couple of high profile digis along the coast and I was<br>
thinking about using the SSn-N model to create a via path that would<br>
ONLY get digi'd along the coast by participating stations.<br>
<br>
I was thinking of something along the lines of MMn-N and then asking<br>
the operators of the two digis of interest if they would set that up<br>
using the UIFLOOD definition usually used for SSn-N.<br>
<br>
Any thoughts or suggestions?<br>
<br>
______________________________<wbr>_________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
<a href="http://www.tapr.org/mailman/listinfo/aprssig" rel="noreferrer" target="_blank">http://www.tapr.org/mailman/li<wbr>stinfo/aprssig</a><br>
</blockquote></div><br></div></div></div>
</blockquote></div></blockquote></div></div>
</blockquote></blockquote></body></html>