Posted by FinnTroll on 09/26/05 19:45

"db" <@ .> skrev i meddelandet
news:43383ea5$0$15038$ed2619ec@ptn-nntp-reader02.plus.net...
>
> "FinnTroll" <yab@roll.uc> wrote in message
> news:5HVZe.34750$d5.190002@newsb.telia.net...
>>
>> "db" <@ .> skrev i meddelandet
>> news:4336d8c5$0$16315$ed2619ec@ptn-nntp-reader01.plus.net...
>>> (odd, first post failed to post correctly so reposted (also slightly edited as
>>> the original was arse))
>>><snip>
>>> Any updated blocklists can be found at:
>>>
>>> http://www.nodata.plus.com/bin/bbbbip-blocklists/
>>>
>>> ...
>>>
>>> Hopefully it's a very easy package to put to work as all that's required is
>>> the user place the following 3 files into their WinMX program folder and
>>> restart WinMX (if it's currently running).
>>>
>>> Feedback appreciated.
>>
>> Well, I don't know if this will be useful, but installing the goods was a peace
>> of cake ... and from the looks of it, there's also an increase in u/l with
>> better speed than before. Same goes for d/l ... better speed and WinMX starts
>> and gives the green light faster right now...
>
> Good stuff. It shouldn't actually affect anything transfer-wise. It's actually
> just a very simple, transparent, package that acts as a middleman between the
> WinMX client and the Windows WS2_32.DLL "Winsock" which handles all TCP/UDP
> communications. All it does is check the IP addresses that run through the
> middleman DLL (WS2_32R.DLL) against those listed in the bendmx.dat file, so, if
> an address contained in the DAT file matches one the WinMX client is trying to
> either send to, or receive from, it blocks it dead.
>

I see ... I better admit straight away I am a newbie on WinMX, but have been
learning by reading here in the NG ... I get the picture of the WSR_32.DLL's role
as a "doorkeeper", but in the context I need to ask ... what is is that makes a
certain IP approved vs. blocked in the first place? I understand an IP is being
blocked if it can be found in the BendMX but what makes it "bad" and be rewarded a
place in the "hall of shame", so to speak?

I have been running WinMX now for a couple of hours ... no d/l, but a mere couple
in the beginning to check things. Since then I have been watching the transfers
window, trying to figure out what makes some u/l'ers never be connected, while
others are being que'ed. While watching the u/l speed I notice that it doesn't
matter much what type of connection speed they have ... speed ranges between
2,5K/s to around 30K/s. It makes me wonder if there's something I missed in the
settings. I would expect a higher rate since I am on a 7/1 DSL and I have set the
Queing to allow 4/2 at once.

> Sure. Just edit it in Notepad if you like. Ultimately you'd probably be
> required to do this in order to maintain an accurate blocklist as the media
> companies change addresses fairly frequently (some of them, at least). I'll
> update the bendmx.dat files for a period of time but can't guarantee for how
> long.

yeah ... I found the "readme"-txt file right after I had hit the <send> button :-)

> Thanks for the feedback.

You're welcome ... I thank you in return for your efforts in making WinMX a great
product.

> P.S. It should create a log file in your WinMX program folder when it blocks
> addresses so have a look for that to see how well it's doing (should be very
> busy on primary connections).

fer sure :-) ... I opened the log file and had a look inside it... during 6.20pm
upto 8.20pm this evening I had 500 "blocked IP".. however several of those came
from the same source, with the same user number, or changed. Something odd though,
I am still running the WinMX as I type and there's been no added IP's in the log
file since then :-\

[Back to original message]