Andrew Suffield wrote: > > I haven't studied the matter closely, but my understanding is that > most clients notice that their inbound path is broken, and simply > start making connections to other peers at random and then try to send > them stuff. On an active torrent, they won't take long to find > something to upload. >
I've been playing with this thing and have found one anomaly in the Azureus NAT/Firewall test. The Azureus client first establishes an HTTP connection (port 80) to a remote host. The remote host then attempts to establish a TCP connection back the the originator of the HTTP connection. This of course can go stupidly wrong if there is an HTTP proxy. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
