[PROXYPER] What's happening to my 304?

Bryan Talbot btalbot at ucsd.edu
Tue Feb 9 00:39:21 EST 1999


So why not block the entire subnet?  It sounds like someone is attacking
your proxy.  Although this is just an annoyance, it is still an attack.



-----Original Message-----
From: Phillip <phile at phile.com.au>
To: proxyper at lists.distributed.net <proxyper at lists.distributed.net>
Date: Monday, February 08, 1999 11:41 PM
Subject: [PROXYPER] What's happening to my 304?


>I've wracked my brains for 2 days and can't work out what the
>problem is - so I'm open to any suggestions here.
>
>I've been running 304 for about a week without probs. This proxy
>servers a few home machines, a few work machines, and a few
>people outside my network.
>
>About 2 days ago I started getting repeated attempts to connect
>from a particular IP. But the connection was never successful. This
>is repeated every second or so. To give an idea of the traffic this
>is generating, before this happened my daily 304 console logs were
>between 2 and 2.5 MB. Yesterday it was 8 MB. Todays ended up at
>just under 14 MB. There is no corresponding increase
>in the blocks fetched or flushed.
>
>I tried an IgnoredIP line in the ini which stopped him connecting, but
>didn't stop it trying. Then after several hours, he switched to a diff
>IP (twice). I don't really want to ignore a whole Class C subnet, and
>I've now removed the IgnoredIP's.
>
>With the frequency and persistence,  I suspect it must be another
>personal proxy trying to connect but is somehow failing. I tried
>shutting down the proxy, unlocking and repairing buff files just in
>case the problem was mine, but it didn't make any difference -
>besides from what I can see, all other clients and IP's have no
>problems.
>
>I've included a few lines from the console output if that helps.
>
>02/08/99 20:32:13,209.79.136.50: Client requesting communication
>02/08/99 20:32:13,Client 209.79.136.50 no longer connected (reading).
>02/08/99 20:32:13,209.79.136.50: Closing client connection.
>02/08/99 20:32:13,Client 209.79.136.50 no longer connected (reading).
>02/08/99 20:32:13,209.79.136.50: Closing client connection.
>02/08/99 20:32:14,Accepted connection from address 209.79.136.50
>02/08/99 20:32:14,209.79.136.50: Client requesting communication
>02/08/99 20:32:14,Accepted connection from address 209.79.136.50
>02/08/99 20:32:14,209.79.136.50: Client requesting communication
>02/08/99 20:32:15,Client 209.79.136.50 no longer connected (reading).
>02/08/99 20:32:15,209.79.136.50: Closing client connection.
>02/08/99 20:32:15,Client 209.79.136.50 no longer connected (reading).
>02/08/99 20:32:15,209.79.136.50: Closing client connection.
>02/08/99 20:32:16,Accepted connection from address 209.79.136.50
>02/08/99 20:32:16,209.79.136.50: Client requesting communication
>02/08/99 20:32:16,Accepted connection from address 209.79.136.50
>02/08/99 20:32:16,209.79.136.50: Client requesting communication
>02/08/99 20:32:17,Client 209.79.136.50 no longer connected (reading).
>02/08/99 20:32:17,209.79.136.50: Closing client connection.
>
>Cheers
>Phillip
>
>
>
>
>--
>To unsubscribe, send 'unsubscribe proxyper' to
majordomo at lists.distributed.net
>

--
To unsubscribe, send 'unsubscribe proxyper' to majordomo at lists.distributed.net



More information about the proxyper mailing list