PDA

View Full Version : If port 80 traffic, route to IP



abates1
09-May-2012, 13:38
Hello dear community!

I am a total suse n00bie who has been asked to help on an installation of Suse Linux Enterprise Server 10.

Info:
- DNS is set to this one SUSE10 server for the clients
- The domain setup of the SUSE10 server is abc.com
- The SUSE10 has no webservers for port 80 (resulting in a timeout)
- The Webservers are hosted off-site

Case:
- How can i set up a simple redirect for port 80 traffice, so that both www.abc.com and abc.com (port 80) traffic gets relayed to an IP adress (the off-site webserver)

I am currently logged into the system via VNC, using YaST
I also have a client that has admin via NovellConsoleOne

Though my efforts of both googling and looking through the configs, i fail to see the solution

Any help and pointers would be greatly appriciated!

Jim Henderson
09-May-2012, 17:09
On Wed, 09 May 2012 12:44:01 +0000, abates1 wrote:

> - How can i set up a simple redirect for port 80 traffice, so that both
> www.abc.com and abc.com (port 80) traffic gets relayed to an IP adress
> (the off-site webserver)

There are a few ways to handle this, each with their own pros and cons.

You might look at using the firewall to do the redirection. It would be
similar to a NAT type setup (in theory), but would redirect traffic to
the remote server. It's possible that this might create some issues for
the webserver itself.

Second would be to install Apache and have Apache do a meta redirect to
the proper location. This would essentially hand off the request to the
remote server, and it would be the cleanest way to handle the requests,
but it also removes the local server from the picture entirely once the
handoff has happened.

Third involves the use of some Apache-fu. :) Using mod_proxy, you can
essentially redirect requests through your server to a remote server.
Your server stays involved, but sends the requests to the remote server.
I've played with this a *very* little bit, but if you search on
mod_proxy, that should get you started to determine if this solution
might work for you.

Jim



--
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell Knowledge Partner

abates1
10-May-2012, 11:43
Hello! Thank you for your prompt response!

I think we should go for the Apache solution as this is what i also had in mind, but if i either as a .htaccess or a index.html set the requests to go to abc.com, and the domain name is abc.com (locally), will this not make a indefinete loop?

Jim Henderson
10-May-2012, 16:55
On Thu, 10 May 2012 10:44:01 +0000, abates1 wrote:

> Hello! Thank you for your prompt response!
>
> I think we should go for the Apache solution as this is what i also had
> in mind, but if i either as a .htaccess or a index.html set the requests
> to go to abc.com, and the domain name is abc.com (locally), will this
> not make a indefinete loop?

It would, so you'll need to use a different domain name on one or the
other systems.

Although you /might/ be able to put the name abc.com in the server's
local hosts file.

Another option just came to mind, though - and I'm not sure why I didn't
think of it before...Use the Squid proxy software and point the browser
at your server as a proxy server. Then the requests go to the server and
there's nothing else you have to do.

Jim

--
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell Knowledge Partner

abates1
11-May-2012, 10:27
Lovely! Testing out the Squid now, slippery!