On Tue, Jan 27, 2015 at 5:17 PM, Geoff Higginbottom
geoff.higginbot...@shapeblue.com wrote:
Hi Hollman,
You need 4 IPs as there is one for the default Source NAT, then 1 per VM
to enable Static NAT.
I believe your original request was to enable three VMs to each have a
unique IP when they
On Tue, Jan 27, 2015 at 10:25 AM, Geoff Higginbottom
geoff.higginbot...@shapeblue.com wrote:
Sorry, wrong terminology
You need to use the Static NAT feature and you will need 1 Public IP per
VM in addition to the original Source NAT IP, so you will 4 Public IPs in
total
someting like
Hi Hollman,
You need 4 IPs as there is one for the default Source NAT, then 1 per VM to
enable Static NAT.
I believe your original request was to enable three VMs to each have a unique
IP when they access the Internet.
Regards
Geoff Higginbottom
CTO / Cloud Architect
D: +44 20 3603
On Tue, Jan 27, 2015 at 10:25 AM, Geoff Higginbottom
geoff.higginbot...@shapeblue.com wrote:
You need to use the Static NAT feature and you will need 1 Public IP per
VM in addition to the original Source NAT IP, so you will 4 Public IPs in
total
I found it on CS UI
...@shapeblue.com
-Original Message-
From: Geoff Higginbottom
Sent: 27 January 2015 15:24
To: 'users@cloudstack.apache.org'
Subject: RE: outbound/mask traffic configure
Hollman,
You can use the source nat feature, this will link each Public IP to a specific
VM
Regards
Geoff Higginbottom
D: +44
Hollman,
You can use the source nat feature, this will link each Public IP to a specific
VM
Regards
Geoff Higginbottom
D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
geoff.higginbot...@shapeblue.com
-Original Message-
From: Hollman Enciso R.