Our whole network infrastructure is working under the common 192.168.1.1 gateway, with its DHCP settings and range. However, we recently got a new application that requires to run its server under the specific ip address 10.240.100.200, clients can have any ip as long as they find the server running at that address, there is no way to access its source code and this setting cannot be changed.
As such we found ourselves with two choices: Change our whole network infrastructure gateway and lan to 10.240.100.x or create a whole new network infrastructure just to use this application. Both would take a lot of adjusting and cost some money.
Then I found about ip aliasing, which as far as I understand should allow this server to both be connected to our regular network infrastructure and have its own dedicated ip be 10.240.100.200 as the clients require. I have been messing with the settings for a while, but I haven't been able to make it work. Could you give me some guidance?
