Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm in the process of setting up a squid server, but I want to do it without having to go to each individual computer, and setting up the browser to use the proxy server....does anyone know what could be the physical setup for this?...this is for a small home office of 10 computers
Without changing *ANYTHING* on the client at all, you'd need a transparent server setup (save for anything not even more complex) which would see any web traffic is it passes through. This naturally requires significant infrastructure configuration and removes lots of potential benefits...
It is actually *possible* that you might be able to use wpad configuration on the clients, assuming that they are already set up to "automatically detect" and all that... that'll require local DNS and a small web server but would provide a full conventional proxy to each client. have a google for wpad (sadly the w does stand for windows but hey...)
Last edited by acid_kewpie; 12-29-2007 at 04:24 PM.
I think the best way to do this is to change the gateway ip given by dhcp from the router to my squid server, it receive all http request, and then do a redirection on the server from port 80 to 3128, I think that'll do it
Last edited by Tinkster; 03-27-2008 at 10:42 PM.
Reason: shameless plug removed
[QUOTE=mia_tech;3005683]I think the best way to do this is to change the gateway ip given by dhcp from the router to my squid server, it receive all http request, and then do a redirection on the server from port 80 to 3128, I think that'll do it
well I think this setup will only work for http connections, but not for any other application, email etc...b/c it will be sending the connection to the squid server, and since that server only has on interface it can not act as a router....correct me if I'm wrong
you appear to be talking to yourself.... and what you suggested is exactly what i suggested, a transparent proxy.
I'm kind of confuse as to the infrastructure needed for this setup...my squid server has only one interface and my router is syslink, and there's no way to redirect internal traffic to the squid server which is inside my network...any other ideas
Last edited by Tinkster; 03-27-2008 at 10:43 PM.
Reason: shameless plug removed
these things can depend how "professional" a solution you want and are happy with. you could use the server as the default gateway, enable routing on it and just have two seperate neworks on the single nic. no need for anything fancy or new gear. an "insecure" and dubious design in an enterprise network but your scenario seems to be fairly basic, so not a huge concern.
you can see though that this sort of architecture puts a requirement on that server for *ALL* internet traffic, not just web, which is a danger. if you can, configure the clients with a proxy.pac file or something, and leave the physical architecture untouched.
Last edited by acid_kewpie; 12-30-2007 at 04:03 PM.