tracker blocked by ip filter

[flasher360]

hi

first of all: i love deluge

but i have a problem:
my most loved tracker is being blocked by ip filter.
i already switched from the ipfilter.dat to level1.zip from bluetrack - but it's still blocked.

so i pinged the tracker to get its ip.
then i looked into the ip filter list and mhm... the pinged ip address isn't in any of the ranges?!

that's why i am unable to connect to any other peers.
it says "keine ankommenden verbindungen" (i'm from germany ^^) - something like "no incoming connections".

it would be a nice feature if it would be possible to make a button like "exclude tracker (ip) from ip filter list".
i mean a button to unban a specific ip adress - whether with manual ip input or just to exclude the used tracker ip like described above.

and like the faq suggested:
* Deluge Version: 1.3.0
* Libtorrent Version: 0.15.4.0
* Operating System: Ubuntu 10.10
* Plugins Enabled: ip filter (bannlist)
* GTK
* Filesystem: ext4 and ntfs
* Installation Type: download from website (package)

thanks in advance and greetings from germany!
keep up the excellent work!
flasher360

[flasher360]

*bump*

developers' opinion?
is it possible?
will a exclude or unban ip input-box come to deluge?

greez (:

[johnnyg]

It shouldn't happen, but it's entirely possible.
In fact, I suspect it might be related to this bug: http://forum.deluge-torrent.org/viewtop ... =9&t=25695

That said, the easiest way to double check would be to run deluge with debug logging enabled
and look for "blocked by ip filter" (that's the error you should get if your tracker is being blocked by the ip filter).

If you see the above message any chance you could tell me which ip it is?
Just want to double check that it's definitely not in the list...

The idea of being able to override the blocklist could be a useful feature

[flasher360]

hi and thank you for your answer!

the debug-mode says following:
"[DEBUG ] 19:26:07 alertmanager:123 tracker_error_alert: #TORRENT_NAME_REPLACED# (http://#TRACKER_ANNOUNCEMENT_HOSTNAME_REPLACED#) (-1) blocked by IP filter (2)

i pinged the address and found out:
the ip is in the range of 85.17.92.xxx

i opened the ipfilter list (level1) and searched for this range.
and as far as i can see the ip from above isn't in any of those blocked ranges.

when i click on a torrent in deluge there is a field named "tracker status".
till the last update and without ipfilter it says "announcement ok".
when i activate the ipfilter it says "blocked by IP filter" there.

as said before:
a button for unbanning the tracker-ip would be cool.
an input-mask for ip-addresses or -ranges would be even cooler. (:

[flasher360]

but it's really strange right now.

i have a few torrents from the same tracker.
9 out of 10 torrents say in this tracker status field "blocked by ip filter".
but one torrent says "announcement ok".

ehm... i don't understand?!
it's always the same announce-url used.
why is it blocked 9 times and once not? ^^

[johnnyg]

It's possible that the last torrent announced before the blocklist was loaded, hence why it's announce is still OK.

Looking through http://bluetack.co.uk/config/level1.zip, I see on line 112556:

Code: Select all

LeaseWeb:85.17.80.249-85.17.93.2

which looks like it would be blocking 85.17.92.xxx

But you originally said it was blocking it with http://bluetack.co.uk/config/nipfilter.dat.gz?
Which doesn't have the address within one of its ranges.

Could you try nipfilter.dat.gz again but restart deluge (or deluged if you are using it) after switching?
When you import a new blocklist, it actually adds the new ips to the previously loadeed ones.
The only way to clear it at the moment is by restarting deluge(d).

[flasher360]

i guess i'm blind... ^^

that's weired.
i switched the list because my announcement url was blocked.
but i did what you said and switched (back) to the list at the url you mentioned above.
now it works.
"announcement ok".

thanks!

but... a unban-method would still be very nice to have.

[johnnyg]

but... a unban-method would still be very nice to have.

yeah it would.
libtorrent supports both black and white lists, so it would just be a matter of implementing it in deluge (i.e. in the blocklist plugin).

Feel free to create a ticket for Deluge 1.4.

[flasher360]

one last question before creating a ticket:

what happens if an IP is in both lists?
does the whitelist override the blacklist? or vice versa?
or will the world implode? ^^

[johnnyg]

what happens if an IP is in both lists?
does the whitelist override the blacklist? or vice versa?
or will the world implode? ^^

Not sure. Hopefully the world won't implode
I will have to double check, but I suspect whichever is added last will override the other.