How to integrate a 10.0.36.* device into the 192.168.1.* subnet?

Question

Network administration

Hello everybody.
There is a device: LT-Artnet-DMX-2 is an ethernet-DMX512 gateway.
It has the peculiarity that the ip address is set only in the subnet 2.0.36.* or 10.0.36.* (selected by a switch), the last byte is set by two HEX controls.
The gateway works on port 6454 over UDP with almost any mask (255.0.0.0 - 255.255.255.0).
This device must be added to an existing local network with classic ip addresses (192.168.1.* mask 255.255.255.0). I would not want to reconfigure the existing network.
How is it easier and more stable to add several such devices so that they have an ip like 192.168.1.*?
For example, use a managed switch or router.

Answer 1

do they need (LT-Artnet-DMX-2) IP 192.168.1.*?
simple routing between two networks will not suit?

Answer 2

And you can describe this device, otherwise I look that this is a light control controller.)))

Answer 3

Option 1) Despite the fact that the device 192.168.1.6 has one Ethernet, it is quite possible that it supports secondary IP - then you assign some free one from 10.0.36 to the same interface.*
Option 2) If the devices are 10.0.36 .* do not need to communicate with the outside world, then set up a free secondary IP from 10.0.36 on the network router. * - the router always knows how to do this - there will be automatic routing through the router, since both networks will be directly-connected. You don't even need any routes. The problem can only arise if you have a second network 10.0.36.* somewhere far away, then the local 192.168.1.* will lose access to it.
Option 3 - as you want, but not optimal) Put a separate router on the network. On the interface to the 192.168.1.* network, register a pool of IP addresses by the number of devices, enable full NAT and configure IP in IP for each of the devices in the 10.0.36.* network (on the second interface). Note 1 - Perhaps your router will be able to NAT from one interface to the same one - then you can collect everything on one interface. Note 2 - Perhaps the software on the 192.168.1.6 machine can work on non-standard ports (and not just 6454), then on the NAT router you can get by with one IP from 192.168.1.* by setting up NAT tunnels from different ports of the 192.168 address. 1.X to different IP 10.0.36.* on port 6454.