sharing bandwidth in a rack

I always have my servers work behind the a router, so that each servers are using 192.168.x.y and NAT

I have read the text about. since I have doing ip -base virtual hosting...

normally I will have

[ virutal hosting internal ip]

....

..
[/virtualhost]



If I am given real IP,

I think I should change the internal ip to real ip in httpd.conf into each virtual hosting. That is what the text said if I am not misleaded.

I will change comment by "#" in service to leave only 80, 443, 23xyx for ssh telnet and ssh ftp....etc.



Since it is real IP(static ip) , but I will also use zoneedit.com and I do not think it will hurt at all for static ip with zoneedit.com.


any comment!!!!!!!!!!!!

>> If I am given real IP,
>> I think I should change the internal ip in httpd.conf into each virtual hosting

No. You need to continue to use internal IP because your Apache is behind a router. In NAT, there are two types of functionality: 1) Mapping; 2) Redirecting;

And you are using (2) in this case. In this situation, NAT rewrites destination addresses and ports of the packets.

he said he will give me two real ip and no router, one utp cable.

NAT - network address translation, I think I am quite familar because I am using it everyday after office hour "at other location".

I once using SUN ENTERPRISE server with real IP. all ports are exposed and it was hacked when I received the project. But I fixed everything and re-deployed successfully last year.

NOW, I will be testing virtual hosting with real IP.

>> he said he will given me two real ip and no router, one utp cable

Then buy a hub yourself.