Yes, I understand the 192, will not be reachable from the public perspective, I
was just attempting to do just that, setup a VPN while at the office, but I
won’t worry about it; I’ll set it up while I am local on the home network.
Thanks for your help! =)
/ Mo
--
On October 15, 2014 at 1:56:
Ah, I see. I believe you'd need access to whatever IP the consoleproxy vm
is listening on. I don't actually use the console proxy vm for my purposes,
but I don't think you need to open the vnc console or libvirt ports to the
outside. If the console proxy works internally, you probably just don't
ha
Would this be on the Console VM, Or from the node? Need to know which local IP
I need to redirect it to.
I see in the log, it’s coming from 192.168.1.43 (which is console vm) so I
suspect there?
--
Mo
Sent with Airmail
On October 15, 2014 at 1:00:12 PM, Marcus (shadow...@gmail.com) wrote:
>From outside, (say from hotel, through home router, to mgmt server) you
need access to the web ui and for the web ui to have access to the api
server. That would just be 8080 (UI) and 8096(API), I believe. you wouldn't
need libvirt and the others unless you are stringing mgmt servers and hosts
acr
Yes, it's all under one server; KVM.On Aug 22, 2013, at 10:56 AM, "Musayev, Ilya" wrote:Are you using this host as both CloudStack management and also hypervisor? I have several instances of ACS installed, I don't have telnet or vnc enabled by default. This is indicative of your server configurat
Are you using this host as both CloudStack management and also hypervisor?
I have several instances of ACS installed, I don't have telnet or vnc enabled
by default. This is indicative of your server configuration (and services
installed) and not cloudstack.
From: Maurice Lawler [mailto:maurice
