…but apparently they sent RSTs both ways. And I wouldn’t put it past my ISP to forcibly reset Bittorrent connections either. So I’ve told my firewall to drop BIttorrent TCP packets with the RST bit set. The question is, when will ISPs understand the two fundamentals of the situation, viz. 1) I’ve paid for my bandwidth and I’m entitled to use it, 2) Bittorrent traffic isn’t all about teenagers downloading copyrighted material – what about Linux distributions, game patches, etc?
Related Posts
getting stuff working on Linux
Inspired by ‘s recent wibblings on Linux, I decided it was time to iron out my own wrinkles. So after a very little googling, I was able to get a bunch of stuff working that for one reason or another had broken when I upgraded from Dapper to Edgy. Sound…
port triggering iptables config
I think the relevant iptables commands for port triggering with Bittorrent are: #iptables -t nat -A prerouting_wan -p tcp –dport 6881:6889 -j TRIGGER –trigger-type dnat –trigger-proto tcp –trigger-match 6881 –trigger-relate 6881-6889 This tells the router to do NAT on the packets arriving on the WAN TCP ports 6881 through 6889…
I’m Jaunty
A pretty smooth upgrade – Freeciv(-client-gtk) seemed to barf, so I just uninstalled it. The new Amarok is nice, even if the jaunty version isn’t totally up-to-the-minute. I did have to install phonon-backend-xine though. LLVM is v2.5, hurrah! GHC is still v6.8.2, boo.