Guliver:

Hi all,

I am a newbie to all this I have recently added the TBG Bogon list to perrblock 1.0 and have noticed this 239.255.255.250 is constantly being blocked. I have checked google an found it is mainly a multicast address to do with windows. I am after some advice as to wether or not I should allow this IP?

Also since running peerblock with the lists below I have noticed that Vuze 4.5 taked long to establish the DHT database is this normal?

I am running the following lists
Anti-infrigement, Allow P2P,spammers, hacker, logmein, hijacked, TBG primary threats, level 2, the pirate bay bad peers list, bad peers, blue track dshield

I hope this makes sense. Any advice wouyld be greatly appreciated.

Guliver

fakhir (I-Blocklist - General Manager):

Most home users dont need to block bogon ranges.

If DHT is blocked then you can allow those IPs.

Guliver:

Hi Fakhir

Thanks for the reply I am not sure that the DHT IP is actually blocked as such, I does connect eventually. Peerblock seems to be blocking various HTTP connections at this time mainly the Quantcast-1, Amazon EC2 cloud and a Savvis-1 connection. I assume Vuze is trying to access these for the DHT info. I am not sure if I should allow these as it may create a hole once the DHT in established. I think this maybe a question more for the Peerblock forum, I just raised it here to if anyone had seen this before.

Thanks again.

Guliver

mwestfall:

*sigh* there is no such thing as a DHT 'server' that's the whole point.

The reason its taking a while for your 'DHT' to 'connect' is because until you actually connect to someone who has some 'DHT' information you won't have any 'DHT' information or be part of anyone else's 'DHT' information.

read:

http://en.wikipedia.org/wiki/BitTorrent_%28protocol%29