Also, you can educate your users so they know that your network has a
proxy and to setup the proxy on the apps is a necessary step to get to
work. Proxy is not a 'out-of-the-earth' thing now days and most of the
users (on a enterprise network, at least) will be able to understand this.
Adam@Gmail wrote:
Hi there,
Thanks for your reply, I was merely asking if anyone has or had the
same problem before, or anyone who might have a solution, of course
If I stop squid now and disable it reconfigure my system to what it
was before of course I will get the updates and the access to the
internet
but now any application or programme I want to run I have to find out
where it is where it's going etc..
It looks as if I need to tweak for every single task,. of every single
application of every single client.
Yes I have followed the configuration where the whole internet goes
through a proxy, when faced with a problem like this can you
imagine how many programmes and apps are there? If I have to tweak
each and everyone of them by hand and how many clients I have and so on
So I can spend the rest of my life fixing things.
Anyway thanks for your reply
Regards
Adam
----- Original Message ----- From: "Jakob Curdes" <jc@xxxxxxxxxxxxxxx>
To: "Adam@Gmail" <adbasque@xxxxxxxxxxxxxx>
Cc: <squid-users@xxxxxxxxxxxxxxx>
Sent: Monday, March 29, 2010 7:00 PM
Subject: Re: Apt-get Issue through squid
Adam@Gmail schrieb:
Hello Everybody!
I have a question if you don't mind or if anyone has a solution to this
I am trying to download some packages with apt-get on one of my
Ubuntu clients
All of the links fail, which means they are blocked by Squid, When I
try the same thing
on the Squid machine itself which is also the router I get all the
updates
Please do not jump to assumptions without having checked the facts.
"All of the links fail, which means they are blocked by Squid" is the
least likely cause.
You can verify that easily by looking at the squid access log,
without going the deviation via the mailing list.
MY assumption is:
- The firewall on the router allows direct internet access
- so it is clear that apt-get on the firewall can get the updates
[without using squid at all]
- apt-get, being a unix-style command line tool, does not know or
respect the browser settings for proxies
- you did not set a http_proxy/ftp_proxy variable in the shell
calling apt-get nor did you configure a proxy in apt.conf
- As you do not allow direct internet access (or maybe even do not
have a gateway set on the client, which would be perfectly OK),
apt-get tries to resolve the name (may succeed depending on setup) an
then tries to download from the origin server
(which you prohibit, so it fails also).
It is very unlikely with any squid configuration near the defaults
(eg. without authentication or complex header manipulation)
that the proxy blocks requests from a particular machine depending on
the "browser" used.
Conclusion: 99% not a squid issue. You might ask on the ubuntu
mailing lists for help if Google does not give you enough explanation
how to use apt-get with a proxy.
HTH,
Jakob Curdes
