Re:"Transparent" proxies (Score 1)

Short answer: Use the --ip x.x.x.x option Long answer: My internal network uses the private ip space of 192.168.1.0/24. The firewall/router NATs the private IPs to a single IP address (for DSL users this may be dynamically assigned each time). We have a very tight firewall so I had to allow new connections out on 6969 and all connections on 6881-6889. New connections to the public IP address had to be forwarded to the private computer running bittorrent. Finally, when running btdownloadcurses.py I had to specify --ip x.x.x.x where x.x.x.x is the public IP address everyone else sees. Else, BT used my private IP which doesn't do anyone any good. btdownloadcurses.py --ip pub.lic.ip.add --minport 6881 --maxport 6889 --max_upload_rate 100 my.torrent The transparent proxy could cause you troubles if the IP is not the same as your router IP. Often I check for transparent IP servers by going to http://www.grc.com. Steve Gibson has the useful ShieldsUp! tool that among other things probes your common ports. It will tell you exactly what IP address it sees you surfing with. If it is different than your router or your PC than there may be a proxy between you an grc.com. How do you bypass a transparent proxy you don't control?