Jayme Sanches wrote: > But de rules are not same for the previous configuration?
What is happening is this: - Traffic to 200.xxx.xxx.240:80,443 is being redirected to the proxy. - The proxy tries to connect to 200.xxx.xxx.240. - Your tcrules entry doesn't deal with connections originating on the router; it only deals with traffic being forwarded by the router. - So the connection is being routed out of the wrong interface You can either do as Christ or I have suggested and change your rules file; or you can add a second rule to your tcrules file that marks traffic originating on the firewall ($FW in the SOURCE column). -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
