On Fri, 24 Feb 1995, Craig Knudsen wrote:
> Does anyone have any experience using IP address aliasing.
>
> Here is what we need to do:
>
> We have a customer who wants to register their own domain name.
> Their single machine name will be our www server (www.btg.com).
> We want to be able to use this one machine as the www server
> for ourselves and this customer. Additionally, we want the URL
> http://www.btg.com/ and http://other.company/ to be a different
> page. I know that we could run a second www server on a
> different port number (http://other.company:8123/), but that's
> kind of ugly. Right now we are stuck with http://other.company/dir.
> The problem with this is that if someone omits the "dir" than they
> will get our home page. And this would not be politacally correct
> for the contract. So... my real question is...
>
> Can a server process tell what IP address a client used to get to it?
> If the answer is yes, then I can write a toplevel wrapper that will
> direct http requests to the different pages...
From what you are describing, i have a few questions on the implementation:
You mention that you will have several names for your machine,
however, you didn't mention how many IP addresses you have
nor how many ethernet interfaces you have. Each IP address
must have its own unique interface.
I have an alternative solution which may not be
the most feasable, but, is likely easier than recoding a lot of
software. Find an old 386/33 with about 8-16mb of ram. Install
linux and use it as a WWW server. I used on at umass/amherst
for a while and found it to equal the speed of a decstation 5000/133
for WWW processing (which isn't very much). It handled
about 15,000-20,000 requests per day.
-- craig
Received on Fri Feb 24 1995 - 09:49:49 NZDT