OK so the next step is:
Routing over tunnel to the other proxy and on it(which has ssl-bump)
intercept.
If you have a public on the remote proxies which can use ssl-bump then route
the traffic to there using Policy Based routing.
You can selectively route by source or destination IP addresses.
Now
Hello,
yes I have full control of all three proxies, both local proxies and
remote proxy; and in my LAN I use static IP addresses;
cache_peer_access remote-proxy allow remote-domains <-- this is
neccessary because a few domains
OK so first you need to make sure you know and understand what you define as
"The Internet is Down''.
How do you recognize that the connection is down?
If the proxy is the gateway and it has the interface up or down it would be
easy to script it.
There are other ways which uses "ping" checks and
A question that will simplify things:
Are you full in control of the remote and the local proxy?
If so you can create a tunnel from the local gateway to the remote squid and
pass the web traffic in the routing level.
This way you would be able to intercept port 80 on the remote proxy and if
require
On 2016-11-27 19:44, piequiex wrote:
> In cache.log I have found "assertion failed: support.cc:1781: "0""
> Squid Cache: Version 3.5.22
AIUI, your Squid binary was build against buggy openssl library
(1.0.1d or
1.0.1e). How did you get the binary?
I build them with libressl.
The configure
Hello,
I've got a special problem ...
I have several devices in my LAN:
- PCs, Notebooks
- a Tablet-PC
- a Smartphone
- a Television
on my LAN I've two squids as VMs on my PC
(both are CentOS 6)
I also have a virtual server (a CentOS 6, too) at a webhoster in a
different country,
which I hav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> On 2016-11-26 22:28, piequiex wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > In cache.log I have found "assertion failed: support.cc:1781: "0""
> > Squid Cache: Version 3.5.22
>
> AIUI, your Squid binary was build against bugg
