Tom Eastep wrote: > > 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. >
In my case, I'm running Asureus on a system that uses one-to-one NAT to 206.124.146.178. I use a transparent proxy whose local IP address is 206.124.146.176. I have worked around the problem by adding the Azureus address block (81.19.16.0/21) to the exclusion list in my REDIRECT rule. YMMV, -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
