From: none@none.invalid   
      
   On 15 Jun 2011 20:33:34 GMT, Jorgen Grahn    
   wrote:   
      
   >On Wed, 2011-06-15, SebastiaNot wrote:   
   >>   
   >> Hi, all.   
   >> We have a server running Red Hat 5, where lots of remote clients   
   >> connect on a specific port, lets say 1234.   
   >>   
   >> I run the command "netstat -an | grep 1234" and I get a listing of   
   >> remote IP's that are connected to this service.   
   >>   
   >> I would need a command to disconnect a specific IP (lets say   
   >> 11.22.33.44) from my port.   
   >>   
   >> Any ideas ?   
   >   
   >The best way by far is to do it with the cooperation of whatever   
   >server process is running on port 1234.  I.e. there should be a   
   >command you can send it "hey, kill all your connections with   
   >11.22.33.44".   
   >   
   >I don't think there's an easy general way to kill existing TCP   
   >connections from the outside (or more generally, introduce a fatal   
   >error on another process' file descriptor).   
   >   
   >/Jorgen   
      
   Under the heading of "what not to do", Comcast was forging TCP Resets   
   a couple of years ago to kill certain P2P traffic. It was apparently   
   effective until people started complaining.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)