[Shorewall-users] Redirect site address for other isp

2009-08-23 Thread Jayme Sanches
Hi, I have a centos 5.3 with shorewall 4.2.10 and transparent squid...(REDIRECT loc3128 tcp 80 - !192.168.1.254) It's working fine with 2 NIC, eth0 - net and eth1 - loc Now I need configure other ISP only for access the system in datacenter - ip 200.XXX.XXX.240 (HTTP and HTTPS)...

Re: [Shorewall-users] Redirect site address for other isp

2009-08-23 Thread Christ Schlacta
sounds like you need ACCEPT+ rules in your rules file. Jayme Sanches wrote: > Hi, > > I have a centos 5.3 with shorewall 4.2.10 and transparent > squid...(REDIRECT loc3128 tcp 80 - !192.168.1.254) > > It's working fine with 2 NIC, eth0 - net and eth1 - loc > > Now I need configur

Re: [Shorewall-users] Redirect site address for other isp

2009-08-23 Thread Tom Eastep
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christ Schlacta wrote: > sounds like you need ACCEPT+ rules in your rules file. Or simply list the data center as an exception in the ORIGINAL DEST column of the REDIRECT rule: e.g., !200.XXX.XXX.240 The Shorewall Squid page should be clear

Re: [Shorewall-users] Redirect site address for other isp

2009-08-23 Thread Jayme Sanches
But de rules are not same for the previous configuration? 2009/8/23 Christ Schlacta > sounds like you need ACCEPT+ rules in your rules file. > > Jayme Sanches wrote: > > Hi, > > > > I have a centos 5.3 with shorewall 4.2.10 and transparent > > squid...(REDIRECT loc3128 tcp 80 - !19

Re: [Shorewall-users] Redirect site address for other isp

2009-08-24 Thread Tom Eastep
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

Re: [Shorewall-users] Redirect site address for other isp

2009-09-10 Thread Jayme Sanches
It's working. The problem was adsl connection. Thanks. 2009/8/23, Tom Eastep : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Christ Schlacta wrote: >> sounds like you need ACCEPT+ rules in your rules file. > > Or simply list the data center as an exception in the ORIGINAL DEST > column of