I'm not super keen on the fancy networking terminology to describe my situation, so please help me out with that as I describe my problem in the best terms I can.
Currently, we have a network living on the 10.0.0.0/24
subnet. We just purchased an embedded device that, apparently, has its IP flashed onto it by the manufacturer ( or at least that's how the tech who installed it described it ), and its IP address is 192.168.1.200
.
While I'm fully confident there's a semi-nice way to change the IP on this embedded device so that it can live on the same network as our other computers, is there a way I can just get the router to route traffic to this device and achieve the same goal? Currently the network and device are literally on the other side of the planet from me, so performing as few steps possible to get this working would be great.
If this matters, I have a SW24 router from SYSWAN.
Thanks!
UPDATE: I should probably mention an additional constraint: I can't change the IP address of the router so that it lives on the 192.168.1.0/24
network. Or at least, I don't think I can, previously it has caused problems. The two modems both all ready have the IP address of 192.168.1.1
, and the SW24 is Load Balancing our Internet between them. Previously when I've tried to give the router an address of 192.168.1.254
, it seemed to cause problems with our Internet.
Clarification: With regard to how the router should handle the traffic: I want the 192.168.1.200
host to work as though it were just another device on the 10.0.0.0/24
network. That is, from my 10.0.0.100
device, I should be able to ping 192.168.1.200
successfully, and vice versa.
Update: Here's a picture of how the network is sort-of laid out right now. The two clouds are the two modems, the 10.0.0.1
is the SYSWAN router's private IP address. I'd like for both of the 10.0.0.100
and 10.0.0.101
devices (actually there are a few more on the network, as well, but this is for simplicity of the picture) to be able to communicate with the 192.168.1.200
device. It seems like this is a job for static routes, but that's where I get confused. What kind of static route do I need to add to my router?
192.168.1.200
node, so adding another ip-address to that one node to sit on the192.168.1.0/24
network was simplest and cost efficient. If the requirements change, I'll definitely implement Catherine's solution.