<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Yes it does.... A better way to block someone is to allow them ONE hop
(so they see -- err think -- they are being digipeated). With digined
you could rewrite their entire path to something more benign. Case in
point, there was a guy in NC that wouldn't listen to the local
digiowners, and ran a crazy path with RELAY on the end. After many
attempts to correct the problem, they finally budlisted him on numerous
digi's. The guy filed for a vanity call and they budlisted that
callsign. Then he got a 160W amp and ran a path of RELAY RELAY RELAY
RELAY. Thats when I started seeing him down here in SC.<br>
<br>
Wes<br>
<br>
Robert Bruninga wrote:
<blockquote cite="mids3149f2f.067@FSGWHUB.usna.edu" type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:bruce.coates@Sasktel.net">bruce.coates@Sasktel.net</a> 08/30/05 2:46 PM >>>
</pre>
</blockquote>
</blockquote>
<pre wrap="">We have a similar culprit...because he has a very small
turn angle set in his smart beaconing.
...I've actually put him in my BUDLIST on
the main digipeater to try to keep a handle
on the QRM.
</pre>
</blockquote>
<pre wrap=""><!---->
That often backfires. The individual seeing
his tracking get worse will only increase his
rate to the max, and narrow his smart
beaconing to generate even more packets to
try to overcome the "problem" he is seeing...
good luck
bob
_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a>
<a class="moz-txt-link-freetext" href="https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</body>
</html>