Blocklist working?

[mp3geek]

How do you know if the blocklist is actually working? I'm grabbing many popular torrents and the padlock on the bottom still shows "0", would nice to see a console log inside deluge to show its realtime blocking..

[johnnyg]

the padlock showing 0 means you don't have any blocked ips.
try forcing a download/import.

[danii]

How do you know if the blocklist is actually working? I'm grabbing many popular torrents and the padlock on the bottom still shows "0", would nice to see a console log inside deluge to show its realtime blocking..

as johnnyg said first you have to make sure ou have imported the blocklist, to check if deluge is currently blocking IPs you must start deluged with:

Code: Select all

deluged -L debug

I don't know if the other levels of logging like info, warning, error, critical show blocked IP's so I chose debug to be sure, then to actually see if deluge is blocking anything:

Code: Select all

tail -f ~/.config/deluge/deluged.log|grep peer_blocked_alert

finally I agree that some sort of console log would be nice and I also think some option to enable/disable logging inside the UIs would be usefull

[Aqualung]

Yeah, I think mp3geek is right: the blocklist isn't really working. It does look like it imports and loads the blocklist, but the padlock still shows 0 no matter what.

Running Deluge daemon on a headless device, controlled via a Vista x86-based remote client.

[johnnyg]

• Close deluge(d)
• Go to deluge's settings folder (http://dev.deluge-torrent.org/wiki/Faq# ... tssettings)
• Delete blocklist.cache and blocklist.conf
• Start deluge(d)

that should normally fix the problem.

what I don't understand is that if the blocklist is corrupted a force download/import should fix it.

[Aqualung]

that should normally fix the problem.

Myeah, sorry, it doesn't. Padlock @ 0 no matter what.

Again, it may be this particular setup (headless Airlive WMU-6500FS device controlled from a Vista x64 client) that gives this sort of trouble. This is a rather thin device I must say.

Btw, which one of the 5 blocklist options should I choose?

[johnnyg]

if you're using nipfilter.dat.gz on deluge's server then you should have emule ip list selected as type.
if you run the daemon with logging enabled (with debug info), it should give you a clue into why it's not importing.
It could also be a bug with the GTK UI in Vista; if you're running the web ui, could you see if that shows any blocked ips?

[Aqualung]

if you're using nipfilter.dat.gz on deluge's server then you should have emule ip list selected as type.

Yeah, that did it, thanks!
How was I supposed to know that though? Is that written somewhere in the Wiki, FAQs etc? I must have missed it then.

[johnnyg]

isn't it selected by default?
It's kinda implied in the faq: http://dev.deluge-torrent.org/wiki/Faq# ... erGuardian

maybe the blocklist should display an error message when the import fails (although this is present in the debug logs).

[Aqualung]

isn't it selected by default?

Is it? I don't recall, frankly.

It's kinda implied in the faq: http://dev.deluge-torrent.org/wiki/Faq# ... erGuardian

I can't really make that out from the FAQs, sorry. It wouldn't hurt making it more explicit though. I, for one, couldn't tell.

maybe the blocklist should display an error message when the import fails (although this is present in the debug logs).

Yes it should. Funny thing is that I had PeerGuardian Text (Uncompressed) selected, and it prima facie looked as if the list did get imported, so I didn't worry too much--that is, until I saw this thread, which got me thinking.

At any rate, It wouldn't hut to get someone to rewrite the relevant FAQ in a bit more explicit manner. The way it is right now is, really, way too cryptic.