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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A transparent proxy is when the client requires no configuration to be proxied.
The way to achieve this is to create fw rules on the gateway that redirect packets with the one destination port, to anther port, generally where the proxy software is listening.
The classic example is for your gateway firewall to redirect packets destinated for port 80 to 3128 or 8080 where they are handled by the proxy server/filter and then passed (if necessary) to the actual destination server/port.
The reason for it is to prevent people un-proxying their http (or whatever) connections.
A transparent proxy is when the client requires no configuration to be proxied.
The way to achieve this is to create fw rules on the gateway that redirect packets with the one destination port, to anther port, generally where the proxy software is listening.
The classic example is for your gateway firewall to redirect packets destinated for port 80 to 3128 or 8080 where they are handled by the proxy server/filter and then passed (if necessary) to the actual destination server/port.
The reason for it is to prevent people un-proxying their http (or whatever) connections.
So this is really only useful for within networks behind a firewall where you want internet connections to go through the proxy first?
If I have a proxy available to anyone on the internet they still need its IP address and I would forward connections on port 80 to 3128?
Why not just tell them to connect to 3128?
So this is really only useful for within networks behind a firewall where you want internet connections to go through the proxy first?
Yes. But then that's the whole point (or at least one of
the major points) of having a proxy.
Quote:
Originally Posted by qwertyjjj
If I have a proxy available to anyone on the internet they still need its IP address and I would forward connections on port 80 to 3128?
Why not just tell them to connect to 3128?
Yes. But then that's the whole point (or at least one of
the major points) of having a proxy.
Because it requires *no* set-up on the client?
Cheers,
Tink
Well, it does in an environemtn where people are connecting to a proxy outside of thir network. For example, to hide their IP or spoof the fact that they are in their own country.
For this, the user has to set up the IP address in their browser anyway don't they?
I guess giving them a different port hides the proxy server port?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.