ipfilter.dat not used correctly

[VWW]

Hi

I have just started implementing ipfiltering in my utorrent and i noticed that it was blocking specific IP's that i had listed in my ipfilter.dat as permit rules. After some experimenting i realised that utorrent seems to only read the IP ranges and blocks them all... it doesnt read whether they are permit or deny rules.

eg:

192.168.000.001 - 192.168.000.001 , 200 , Description - this should be allowed but utorrent blocks it.

192.168.000.002 - 192.168.000.002 , 000 , Description2 - this should be blocked and utorrent correctly blocks it.

I hope this can be resolved soon.

Thanks

V.

[h0rnytoad1]

hi,

i hope talking of an other p2p app isn't forbiden of so, sorry.

i havent used ipfilterring in utorrent yet (don't know how), but i use peergardian2, it blocks all connections to/from my pc before they get to bad ip's.

But, if there was a way to tell utorrent where to get this ipfilter.dat file, either web or folder... (ie: emule downloads it automatically) so utorrent could just use that one or direct from the pawcio website.

like in the advanced options, instead of just true/false, why not use a path (web or folder) or False/no path at all to disable this feature.

here's the url in case the utorrent developpers want to include it :

http://emulepawcio.sourceforge.net/nieuwe_site/Ipfilter_fakes/ipfilter.zip

edit: maybe this should go in suggestions?

hth,

HT

[r00ted]

hornytoad, yours is a suggestion.....the author's post was regarding a bug with the ipfilter.dat format.

As he stated

192.168.000.001 - 192.168.000.001 , 200 , Description - this should be allowed

192.168.000.002 - 192.168.000.002 , 000 , Description2 - this should be blocked and utorrent does block it.

Basically, it's treating the block, and allow toggles the same, as blocks.

On the otehr hand, didn't I read in 1 of ludde's posts, that the ipfilter.dat format is actually

x.x.x.x - x.x.x.x

y.y.y.y - y.y.y.y

a.a.a.a - a.a.a.a

notice, no comment lines, just plain IP address filtering.

[VWW]

Thanks r00ted for your reply.

Yes the author has stated that its just an ip range... but that is going to be confusing to many people considering utorrent therefore does not support the correct ipfilter standard.... i doubt anyone is actually using an ipfilter with only the ranges as most people just download some pre-made emule ipfilter from the web... i know of a couple of pre-made ipfilters that also include quite a few permit ranges, and the people using those with utorrent could be having some trouble.

I know it wouldnt be difficult to implement this change as its just about reading the permit/deny number and doing an IF statement around it. The description can be left out... although it would be nice if it could be displayed in the log whenever a deny takes place

V.

[ludde]

Where is the ipfilter standard?

[VWW]

Here is the best description i can find for it: http://www.emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=142

Considering ipfilter.dat was originally made by the emule team this seems to be the best place to get the description of the standard.

[ludde]

So what happens if you got two entries for a particular IP.. one that blocks, and one that doesn't block?

[VWW]

Good question... personally i have not encountered that problem as i have a correctly sorted and merged ipfilter..... but i would recommend that its blocked rather than permitted. Its really up to the program, either permit or deny rules take priority.... for utorrent i would suggest deny rules should as it gives that warmfuzzy feeling of security

[btarg]

So what happens if you got two entries for a particular IP.. one that blocks, and one that doesn't block?

It should use the first line.... if it first says to block it blocks.... just like firewall rules...

Another thing is that when you add an ip to ipfilter.dat it prevents it from connecting but if it is already connected utorrent doesn´t disconnect the client. The torrent with that peer must be stopped and started to take effect (besides reloading ipfilter).

I´d be nice this to be corrected in next beta...

[TheDude]

So what happens if you got two entries for a particular IP.. one that blocks, and one that doesn't block?

Correct software engineering would be to issue an error message stating that the same address had conflicting entries.

PS While we are talking about error messages, one weird omission in utorrent is a "message" column for the torrents in the torrent list. Putting error messages in "status" does not work since the column is always too narrow - messages should be at the end as the last column, so that they can be long. (eg "no more disk space", "i/o error", "torrent not authorized", etc.)

[avatarl]

I use blocklist manager to make and update my ipfilter.dat for utorrent and its default option is "Permit rules take priority". PeerGuardian works the same way actually, it blocks an IP you don't want it to block, you add an exception, the exception takes priority and allows the IP to connect. And it's pretty logical actually.

I also have PeerGuardian enabled most of the time, but if I disable that, ìTorrents seems to be blocking a decent number of IPs. Maybe you've written some rule that allows an IP you wanted blocked? Or maybe a rule to block IPs x-x1 is not considered because IPs x-x1 belong to a bigger group that is allowed by another rule? Maybe you should check your rules one more time, just to be sure.