Descripción: Trabajo de configuracion de un servidor squid
squidDescripción completa
trabajo del magnetometro de Squid
Descrição completa
Descrição completa
Descripción completa
MikrotikFull description
Descripción: configuracion Pfsense + squid
Squid proxy server configuration guide.Full description
modul
Descrição completa
Descripción completa
Manual de Configuração Squid - SquidGuard No PfsenseDescrição completa
Heitor de Souza Ganzeli - Analista de Projetos - CEPTRO.BR - Nic.brDescrição completa
Descrição completa
Descripción: CONFIGURACION DE UN PROXI SQUID
Descripción: Limitar Ancho de Banda Con Squid
Descrição completa
Procedimiento de instalación de una herramienta que se encarga de desplegar de forma adecuada el log de acceso al servidor proxy Squid, es muy sencilla de instalar y sobre todo muy útil, a u…Descripción completa
SQUID server with multiple Internet sources In this document I will try to explain how to use multiple internet links from two ISP on the same squid server , assuming running Linux 2. kernel. In the following scenario I will assume you have two links from two ISP assigned to the same linux !ox on eth" # eth$ %
-ote that we have only one default gateway which is $&2.$'.".$ through which all of our outoing traffic goes to , now we need to add another gateway to the system , !ut without affecting the default one.
In the following steps we will create new routing ta!le for our second link on $)2.$.".$" and route traffic originating from this ip through $)2.$.".$ echo “1 isp2” >> /etc/iproute2/rt_tables ip route add 172.16.0.0/24 dev eth1 src 172.16.0.10 table isp2 ip route add default via 172.16.0.1 dev eth1 table isp2 ip rule add from 172.16.0.10/24 table isp2 ip rule add to 172.16.0.10/24 table isp2
-ow we are doing with IP routing stuff , to test that your routing ta!le is working pro!a!ly try doing traceroute using each interface at a time % #traceroute -i eth0 8.8.8.8 1 192.168.0.1 (192.168.0.1) 0.356 ms 0.486 ms 0.513 ms 2 xxx.xx.xxx.x (xxx.xx.xxx.x) 1.813 ms 2.365 ms 2.356 ms 3 84-235-111-9.igw.com.sa (84.235.111.9) 26.949 ms 26.948 ms
27.184 ms
#traceroute -i eth1 8.8.8.8 1 172.16.0.1 (172.16.0.1) 1.046 ms 1.207 ms 1.898 ms 2 10.0.1.1 (10.0.1.1) 5.602 ms 5.605 ms 5.743 ms 3 79.133.88.13 (79.133.88.13) 104.516 ms 104.555 ms 104.850 ms
-ow we are done with routing , let+s me to squid.conf
-ow we have three clients using our squid server , we want to map them to different outoing ip addresses %
$".".".2 / $&2.$'.".2 $".".".( / $)2.$.".2 $".".".0 / $)2.$.".2 1s you see , requests from $".".".2 must go through $&2.$'.".2 and others go through $)2.$.".2. In squid.conf add %
In case you want to do some load !alancing inside linux and let it to decide which route each request goes to , you can skip the a!ove squid changes and run the following in your linux shell % ip route add default scope global nexthop via 192.168.0.2 dev eth0 weight 1 nexthop via 172.16.0.2 dev eth1 weight 1
he a!ove code will allow you to distri!ute traffic among your two gateways , and we can prefer one over the other !y changing its weight value.