<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; CHARSET=UTF-8">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>It is my experience that you must set the
hop_table.pl number one higher than you think. I must set PC16 to 1 in
order to not send it. And setting PC19 to 11 results in it going out with
a hop count of 10.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2> Tom
WB8ZRL</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV><BR></DIV>Hi:<BR><BR>question: what exactly does
/spider/data/hop_table.pl control?<BR><BR>problem: a link partner has my
kf3b-2 entry in his %nodehops PC16 and PC17 set to 1. I believe this
means that 16's and 17's should expire in my node (being seen by connected
local users) but not be propagated to my other link partners. <BR><BR>in
my %nodehops, I have set a different link partner's entry set to 0 for
PC16 and PC17, yet in the debug data log am sending PC16's and PC17's to that
node despite my hop_table settings.<BR><BR>Am I getting it wrong?<BR><BR>Is
there more descriptive documentation somewhere you can refer me
to?<BR><BR>Thanks,<BR>Alan KF3B-2<BR><BR><BR><BR><BR><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>Dxspider-support
mailing
list<BR>Dxspider-support@dxcluster.org<BR>http://www.tobit.co.uk/mailman/listinfo/dxspider-support<BR></BLOCKQUOTE></BODY></HTML>