Search squid archive

Re: Squid 3.2 NAT+Intercept+tcp_outgoing_address

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nevermind, the problem was a iproute2 rule matching wrong default gateway and mixing tables from two ISPs


Thanks anyway..

El 01/03/2013 16:32, M.C. Rogelio Sevilla Fernandez escribió:
Hi all..

I have a Linux Proxy with 3 physical network cards and 3 different ISPs on each port. This Linux do NATs from my private network and send traffic to each ISP based on Iproute2 rules (ip rule) except for Web traffic. So, im trying making squid to use 'tcp_outgoing_address' to forward traffic from my private clients to
each ISP bases on src ACLs like this:

acl firstprivate src 192.168.1.0/24
acl secondprivate src 192.168.2.0/24

tcp_outgoing_address PUBLIC_IP firstprivate
tcp_outgoing_address SECOND_PUBLIC_IP secondprivate


but some strange things happen.. All traffic its going to my third ISP not defined in squid.conf over any ACL or tcp_outgoing_address rule and this ISP is not my default Gateway..

So, If i dont redirect all Web Traffic (80) to squid, iptables2 rules do their job so well.. but if i use squid and redirect web traffic to it make this strange things..

What do you think is happening?..

Thanks!

--
Este mensaje ha sido analizado por MailScanner del
Gobierno del Estado de Colima en busca de virus y otros
contenidos peligrosos, y se considera que está limpio.



--
Este mensaje ha sido analizado por MailScanner del
Gobierno del Estado de Colima en busca de virus y otros
contenidos peligrosos, y se considera que está limpio.



[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux