user1878: I am experimenting with leaving a public replica of the Bitcoin chain on the internet.  In doing so I'm actively monitoring the debug output so I can get a sense of what is happening with the inbound connections.
How can I tell what the clients are doing and respond appropriately? 
Under what criteria should I block a port to an IP address, subnet, etc?

user153: You are looking for ways to improve the client's protections against flaws? 
Here's a list of its current protections:

http://en.bitcoin.it/wiki/Weaknesses#Denial_of_Service_.28DoS.29_attacks


1878: <p>I am experimenting with leaving a public replica of the Bitcoin chain on the internet.  In doing so I'm actively monitoring the debug output so I can get a sense of what is happening with the inbound connections.</p>

<p>How can I tell what the clients are doing and respond appropriately? </p>

<p>Under what criteria should I block a port to an IP address, subnet, etc?</p>
 153: <p>You are looking for ways to improve the client's protections against flaws? </p>

<p>Here's a list of its current protections:</p>

<ul>
<li><a href="http://en.bitcoin.it/wiki/Weaknesses#Denial_of_Service_.28DoS.29_attacks" rel="nofollow">http://en.bitcoin.it/wiki/Weaknesses#Denial_of_Service_.28DoS.29_attacks</a></li>
</ul>
