virtual hosts, virtual ip's?

kuplo · 11-29-2005, 07:06 AM

I run everything on virtual host name, but IM wondering if there is a way to give out virtual ip's off of my one ip on this linux box. Because I did this to my etho (1 ethernet card in my box)

eth0 Ethernet 192.168.1.100 255.255.255.0 Up
eth0:1 Ethernet (Virtual) 192.168.1.101 255.255.255.0 Up
eth0:2 Ethernet (Virtual) 192.168.1.102 255.255.255.0 Up
eth0:3 Ethernet (Virtual) 192.168.1.103 255.255.255.0 Up
eth0:4 Ethernet (Virtual) 192.168.1.104 255.255.255.0 Up
eth0:5 Ethernet (Virtual) 192.168.1.105 255.255.255.0 Up
eth0:6 Ethernet (Virtual) 192.168.1.106 255.255.255.0 Up
eth0:7 Ethernet (Virtual) 192.168.1.107 255.255.255.0 Up
eth0:8 Ethernet (Virtual) 192.168.1.108 255.255.255.0 Up
lo Loopback 127.0.0.1 255.0.0.0 Up

Is it possible to use one of these ip's a a virtual ip or as a serveralias to get to a site that hasnt propegated yet?So if I put ServerAlias 192.168.1.105 for a new domain would it be accessible by that, or do people just have to wait till it propegates.

Thanks,

twantrd · 11-29-2005, 01:43 PM

Quote:

but IM wondering if there is a way to give out virtual ip's off of my one ip on this linux box

Because 192.168 is a private class C ip address, you can't give that out. You can give out that 1 public ip address that you have and then forward any http requests to your 192.168.x.x address.

Also, why do you want so many virtual ip's? You can set up virtual hosting for many domains to point to one interface. I don't use ip alias whatsoever. That's how I'm doing mine.

-twantrd

kuplo · 11-29-2005, 02:48 PM

Im a newbiew, I thought I had to setup one virtual ip per virtual host even though all virtual hosts use 192.168.1.100

What would happen if I switched one over to a virtual ip, so instead of 192.168.1.100 I put 192.168.1.108 Would they be able to reach their site by that ip, or even reach that site by name anymore. I guess not since you said it's a class C ip address. How do I go about forwarding my regular 1 ip to the virtual ip's seperatly so they dont all go to the same place, assuming I can assign each virtual host its own virtual IP?

twantrd · 11-29-2005, 09:44 PM

Something like this is probably what you're looking for:

Code:

BindAddress 192.168.1.100
Listen 192.168.1.100:80

<VirtualHost 192.168.1.100>
ServerName blah.com
ServerAlias blah
DocumentRoot /var/www/docroot
HostNameLookups off
TransferLog logs/access.blah
ErrorLog logs/errors.blah
</VirtualHost>

<VirtualHost 192.168.1.100>
ServerName blah1.com
ServerAlias blah1
DocumentRoot /var/www/docroot1
HostNameLookups off
TransferLog logs/access.blah1
ErrorLog logs/errors.blah1
</VirtualHost>

So, whenever someone hits "blah.com" they will see whatever pages you setup in /var/www/docroot, while someone else that hits "blah1.com" will see whatever is in /var/www/docroot1. I don't use ip based virtual host, I use name based virtual host. To me, that's easier but it's really up to you.

How are people hitting your site now? Just people on your internal network or outside as well? If people from the outside are hitting your site, then you must be forwarding httpd requests from your router to your linux box.

-twantrd