most probably there will be no solution (from what I found so far on the forum and the net), but still.. lets try:
Topology:
PC Server
PC Client
Managed Switch
Mikrotik to be configured ( if possible)
ethernet device with no gateway (only static IP address on subnet 192.168.33.0 255.255.255.0)
Problem: No communication with Ethernet device from PC Server, only from PC Client
Mikrotik will need same subnet on both ethernet interfaces ETN1 and ETN2, which does not work.
No need of Internet, this is connection to industrial device.
I will tell you what I have tried so far:
Bridging Ethernet 1 and 2 interfaces (MAP 2nd).
NAT from PC Server to Ethernet device.
I have reset both configurations with no export files, since nothing worked.
My question is principal, what is the approach here, if any?
It is supposed that MT, properly configured (as I said, if it is possible at all), will help to provide connection between PC server and Ethernet device.
I’m still at loss. PC client and ethernet device, being in the same IP subnet, can communicate directly if only switches and wires are in between. It’s the PC server which needs help. Is there any particular reason for this topology (i.e. PC client and PC server in different subnets but on same ethernet broadcast domain and ethernet device on another broadcast domain)?
There are ways to even make your current layout work, but IMO this combination of physical layout and IP layout is flawed and I think it would be better if you could make things more “by the book”.
And then it’s important to know the limitations of ethernet device (e.g. it may only work within single IP subnet or some such).
Thanks for your reply, mkx. To throw some light, what is shown on the topology, is one branch from company’s network. The PC Server does not need help, because it communicate perfectly with other 40 devices without issues. But, they have gateway properly configured. The ethernet device does not have any. If the static IP address of the ethernet device was on another subnet, I would place MT with NAT, and it will work just fine, I have at least 15 other devices working this way. But since the ethernet device has static address 192.168.33.142, i.e. on the same subnet between the managed switch and the device, neither NAT, nor bridge work. There is simple solution, to change the IP address of the device, but I am not owner of the its program, and next appointment with the manufacturer is after two months. So, shall I forget for any workaround until then? Nothing to lose, at the end of the day…
I think you could use MT device … but not the way you tried. You would connect it to the managed switch with single connection (e.g. ether2). Then assign two IP addresses to same interface, one in 192.168.0.0/24 and one in 192.168.33.0/24. Then configure hairpin NAT - this means both DST NAT and SRC NAT - for protocols and ports needed. Devices outside 192.168.33.0/24 will use router’s address from 192.168.0.0/24 subnet, ethernet device will see router’s address (from 192.168.33.0/24 subnet) as source address.
