Multiserver / Cluster

WAN - external full public ip. And LAN's like 192.168.1.2. Router in LAN is 192.168.1.1 Like usually...just one LAN (server1: 192.168.1.5, server2: 192.168.1.6, etc.)

 

So I have a solution for this setup?

 

So... I have 3,4,5,6,etc. public IPs; each server with an IP. In this case I dont have a LAN anymore... and connection between servers must be by public IPs?

 

Hmm... I think my questions are good for me and the others and not come from a noob, maybe a noob in ispconfig...
Thats easy with each server with a public IP, but with one public IP... to sustain multiple servers its a question...
In a post from yesterday: the servers works well (with your help), but not the same services from all servers same time (because of one public IP and ports redirected to one LAN IP)... To put in practice ispconfig we must searching and reading this and this and this. You know, tutorials are a little bit complicated and works with some mods. For the staff maybe are like a kindergarden lesson, but I searching days and I dont find a tutorial or anything about my trouble... Just separate dedicated servers. Thats ok... I dont find anything good about a setup with 3 or 50 servers with the same services with proxy or not, with 50 public IPs or not.

 

Since you already tested that forwarding to the server2 makes websites on server2 work, your setup is OK and by port forwarding as previously discussed would make you setup work fully.
In other words:

• forward port 80 to server1
• forward port 82 to server2 (and use http://domainx.com:82/ to access websites)
• forward port 83 to server3 (and use http://domainy.com:83/ to access websites.

You can not use your servers directly because the 192.168.*.* addresses used in your intranet are RFC 1918 Private Address space addresses, which are not routable over the Internet. So no matter what, you can not use your servers directly from the Internet. They do work inside your Intranet, there you can control routers so they do route traffic to those private address space networks.
PS @till is correct. A frontend host doing proxy or something would also work to forward traffic to the correct internal host. Your router probably can only do forwarding based on port number.

 

yeah right, its basic network, but not good on production with different ports...
im in some disscutions with the provider about public ip class... fiber ont>router transparent> ips for each server
they have a solution about this problem. so thats look solved, but with different ips how the servers communicate? not like now by lan ips... by external ips? was my ante question when Till was irritated by my network knowledge... Was a question about ispconfig and intercommunications, for me...
and the proxy maybe...