well...actually I was referring to my real firewall, not PG2...and said IP addy is already in there (for what reason, I surely don't remember, but its there)...so, I for one assume I manually put it there for some good reason at some point in time...

as far as PG2, well it seems to do some good for me, at least as far as connections go..sure, if I'm sharing the bad guys get results with my IP addy, but I'm more concerned with blocking them from getting connected to my box in any way, at the very least as a download source for their version of the file (which I'm sure is corrupted)...

and yes, the internal ability to create your own blocklist would be grand...though I'm not sure that would stop search results from being seen by the bad guys..

"search results being seen by the bad guys"? Huh, completely different movie. That's not my problem at all. I don't want to see or route results *from* the bad guys. The former isn't possible at all in Gnutella without a lot of modifications to the protocol and even then you can hardly expect to know all addresses of the "bad guys". I guess everybody has his own set of "bad guys" but with respect to this thread, your set has nothing to do with the issue at hand.

What I wanted to say is that there are several ways to apply IP address filters and most of them are inappropriate. The problem with LimeWire is that it doesn't even block the most obvious spam. Other programs do a great job eradicating virtually 90% of all spam not for themselves (in the GUI) but for the whole network - without resorting to arcane, draconian filters causing tons of casualties that occur if you leave this task to the common user who does and does not have to have a clue how the protocol works.

This may be an arms race, however, there's really nothing to
lose but a lot to win.

Here are the trace route results

Tracing route to 85.88.2.200 over a maximum of 30 hops
1 23 ms 15 ms 15 ms 64.203.233.1.dial-pool-10.pool.hargray.net [64.2
03.233.1]
2 63 ms 67 ms 141 ms 64.203.253.9.unassigned-253.pool.hargray.net [64
.203.253.9]
3 273 ms 58 ms 59 ms 209.221.47.153
4 112 ms 259 ms * 209.221.47.10
5 * 69 ms 82 ms 4.78.210.25
6 121 ms 107 ms 200 ms ae-1-51.bbr1.Atlanta1.Level3.net [4.68.103.1]
7 136 ms 196 ms 140 ms ae-1-0.bbr1.Frankfurt1.Level3.net [212.187.128.3
0]
8 162 ms 132 ms 124 ms ae-22-52.car2.Frankfurt1.Level3.net [4.68.118.48
]
9 147 ms 181 ms 211 ms 62.67.38.22
10 156 ms 153 ms 148 ms core-sto1-p1.netcologne.de [81.173.192.1]
11 196 ms 158 ms 162 ms rtgeman-sto1-g01.netcologne.de [81.173.192.114]
12 161 ms 180 ms 213 ms ge-bb-dea1.netcologne.de [81.173.192.166]
13 197 ms 327 ms 154 ms 195.14.228.42
14 170 ms 137 ms 136 ms backbone3-cgn.surfplanet.de [85.88.0.38]
15 160 ms 181 ms * 85.88.2.200
16 185 ms 183 ms 177 ms 85.88.2.200
Trace complete.

The IP blocklist capability is now working in the LimeWire 4.13.0 Beta.
Just drop the Fullsize Hostiles List into your .limewire folder.

I've had 85.88.2.193-85.88.2.255 blocked since a major spammer moved there in
November of 2005.