Tue Feb 28, 2023 10:28 am
We ship the Mikrotik with our products, preconfigured to allow them to work.
We have a few devices that act as a cluster, and are configured with DHCP. They are identical but one of them takes the rule of a web server.
Moreover, since they are identical, the device taking the rule of the web-server can be replaced by another (either because it is faulty, or because the system configuration is changed). We want the Router configuration to be relatively static, which means that we do not know which of the devices acts as the web server, or what is his IP address.
We can know (or enforce) that the server will be connected to Ether2.
Up until now, we used static IPs, and made sure that the server had a specific IP outside of the DHCP range, but we want to change that.
This means that redirecting traffic coming into port 80 to Ether2 will solve our problem (instead of a specific IP, as in a normal port forwarding rule that we are currently doing).
Another option we just found: Creating a separate vlan with some IP address, bridge it to Ether2, and forwarding traffic to that IP. Sounds less ugly compared to 2 DHCP pools.