Question about configuring firewall settings, domain management, and network pipe functionality.
Question about configuring firewall settings, domain management, and network pipe functionality.
You aim to run two websites on separate machines within the same network, directing traffic based on domain names. The goal is to route requests from different domains to their respective local IP addresses while keeping everything simple. You’re considering a basic home setup with an open network and no enterprise restrictions. A PFSSense router could work if needed, but you’re looking for a straightforward solution.
Apache Virtual Hosts were created to allow multiple sites on a single server without needing separate hosting. Learn more about the installation guide here: https://www.digitalocean.com/community/t...-14-04-lts
I'm not running websites directly. Instead, I'm managing two identical services across different machines on the same network. I prefer avoiding constant changes to port numbers since I anticipate needing more machines in the future, so I'm looking for a more efficient solution than relying on "website" as my comparison.
In this scenario, you must employ NAT forwarding to allocate a local IP address from a public one. https://documentation.meraki.com/MX-Z/NA..._on_the_MX
The problem is setting up two services on the same port while ensuring the network can direct traffic based on subdomains. Each service needs to be linked to a specific machine with unique IP addresses, even though both subdomains point to the same port. It’s possible but requires careful configuration.
You can indeed apply NAT with particular external IP addresses. It sounds like a straightforward approach now. In this scenario, you could run the same service on the same port but assign it different external addresses as needed. The main consideration is likely to save effort by avoiding changes to the default port for servers. If that’s the case, I can help explore further details.
I believe @Homeless Pineapple had an error and intended to specify the domain addresses correctly. The suggested format would clarify the internal and external ports for each domain. At the TCP/IP layer, only the IP address is visible; browsers send full hostnames, but routers typically ignore them unless advanced firewall rules are in place. If your router supports Layer 7 filtering, you might achieve the desired routing otherwise it won't work with just an external IP and port.
I think you referenced a previous message before I mentioned the 1:Many NAT change. From what I understand, 1:many supports translation between public and local ports, even though I haven't used NAT recently. https://meraki.cisco.com/blog/2014/08/1m...meraki-mx/
It seems you're planning to try various ports and will be using an Excel spreadsheet for your hosts list.