Help Forwarding Incoming Requests to Other Internal Machines (not the web server)

[jkrell]

Hey all:

First off, I want to say that I am fairly well versed in computer hardware, networking, etc. but relatively new to Linux and very new to Web hosting. I just built a Web server, installed Fedora Core 5 and followed the excellent "How-To" on the "perfect setup." I now have ISPConfig installed and working great. Thanks to these excellent forums and some other great resources, I have my Web domain working just like I want it to.

The only thing left for me to do is to migrate one more thing from my Windows machine to my new Linux server so that the Windows machine can be shut down when not in use, and that is my setup for remote access to my TiVoWebPlus.

The way it is set up now, a incoming request to a certain domain (tivo1.xxxx.dyndns.com) is directed to my Windows machine. I have a program called OrenOSP (which as I understand it is based on Apache) set up to re-route these requests to my various TiVos (for instance, tivo1 would get rerouted to internal IP 192.168.1.121, and tivo 2 to .122, etc.). I know there has got to be a way to set up my Linux box to do this.

My first attempt was to simply set up co-domains where tivo1, tivo2, etc. were the hosts and were forwarded to 192.168.1.121, etc. While this works inside my network, it doesn't work remotely because, obviously, 192.168.1.121 is not an accessible IP from the outside world.

Any ideas as to how I would set this up? I only have one domain name, and would very much like to let my server handle these requests.

Thanks.

[falko]

Originally Posted by jkrell

The way it is set up now, a incoming request to a certain domain (tivo1.xxxx.dyndns.com) is directed to my Windows machine. I have a program called OrenOSP (which as I understand it is based on Apache) set up to re-route these requests to my various TiVos (for instance, tivo1 would get rerouted to internal IP 192.168.1.121, and tivo 2 to .122, etc.). I know there has got to be a way to set up my Linux box to do this.

If this OrenOSP is really running on Apache, it should not be difficult to move it to your new Linux system because you also have an Apache there.

[jkrell]

Sorry -- I think I was unclear -- what I meant to say was that I was told when I installed Orenosp is that it is similar to Apache.

I know I have Apache on my server, just not sure yet how to tell it to do this. Unless someone here has seen a "How-To" on this, I'll have to keep looking at the multiple resources I have come across thus far.

[falko]

Originally Posted by jkrell

Sorry -- I think I was unclear -- what I meant to say was that I was told when I installed Orenosp is that it is similar to Apache.

Is this what you're currently using? http://www.orenosv.com/orenosp_en.html

You can set up reverse proxies with Apache as well: http://httpd.apache.org/docs/2.0/mod/mod_proxy.html

[jkrell]

Originally Posted by falko

Is this what you're currently using? http://www.orenosv.com/orenosp_en.html

Yes.

Originally Posted by falko

You can set up reverse proxies with Apache as well: http://httpd.apache.org/docs/2.0/mod/mod_proxy.html

OK, I just worked on this, following the documentation you linked to above. I am able to get to the main index of my other servers (TivoWebPlus on my various TiVos), but any redirects screw me up.

The way TWP works, if you click on a link that operates a separate module, it redirects you to the relevant address (i.e., clicking on "User Interface" takes you to 192.168.1.121/ui).

The problem with the way Apache seems to do reverse proxies is that this causes a problem (i.e., clicking on "User Interface" takes you to www.mydomain.com/ui, which does not exist). Is there a way to tell Apache to stay on the servers behind the firewall? What use is this if it keeps pushing you back out to the public server?

[falko]

What does your reverse proxy configuration look like now?