David.
Thanks for your input, but it's not the proxy changing that is the problem,
it is its very existence.
Perhaps I didn't explain very clearly. On the internet side the service
provider enforces the use of proxies. Therefore if you don't set up a proxy
on the browser of the client desktop, you either surf very slowly or not at
all.
The difficulty arises where a page request is made of an address on the
organization's intranet. The browser makes the page request of the internet
proxy server, which of course has no idea of the intranet address space and
accordingly fails.
Implementing the proxy on the e-smith server as it stands gains me nothing
as it will still make the same request to the outside prosy server and
likewise fail.
However, from experimentation I know that at the client end, if I configure
it with two gateways and no proxy then if a request is made for a page from
the "currently in use gateway" and a failure results a request will then be
made automatically of the other gateway and that will succeed.
This is where transparent proxy support comes in. On the internet side all
requests must be made via the proxy, but if the e-smith server can be made
to do that automatically and then pass the resulting pages on to the client
browser without the client having to know anything about proxy support then
it will work perfectly (I hope).
E-smith as at 4.1.2 has the correct version of squid to do this and it also
has an installed (but unused?) copy of iptables. I lack the knowledge to set
up iptables either in place of ipchains or in addition to. I have made an
honest search for iptables documentation that I can understand and have not
found any. This is the help I am looking for.
Cheers
Tony Smith
Connected to the internet in Sunny Far North Queensland Australia
http://www.tonsyl.org