dj_maxx Posted September 18, 2007 Report Share Posted September 18, 2007 BUG Description: After updating ipfilter and reloading it using "Reload IPFilter" menu or Options dialog, existing connections (allowed by old ipfilter, but blacklisted by new ipfilter) do not terminate.Reproduce: start downloading or seeding with some ipfilter applied or without it, remember one of peer's IPs, add this IP to ipfilter.dat and reload filter. Banned peer will not disconnect.Affected versions: All known. Link to comment Share on other sites More sharing options...
Switeck Posted September 18, 2007 Report Share Posted September 18, 2007 I've been told that is how it's designed -- to block NEW connections using ipfilter.dat but not break existing connections if you make changes to ipfilter.dat.I use TCP view to break connections if/when I need to....mainly to close out the half-open, totally dead connections. Link to comment Share on other sites More sharing options...
dj_maxx Posted September 19, 2007 Author Report Share Posted September 19, 2007 I've been told that is how it's designed -- to block NEW connections using ipfilter.dat but not break existing connections if you make changes to ipfilter.dat.But, I think, this is incorrect. For example, my ISP has a list of networks (~1700), to/from which traffic is free. Traffic to other (World) networks is very expensive. This network list changes every hour (added new subnets, removed some old, due to routing issues). So, after reloading filter, some peers may be "World", and they will not disconnect, and will continue consuming of expensive world traffic. Restarting uTorrent after every update is not a solution, as this will interrupt all active transfers and initiate new peer discovery.This is common situation for Ukraine, Baltic countries, Russia, and maybe some others.Upd: after hour of testing I discovered, that some banned connections are reset after reloading filter (but not all). After several consecutive reloads all banned connections are broken. Some unstability... Link to comment Share on other sites More sharing options...
µtorrent-Guest Posted September 19, 2007 Report Share Posted September 19, 2007 @ switeck if i remember correctly the non breaking of the conns where changed in the 1.7 version. µTso µT will break existing connections once you choose "reload IP filter". However if you add a big number of new IPs that are currently connected. I can confirm that µT sometime "forgets" to kill some after the first time pressing reload. (4 times hitting reloading here was the highest count once to get rid of even the last of about 300 BCs I added once) Link to comment Share on other sites More sharing options...
dj_maxx Posted September 19, 2007 Author Report Share Posted September 19, 2007 So, it's definitely a bug... Link to comment Share on other sites More sharing options...
Switeck Posted September 19, 2007 Report Share Posted September 19, 2007 ...sounds like it. Link to comment Share on other sites More sharing options...
Firon Posted September 19, 2007 Report Share Posted September 19, 2007 Thanks for the report. Link to comment Share on other sites More sharing options...
Firon Posted November 23, 2007 Report Share Posted November 23, 2007 Can someone confirm if this still happens with the latest 1.8 alpha? (see the announcements forum) Link to comment Share on other sites More sharing options...
Ultima Posted November 23, 2007 Report Share Posted November 23, 2007 I can't. I just tested it on a random peer's IP (poor guinea pig peer... ;D), and the peer got disconnected immediately after µTorrent loaded ipfilter.dat. Link to comment Share on other sites More sharing options...
Firon Posted November 23, 2007 Report Share Posted November 23, 2007 Well, there was another bug where it seemed like it wouldn't reset all blocked connections if you added large amounts of IPs to the list. Link to comment Share on other sites More sharing options...
dj_maxx Posted January 7, 2008 Author Report Share Posted January 7, 2008 Hmm... i have tested today version utorrent-1.8-alpha-7593.upx.exeBug is still present, behaviour absolutely same.Initially was 100 peers, after first "Reload IPFilter" 50, after second - 20 ....After five reloads all peers disappeared.PS: ipfilter.dat has 860 entries Link to comment Share on other sites More sharing options...
Ultima Posted January 7, 2008 Report Share Posted January 7, 2008 I still can't confirm the behavior. I just selected 5 random peers I was connected to, added their IPs to ipfilter.dat, and reloaded ipfilter.dat. Those peers -- and those peers only -- got disconnected immediately. Link to comment Share on other sites More sharing options...
Greg Hazel Posted January 7, 2008 Report Share Posted January 7, 2008 Hmm... i have tested today version utorrent-1.8-alpha-7593.upx.exeBug is still present, behaviour absolutely same.Initially was 100 peers, after first "Reload IPFilter" 50, after second - 20 ....After five reloads all peers disappeared.PS: ipfilter.dat has 860 entriesWhat does the log say? Does "Loaded ipfilter.dat (N entries)" say the correct number? Is it possible the peer connections that are not dropped were currently being made? Link to comment Share on other sites More sharing options...
dj_maxx Posted January 9, 2008 Author Report Share Posted January 9, 2008 What does the log say? Does "Loaded ipfilter.dat (N entries)" say the correct number?Yes, the number is correct each time.Is it possible the peer connections that are not dropped were currently being made?No, there are established connections too. Link to comment Share on other sites More sharing options...
jewelisheaven Posted January 18, 2008 Report Share Posted January 18, 2008 It disconnects on all 1.8 versions I tested... What version are you reporting this on specifically. Link to comment Share on other sites More sharing options...
Switeck Posted January 18, 2008 Report Share Posted January 18, 2008 I've also had problems disconnecting more than 5 ips at once using a modified ipfilter.dat in the v1.8 alpha series.I was doing it as a complex series of tests against ComCast's disruption schemes, I was trying to disconnect seeds when I was in 99.8% "seeding" mode. Link to comment Share on other sites More sharing options...
Greg Hazel Posted April 30, 2008 Report Share Posted April 30, 2008 Fixed for the next 1.8 Beta (> 9407). Thanks everyone! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.