Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I have a squid-box with other services running on it. This squid service on this box needs to be stopped for certain other activities. The web traffic however cannot be disrupted. So i have setup another squid-box-2.
My query is how do i redirect all web traffic from squid-box to squid-box-2.
well how are clients reaching that box in the first place? what other network architecture do you have? presumably you don't want to actually redirect on the box itself if it's a maintenance window you're after...?
All the clients have their browser configured for the SQUID-BOX IP and PORT. After authentication on this box, they are able to browse.
Now since the squid services on this box are to be stopped, i need some method to divert the web traffic coming to the SQUID-BOX on port 3128 to the new SQUID-BOX-2, without the users being hassled about it.
wel you could use an iptables rule on the box, but ideally you'll have a NAT capable router between these points which would be a better way to do it... is there such a thing?
on the server itself, "iptables -t nat -A INPUT -i eth0 -p tcp --dport 3128 -j DNAT --to other-squid-box:3128" should work i think... but this isn't a nice solution if you're actively working on the box.