The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
how to get peerguardian to play nice with utorrent?
Utorrent has its own built in IP filtering, you don't need to use Peerguardian at all.
In fact utorrent's filtering is a better choice, since it prevents questionable connections before they happen. But, the connection has to be made before peerguardian can cut it off.
I don't like this solution because it doesnt self update like PeerGuardian does on every startup
So back to the problem
How to get PG to not block the port utorrent is configured to use
Sigh. Then get a program that automatically updates your IP filter. The people who make the ipfilter list make an updater.
Let me make the real issue here more clear.
PeerGuardian doesn't work.
By the time peerguardian can detect and disconnect, the connection is already made, your IP is already seen. I'm pressuring you to use the internal utorrent method for your own good. It works. Even if you never update it, set the list up once and you have better protection thatn peerguardian can ever give you.
I know that's not the answer you were looking for, but it's the answer you need to hear.
EDIT: Also, I'm failing to see (from a technical standpoint) how the filtering that uTorrent does is or can be any better than what PG does.
PeerGuardian disconnects you from dangerous IPs after the connection has already been made. All it does is reduce the window of time in which you can be identified.
Utorrent filtering avoids making these connections in the first place.
Or let's put it this way:
If you're being watched, your ass is already busted by the time peerguardian kicks in. It's too slow. It's reactive, not proactive.
EDIT: Also, I'm failing to see (from a technical standpoint) how the filtering that uTorrent does is or can be any better than what PG does.
PeerGuardian disconnects you from dangerous IPs after the connection has already been made. All it does is reduce the window of time in which you can be identified.
Utorrent filtering avoids making these connections in the first place.
Or let's put it this way:
If you're being watched, your ass is already busted by the time peerguardian kicks in. It's too slow. It's reactive, not proactive.
And again, I'm looking for a more technical explanation of how this works (especially regarding incoming connections, which uploads are). The link you gave obviously doesn't go into it. I'm not seeing how uTorrent can manage to mask you that much more effective than PG, especially since IIRC merely being present on the tracker for the file is considered evidence now (and it certainly can't mask that).
Yeah, I'd like to see a more substantial explanation of why Peerguardian is supposedly slower. PG blocks at the kernel level.
I don't think PG blocks the way he say it does. An easy way to see is to get a filter that blocks http ad sites. Sites like IGN will not even start to connect.
I'm pretty sure when I ran PG that yes, the color of the status icon went to yellow (in addition to the already mentioned failing the built-in check port test)
Like mcdermott said, ignore the built-in Utorrent port test. All that does is try to connect to the Utorrent server on the port you specify. Depending on what lists you are using with Peerguardian, it is probably being blocked. A lot of the list managers started blocking Utorrent when it was taken over by the main Bittorrent guy because they were afraid of potential connections to the **AAs.
If you want, you can allow that IP address permanently. Just try the port test, and if Peerguardian shows something like "BittorrentInc" blocked, right-click the IP and select "Allow permanently."
And like mcdermott also said, depending on how well seeded the torrent is and how strict the lists you're using are (i.e. blocking college IPs), it might take a minute for a torrent to go from yellow to green.
Posts
In fact utorrent's filtering is a better choice, since it prevents questionable connections before they happen. But, the connection has to be made before peerguardian can cut it off.
http://www.zeropaid.com/news/6443/IP+filtering+with+uTorrent
So back to the problem
How to get PG to not block the port utorrent is configured to use
Let me make the real issue here more clear.
PeerGuardian doesn't work.
By the time peerguardian can detect and disconnect, the connection is already made, your IP is already seen. I'm pressuring you to use the internal utorrent method for your own good. It works. Even if you never update it, set the list up once and you have better protection thatn peerguardian can ever give you.
I know that's not the answer you were looking for, but it's the answer you need to hear.
Utorrent filtering avoids making these connections in the first place.
Or let's put it this way:
If you're being watched, your ass is already busted by the time peerguardian kicks in. It's too slow. It's reactive, not proactive.
run peerguardian? (which is apparently the same list that this other method uses) or go filter-less or what?
Yeah, I'd like to see a more substantial explanation of why Peerguardian is supposedly slower. PG blocks at the kernel level.
I don't think PG blocks the way he say it does. An easy way to see is to get a filter that blocks http ad sites. Sites like IGN will not even start to connect.
If you want, you can allow that IP address permanently. Just try the port test, and if Peerguardian shows something like "BittorrentInc" blocked, right-click the IP and select "Allow permanently."
And like mcdermott also said, depending on how well seeded the torrent is and how strict the lists you're using are (i.e. blocking college IPs), it might take a minute for a torrent to go from yellow to green.