Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
How Link a port from the WAN to 2 lan host ? : wan 192.168.55.56:2422 - > LAN hosts same bridge 192.168.88.56:2422 & 192.168.88.186:2422
Re: Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
Impossible. Is not a mikrotik issue, is a logical issue. How could you (the router) determine what is the correct destination between two packages?
Re: Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
As @hgonzale says - impossible.
The only thing you can do is to determine another external port and forward it to the desired port of the other device, for example:
1st device
forward external port 80 to IP 192.168.1.10 internal port 80
2nd device
forward external port 81 to IP 192.168.1.11 internal port 80
The only thing you can do is to determine another external port and forward it to the desired port of the other device, for example:
1st device
forward external port 80 to IP 192.168.1.10 internal port 80
2nd device
forward external port 81 to IP 192.168.1.11 internal port 80
Re: Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
only one host active, second passive ->
Full task: 2 wan interfases 1st 192.168.55.56 second 192.168.55.186
2 lan interfaces 1st 192.168.88.56 second 192.168.88.186
From the first wan go the requests 2421 to lan hosts
From the second wan go the requests 2422 to lan hosts.
How to split requests or switch considering that only 1 of them is active
Full task: 2 wan interfases 1st 192.168.55.56 second 192.168.55.186
2 lan interfaces 1st 192.168.88.56 second 192.168.88.186
From the first wan go the requests 2421 to lan hosts
From the second wan go the requests 2422 to lan hosts.
How to split requests or switch considering that only 1 of them is active
Re: Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
So ... it is possible as you have two totally different redirects.
The first is from IPA:port2421 to LAN IP1:port2421
The second from IPB:port2422 to LAN IP2:port2422
The problem is with "one is active". What means "one is active" ?
Check this https://wiki.mikrotik.com/wiki/Manual:I ... ernal_host
The first is from IPA:port2421 to LAN IP1:port2421
The second from IPB:port2422 to LAN IP2:port2422
The problem is with "one is active". What means "one is active" ?
Check this https://wiki.mikrotik.com/wiki/Manual:I ... ernal_host
Re: Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
Yes, that is rightSo ... it is possible as you have two totally different redirects.
The first is from IP1:port2421 to LAN IP1:port2421
The second from IP2:port2422 to LAN IP2:port2422
The problem is with "one is active". What means "one is active" ?
Check this https://wiki.mikrotik.com/wiki/Manual:I ... ernal_host
Code: Select all
1 chain=dstnat action=dst-nat to-addresses=192.168.88.56 protocol=tcp dst-address=192.168.55.186 dst-port=2422
2 chain=dstnat action=dst-nat to-addresses=192.168.88.56 protocol=tcp dst-address=192.168.55.56 dst-port=2421 It is necessary as that to provide switching or activation of rules NAT in a case when 2 host becomes the MAIN ->
Code: Select all
1 chain=dstnat action=dst-nat to-addresses=192.168.88.186 protocol=tcp dst-address=192.168.55.186 dst-port=2422
2 chain=dstnat action=dst-nat to-addresses=192.168.88.186 protocol=tcp dst-address=192.168.55.56 dst-port=2421 
Re: Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
I believe this can be treated as a feature request to be implemented by Mikrotik.
Because large vendors already have a server load balanced solution: F5 Networks, A10, Cisco...
There is even an open source implementation.
Is a very lucrative market as companies are looking for this high availability solution.
Because large vendors already have a server load balanced solution: F5 Networks, A10, Cisco...
There is even an open source implementation.
Is a very lucrative market as companies are looking for this high availability solution.
Re: Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
Any ideas? What can be done to solve the problem ... 
Re: Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
What do we know from which server is MAIN at the moment ?...It is necessary as that to provide switching or activation of rules NAT in a case when 2 host becomes the MAIN -> ...
Do I understand that it is router role to decide which one is MAIN ? Do you need, mentioned earlier, load balancer ?
Re: Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
Servers handle requests on these ports and decide among themselves who is the main one, the router does not participate in this, the servers have additional interfaces (network adapters) on which they decide which of them is the main one.What do we know from which server is MAIN at the moment ?...It is necessary as that to provide switching or activation of rules NAT in a case when 2 host becomes the MAIN -> ...
Do I understand that it is router role to decide which one is MAIN ? Do you need, mentioned earlier, load balancer ?
The default is the master 192.168.88.56.
if he down, 192.168.88.186 becomes the main.
I need advice, a hint how to ensure the reception of requests to the server at the moment being the main
Re: Can Port Forward the Same Port # to 2 Different Internal IP Addresses?
Seems to be "quite" easy.
Both servers should have script "fired" on event of becoming main router.
The first server should have script disabling the second rule and enabling the first one
The second server should have opposite script.
Scripts should be started as ssh session to the router...it could look like ... writing pseudopseudocode
Both servers should have script "fired" on event of becoming main router.
The first server should have script disabling the second rule and enabling the first one
The second server should have opposite script.
Scripts should be started as ssh session to the router...it could look like ... writing pseudopseudocode
Code: Select all
/ip firewall nat
set [find where comment=RULESERVERA] disabled=yes
set [find where comment=RULESERVERB] disabled=no