I Guess This is The End 4 Me…

[bugmenot69]

Have you tried forcing encryption in your torrent client?

[raphjd]

Encryption doesn't help with this issue, but it helps in most cases.

[trukr]

@Jake:

Linux usesr seem to say they have the solution by blocking the reset packets. "iptables -A INPUT -p tcp –dport $TORRENT_CLIENT_PORT –tcp-flags RST RST -j DROP" Maybe setting up a linux machine for torrents?

Here is a windows ipfw i found in a thread, can't remember where now, that may work.
hxxp://wipfw.sourceforge.net/

one user is claiming to have success with this method.
hxxp://forum.utorrent.com/viewtopic.php?pid=271211#p271211
read the few posts below it too.

[thomascuhna]

I have Comcast and can seed. The speeds are not what they should be but not too bad, around 79kbps

[raphjd]

@thomascuhna:

I have Comcast and can seed. The speeds are not what they should be but not too bad, around 79kbps

It depends on which area you are in. ComCast is rolling out this anti P2P software to it's various markets, so not everyone has it yet.

[Chris4u19]

sorry i haven't posted in a while i was busy but…i read up on it and the code for linux users won't work for me due to the fact that i use windows lol...but i downloaded a new torrent (µTorrent) and i downloaded a wipfw so hopefully this works i will hopefully have happy news in the next couple of hours or less but ill tell you what happens ok here i go...

[Chris4u19]

@trukr:

@Jake:

Linux usesr seem to say they have the solution by blocking the reset packets. "iptables -A INPUT -p tcp –dport $TORRENT_CLIENT_PORT –tcp-flags RST RST -j DROP" Maybe setting up a linux machine for torrents?

Here is a windows ipfw i found in a thread, can't remember where now, that may work.
hxxp://wipfw.sourceforge.net/

one user is claiming to have success with this method.
hxxp://forum.utorrent.com/viewtopic.php?pid=271211#p271211
read the few posts below it too.

thanks for the help…btw i lol'd @ ur avatar

Edit: i have no idea how to use wipfw...haha please explain or give me a link to explain what it does and how to use it lol i was thinking it would be a program with an interface or something...im so lost with this program lmao i know how to look at the logs and i know i can allow and deny certain things but i have no clues how to...
i need a wipfw for dummies!

[Chris4u19]

so with my new torrent and the encryption option my seeding is acting weird…it lets me seed at a max of 98 kb/s and fluctuates from there lower and higher and then stops and then starts again sporadically...hmm hopefully i can fix it and make it more stable...

Edit: i tryed changing the ports and it seems to help out its still seeding weird but it is more stable
...at least its seeding now!

this is the graph from my torrent...you can see the uploading isn't 100% stable

Edit: so i turned my torrent off and i turned it back on a couple hours later and it's not working as good now its going up and down in stead of trying to stay up…also changing the ports apperanty can give you a worm...i changed the port to 60000 and the worm deepthroat trojan or something like that tryed to get me luckly Nortan Antivirus stopped it...Hmm

[trukr]

here is a link to the GUI frontend for wipfw.
xttp://sourceforge.net/project/showfiles.php?group_id=113599&package_id=142484

i never bothered much with command line firewalls but try this.
in the command "iptables -A INPUT -p tcp –dport $TORRENT_CLIENT_PORT –tcp-flags RST RST -j DROP"
, you did enter your torrent client port right?
example: "iptables -A INPUT -p tcp –dport $60000 –tcp-flags RST RST -j DROP"
try entering that into the command line with the port you want to use.
then use the GUI to open your bittorrent port.

port 60000 is one of the the ports DeepThroat uses, may be a false positive.

hope that helps, good luck.

[F00F]

Norton might be stupid and assume that anything that access that specific port is the trojan.

iptables -A INPUT -p tcp –dport 60000 --tcp-flags RST RST -j DROP
Should work better.

[trukr]

@F00F:

Norton might be stupid and assume that anything that access that specific port is the trojan.

iptables -A INPUT -p tcp –dport 60000 --tcp-flags RST RST -j DROP
Should work better.

thanks F00F!

whoops…copy/pasted the wrong stuff and didn't think much about what was in that line, wasn't really sure what a couple of those commands were anyhow.
like i said i don't use terminal/command line often, hardly ever, and don't remember much from when i did use it.
sorry Chris4u19.
iptables -A INPUT -p tcp --dport 60000 --tcp-flags RST RST -j DROP
ya...lol, that should work better without all the extra garbage i posted. :lol:

i thought exactly the same thing about norton because as soon as Chris tried to use port 60000, it sent an alert.

i really hope this works for you Chris4u19.