Dave Platt wrote:

In article ,
Tom Ring wrote:


What client are you using? Are you behind some sort of NAT gateway or
other firewall?


TorrentStorm, behind a NAT, but that has never been an issue before.


The documentation at BitTorrent.com points out that downloads may not
work, or may be quite slow, if you're behind a NAT and don't arrange
for port forwarding of inbound connections from your peers. In this
situation, you can end up being unable to exchange data with some or
all of the peer sites you try to connect with.

As I understand it, this shouldn't affect the seeder I'm running,
since it already has a complete copy of the file and doesn't insist on
a tit-for-tat exchange of data. However, it's possible that there may
still be some issues, with some NATs or firewalls.

Both my tracker, and my seeder clients, use the BitTorrent 4.01
reference implementation, and neither is behind a NAT. I've been able
to transfer successfully from a system here at work which *is* behind
a NAT, and the transfer went quite efficiently. So, it's possible
that the problem lies at your end, although that's not a certainty.

My system _does_ react rather strongly, in defense, against systems
which appear to be trying to port-scan it for vulnerabilities or
trojans... it'll slap down a hard IP filter against such systems and
will appear to "vanish" from the net.


Thanks for the response. I don't think I have a problem with the
network side, since I forward the torrent port to that box, and my ACL
allows that port to see all public addresses. I have a Cisco IOS DSL
router running the latest release, so I have a bit more flexibility than
most. I'll give it another shot tonight.

tom
K0TAR