I've been doing a little experimenting to counter-act comcast's anti-bittorrent practices, or the fact that they impersonate your computer to cut connections so they can be jews and not have to upgrade their network.I've discovered on the web that there's supposedly three different ways to get around sandvine:1. the new Azureus has something called "RC4" encryption, that while it takes more CPU power, can get around sandvine2. using a firewall program such as ipfilter or something along those lines, you can choose to block TCP RST flags on the ports that bit torrent is using.3. get a shell account on a network outside of comcast (such as silenceisdefeat.org), and set up a SOCKS proxy and route all your bit torrent traffic through the proxy. (I.E. SSH/VPN tunnel)Thus far I've tried method 1, installing azureus. Even though I hate java and this torrent client is a thousand times more bloated the utorrent, this method works -- somewhat. I can seed but my upload caps out at around 18-20 kbps. better than the 0-.1 kbps I was getting while I was encrypting utorrent traffic, but nowhere near where it use to be.Method 3 sounds like a sure fire way to do it, but I haven't tried because to set up an account on silenceisdefeat they require either you mail them a form and a stamp and wait for them to process it, or fill it out online using a verified paypal account. I have no experience with paypal, but adding my bank account number and routing number to an online database is nothing I want to do right now. I'd end up mailing the form to them.method 2 sounds like a good way to go, but I don't know what ports I should be blocking RST flags on. Do I block on ports 6881-6889 for actual bit torrent connections, the bit torrent listening port, or both? Halp plz.TL;DRHow does I set up TCP RST blocking for bittorrent?in b4 switch ISPs, an hero, stop pirating, etc. There's no other broadband ISP in my area.
bump