XDCCCatcher.net

Thanks for reporting. Can you just let me know which filtering was enabled?
I'm currently testing the filtering on bots and can't simulate this particular issue.
Was the filter enabled using a 'Search on Bot', 'Channel' or 'Network' as i just fixed an issue there with the autorefresh.

Thanks!

Hi,

The Bot in the 1stt and 3rd example is sending its local ip (192.168.x.x) instead of his/her public ip.

The second bot i'll do a test myself.

Thanks. Can you also check the folder in which you installed Catcher? There should be a file called debug.log. Can you find the lines related to those reversed xdcc transfers? I’m interested to see which ip and port the bots were sending over.
Thanks!

Can you see if after a resfresh, the correct filter is applied? So, you changed the filter parameters and you click on the big 'Filter' button correct? Only when you click on that button, the filter will be updated and refreshed. When you wanted filtering, at the top it said "Filter (enabled)&q...

i'm going through the searchfilter code to find what might be causing this.

So if i understood correctly, you entered the search filter and clicked on 'filter' and all of the packs just kept on being displayed?

Can you please post the error you get related to reverse xdcc?

Did you modify the search filter after you clicked on 'search' ?
The autorefresh will use the filter param as they were when you click on search. When you make any changes after this, you'll have to restart the search. I'm still thinking about a better way to implement this.

Hello,

Sorry, there are no plans to make a mobile phone version of xdcccatcher (ios, android, ...)

balduz

Today we released v3.0.0.12 BASIC

Hi,

Can you please download Basic version 3.0.0.12 which was released today?
This should normally fix any problems.

Thanks!