<div>I think I have to come up and give an explanation</div>
<div>As you could see from here <a href="http://www.dxcluster.info/telnet.shtml">http://www.dxcluster.info/telnet.shtml</a></div>
<div>I am the administrator of both BG2RVL-9 and BA2IA-2</div>
<div> </div>
<div>At the beginning ,my friend BA2IA gave me a private server to me for DX Cluster server test</div>
<div>When I worked this out , he want me to set up another system in the name of his callsign (maybe I can call this a paying back?)</div>
<div>So, here comes two clusters on one IP but different port number<br></div>
<div>Don't know if you are still going to treat my two nodes as badnode?</div>
<div> </div>
<div>Hoping for your reply</div>
<div> </div>
<div>Yang</div>
<div>BG2RVL</div>
<div><br> </div>
<div class="gmail_quote">2010/7/15 Anthony J. Cioffi (N2KI) <span dir="ltr"><<a href="mailto:n2ki@amsat.org">n2ki@amsat.org</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">I noticed two of those nodes connect to me for spots!<br><br>BG2RVL-9<br>BA2IA-2<br><br>Suggestions?<br><font color="#888888"><br>
Anthony<br></font>
<div class="im"><br><br>-----Original Message-----<br>From: <a href="mailto:dxspider-support-bounces@dxcluster.org">dxspider-support-bounces@dxcluster.org</a> [mailto:<a href="mailto:dxspider-support-bounces@dxcluster.org">dxspider-support-bounces@dxcluster.org</a>] On Behalf Of SM6U, Rickard<br>
Sent: Thursday, July 15, 2010 5:14 AM<br>To: The DXSpider Support list<br></div>
<div class="im">Cc: <a href="mailto:vk3ama.laurie@gmail.com">vk3ama.laurie@gmail.com</a>; The DXSpider Support list<br>Subject: Re: [Dxspider-support] FYI: 4 new nodes added to ROS Auto-Spottingfunction.<br><br></div>
<div>
<div></div>
<div class="h5">I vote YES for cripple mode! Please make it configurable, but on by default.<br><br>Even if it only covers thoose running updated spiders, it will sure cause trouble for the softwares that keep abusing the<br>
cluster network, possibly convincing the creators to change the code.<br><br>/Rick, sm6u<br> on the phone<br><br>14 jul 2010 kl. 09:39 skrev Dirk Koopman <<a href="mailto:djk@tobit.co.uk">djk@tobit.co.uk</a>>:<br><br>
> On 12/07/10 21:51, VK3AMA wrote:<br>>> FYI<br>>><br>>> The latest release of ROS software has added 4 new nodes to<br>>> auto-spotting function.<br>>><br>>> BG2RVL-9 <a href="http://dx.5iyou.cn:7373/" target="_blank">dx.5iyou.cn:7373</a><br>
>> BD5RV <a href="http://dxc.jsdxc.net:7300/" target="_blank">dxc.jsdxc.net:7300</a><br>>> BA2IA-2 <a href="http://spot.ba2ia.com:7300/" target="_blank">spot.ba2ia.com:7300</a><br>>> 9H1LO-1 <a href="http://dx.9h1lo.net:7300/" target="_blank">dx.9h1lo.net:7300</a><br>
>><br>>> At time of this email, of the last 150 ROS cluster spots,<br>>> 148 were auto-generated (98.7%).<br>>><br>><br>> If all major nodes were to do a "set/badword ros" then it probably does not matter that he keeps adding to the list, as the<br>
spots won't propagate very far.<br>><br>> On an other tack: I have been wondering for a while what to do with all the programs (of which the ROS stuff is but one)<br>that insist on logging in, doing one or two things (eg send a spot or sh/dx), then immediately logging out.<br>
><br>> Now, the code already does not bother (in most cases) to send out routing information for these in/out merchants, but I am<br>now thinking that I ought perhaps to be a bit more brutal.<br>><br>> It would be a fairly simple job to have some kind of averaging or pump up timer that has the effect going into "cripple"<br>
mode if the last n connections were less than m seconds long.<br>><br>> "Cripple" mode would something like pretending to be a nice cooperative cluster that accepts spots, but does not send them<br>on, and/or returns a *very* limited view of data such as spots (maybe only two or three spots else spots that are an hour or<br>
so old).<br>><br>> If the user starts to behave like a real person and connects p times for more than m seconds, it automatically comes out of<br>"cripple" mode. While in "cripple" mode for more than (say) 2*m+random amount seconds then de-cripples that user for that<br>
session. This behaviour persists until they have behaved for p sessions.<br>><br>> "Misbehaviour" puts the user back into "cripple" mode.<br>><br>> Views anyone?<br>><br>> Dirk G1TLH<br>
><br>><br>> _______________________________________________<br>> Dxspider-support mailing list<br>> <a href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</a><br>> <a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" target="_blank">http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>_______________________________________________<br>Dxspider-support mailing list<br><a href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</a><br><a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" target="_blank">http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br><br>_______________________________________________<br>Dxspider-support mailing list<br><a href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</a><br><a href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" target="_blank">http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</div></div></blockquote></div><br>