If I edit the second NAT rule and replace the IP 192.168.5.21 to any other from the 192.168.0.0 range, it will work. The question is, what do I need to configure to be able to NAT to 192.168.5.0.
It should work.
But your device (PC?) must be attached to the right interface on the router…
Can you ping the 192.168.5.21 from the router? From other PC?
And what does “/ip route print” say?
And what does “/interface print” say?
It seems the problem is rooted in the fact that you renamed the interfaces to “ether3-LAN” and “ether3-LANO”.
Forget IP addresses, and tell us in words, what the use case is or cases are?
What do you need to provide to people or devices, (capabilities, requirements) without talking solution space(the config).
Then it will be clearer.
(So far it looks like you have two subnets on the same port that you want to nat one to another and which makes no sense at all anyway I think about it)
@mutluit ‘It seems the problem is rooted in the fact that you renamed the interfaces to “ether3-LAN” and “ether3-LANO”.’ It’s a typo, both are ether3-LAN.
There are 2 Lan networks, one for the PC/Laptops/Access points/etc (192.168.0.0/24), and another one for PLCs/etc (192.168.5.0/24). Being on the same interface I guess, I can ping to any PLC on the other LAN.
The thing is, a provider needs to have access to a PLC, 6 to be specific, I will use the same public IP, but different ports.
Checking the status of the rule using Winbox/web interface, it appears to be working, looks like the package gets lost somewhere.
It is simply impossible to have two /24 IP networks on the same router port (that’s IP routing 101, first lesson ).
Either use a separate router port for each, or change the mask from /24 to /21 for example, and attach a dumb switch to the router port and attach the end-user devices to that switch:
>
For mask /21 change it as follows, and remove the 2nd there:
/ip address
add address=192.168.0.189/21 comment=LAN interface=ether3-LAN network=192.168.0.0
On the router you can assign multiple networks to a port, yes.
But how do you attach the end-user devices to that port? Surely you must be using a switch for this. But then the switch cannot handle such 2 networks, unless it’s a managed switch and you can tell the switch the same that you told the router… Ie. you would need to do similar settings on the switch as well…
Don’t get me wrong, but I prefer pure clean IP routing, not any tunneling nor some other tricks nor some esoteric protocols. Yes, it might somehow work, but it wouldn’t be a “clean” solution, IMO. Maybe someone else can help you further, I’m giving up.
).