<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA256 <br>
<br>
<br>
<br>
14.08.2016 3:59, Vito A. Smaldino пишет:<br>
<span style="white-space: pre;">><br>
><br>
> 2016-08-13 23:31 GMT+02:00 Yuri Voinov <<a class="moz-txt-link-abbreviated" href="mailto:yvoinov@gmail.com">yvoinov@gmail.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:yvoinov@gmail.com"><mailto:yvoinov@gmail.com></a>>:<br>
><br>
><br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA256<br>
> <br>
> I suggests you lost of op point. He is talking about
anonimity, not about rotating outgoing IP's.<br>
><br>
><br>
> I found only 1 mex from james82 (i'm missing something?) and
he didn't wrote about anonimity.</span><br>
By the way, we do not know what the devil wants op. He gives us a
whole month for a ride, without disclosing what the heck wants to
achieve.<br>
<span style="white-space: pre;">><br>
> The tutorial doesn't deal with rotating IPs or load balancing
(not only), it deals with routing the http requests through
different ISPs (or IPs) based on the net of the client generating
the request. In my case, the goal is to make sure that
administration net and dida net route using 2 different public IP,
using a unique squid proxy.<br>
><br>
> A similar approach could be used for a route based on the
destination website.<br>
><br>
> V</span><br>
<br>
-----BEGIN PGP SIGNATURE-----
<br>
Version: GnuPG v2
<br>
<br>
iQEcBAEBCAAGBQJXr5oyAAoJENNXIZxhPexGZVEIAMXtNhucRzhdwiDMtRKsQN3c
<br>
9CVF//6JDNAtmXcEnUHRlpZw6mFweqMLm1bxkFo9H2EgpbVmqSaMEPMRZDzAmjMS
<br>
eSW0KwKkFuOs7inw3fG0QO1IzGCGVfL+1P1T8QPXhHVhVsi9P/1HnDm7aNB3g2ID
<br>
k3IdOEiWyxA97r2hNqMDWSJ8N2Kr/897NCf3Qk17Y8IsNjDT+GUmDZ3UmhE8CNSp
<br>
BtRYXbPar1dOX3NNT3ePZVkIPP5eJO6eXFLbPAsrQ79yH6FG+4dFcpRrSDvxn/lw
<br>
lHRhywIlM17D1vJhBhSCMsHPq7/KSN8pCMLpJDAeSdY23g6VKut9MIRrfwNCUSs=
<br>
=4Y5Y
<br>
-----END PGP SIGNATURE-----
<br>
<br>
</body>
</html>