|
|
Posted by -Angela- on 10/20/05 15:20
On 20 Oct 2005 11:53:05 GMT, "fred-bloggs"
<fred-bloggs@hahahotmail.com> wrote:
>-Angela- <TarapiaTapioco@jetmail.com> wrote in
>news:22ldl15k7e4kdjdhiaq05jk1qhgfs5t93q@4ax.com:
>
>> On Wed, 19 Oct 2005 15:12:28 -0700, gregfarr <gregfarr@comcast.net>
>> wrote:
>>
>>>Just minutes age I was watching winmx at the time, the bottom just
>>>dropped out of the bandwidth. The Primary's started changing from 6 to
>>>5 to 3, several of the up loaders with cancelled out, my d/l's went
>>>from a 100 down to almost nothing. This has happened before, just not
>>>while I was looking. I'm cable comcast.
>>>
>>>Greg
>>>http://gregsplace.50megs.com
>>>http://www.picturetrail.com/fugitive1
>>
>> Check your bandwidth graph when this is happening. You'll probably
>> see a huge spike on your outgoing WPN packets. This would indicate
>> that you are hosting a fake / flooder (secondary) that has sent their
>> results from someones' search, and you being the priamary they are
>> served by, your connection just suffered a UDP packet storm that
>> overwhelmed (killed) your TCP connections.
>
>I believe the spike is actually *incoming* WPN UDP packets, which would
>imply that one of your secondaries has searched for a fake file. You are
>actually being flooded by your primaries :(
Fred, You are right, it is the *incomming* that suffers. Same result
though, connections get kicked. Usually can only happen so severe as
to kill connections when the flooder is on your system. A flooder
searched through your system getting results from another primary you
are connected to will kill that primary, not you.
>
>> I keep saying it, and nobody is listening: Do *NOT* trust the patches
>> and Dll's to protect you from the flooders. You have more than your
>> TCP connections to loose. Use your own firewall and enter the TCP
>> blocks I posted before here:
>>
>> news:jbj3l1hn4ih1mje1015incs1quo9pbup0r@4ax.com
>>
>
>The floods will only be prevented if EVERY primary refuses connection to
>ALL fakers - unlikely, unfortunately. Even if *everyone* ran a filtering
>dll it would only take 1 unfiltered address to compromise the network.
Navigation:
[Reply to this message]
|