I didn't know which OS to put. The host OS is Debian 7.11. The guest OS is FreePBX, which is based on CentOS 7. However, I've had this issue on Debian, CentOS 6, ...
Main Steps to reproduce: - create empty system - set up the parameters as you normally would for any system; in my case, I've chosen 4GB RAM, 10GB HDD, set a hostname, ...
Path 1: - select manually entered ip addresses below: 18.104.22.168 255.255.255.240 * gateway ip address from host system 10.127.0.150 255.255.255.0 * don't get gateway ip address from host system
Path 2: - assign only on bridges br0 - enter ip address information for br0 below: 22.214.171.124 255.255.255.240 * gateway ip address from host system - after vm is created, add in the additional interface for br1
Whether I use path 1 or 2, I then set up the ip addresses inside the vm.
I was able to fix this problem for a while by going in and swapping the br0 and br1 inside of cloudmin, and then swapping them back. However, that doesn't seem to be working any longer. This new vm I'm trying to get working is very pig headed about not wanting to work.
I can ping 126.96.36.199, but I cannot ping 10.127.0.153 or 10.127.0.2 or 10.127.0.4. The host 188.8.131.52/28 / 10.127.0.4/24 does not have an active firewall.
For an example of one that works, mon1.hammersoftware.ca (184.108.40.206). 220.127.116.11 also works great, but it's running RouterOS (a highly customized Linux kernel/package manager).
I can give you access to 18.104.22.168, 22.214.171.124 and 126.96.36.199 if you'd like. 188.8.131.52 you'll need to access from .152 or .153 because 184.108.40.206 is not routing...it's only available across the br1 interface, even though it's bound to br0.
I can also give you access to the cloudmin interface.
Please let me know.