topic Changing the ML Address in Expedition Discussions

Changing the ML Address

Tim_Grossner — Sat, 14 Jul 2018 22:26:28 GMT

Changing the ML address to "localhost", it keeps going back to the IP assigned to the virtual ethernet interface. Did we ever come up with a way to force it to change to and keep "localhost"?

Re: Changing the ML Address

dgildelaig — Thu, 19 Jul 2018 18:35:30 GMT

Does "localhost" resolve to the IP that it assigns?

We do prefer to have the IP than localhost, as some processes with "localhost" are not completing correctly to resolve the IP (we have experienced that before).

Re: Changing the ML Address

SLetard — Thu, 09 Aug 2018 17:41:10 GMT

Issue still present with version 1.0.101:

- Neither localhost or 127.0.0.1 is accepted.

- It always goes back to the IP of the VM.

Re: Changing the ML Address

anuj_mor — Thu, 30 May 2019 15:57:49 GMT

I am having the exact same problem. THe ML server IP is shown incorrect ...some 192.168.252.136 and unable to change it to either 127.0.0.1 or the expedition server IP address. After entering the correct IP, it reverts to 192.168.252.136. How do we resolve it?

Re: Changing the ML Address

dgildelaig — Thu, 30 May 2019 17:48:53 GMT

As mentioned above, neither the localhost or 127.0.0.1 are allowed, as would not allow connections between ML and expedition processes.
If you enter an invalid IP or leave it blank, expedition will determine its own IP checking its interface.
So, if it reverts back to a certain IP, this means that Expedition has that IP assigned to its main interface

Re: Changing the ML Address

anuj_mor — Thu, 30 May 2019 20:28:01 GMT

I wasn't mentioning localhost or 127.0.0.1. I was entering the correct IP (expedition server IP) for ML server but despite of clicking save, it use to revert the IP to some 192.168.x.x range which I believe would have coded while extracing the OVA/OVF image. We used OVA to build expedition. At the end, I rebooted expedition and then updated the IP again and this time is worked.