Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of m.kumar@leaseweb.com
 designates 85.17.130.6 as permitted sender)
From: Mukesh Kumar <m.kumar@leaseweb.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Fri, 17 Aug 2012 11:26:15 +0200
Subject: RE: port-range support in createPortForwardingRule API method
Thread-Topic: port-range support in createPortForwardingRule API method
Thread-Index: Ac17zH7zhl64KVW2SqaucPVxSUV78QAihp8g
Message-ID: <2E7DE59E63E62E428DCDF9A173D43BF12F7FE14911@soco-ex02.ocom.lan>
References: <2E7DE59E63E62E428DCDF9A173D43BF12F7FE148DD@soco-ex02.ocom.lan>
 <CC526D64.FA62%alena.prokharchyk@citrix.com>
In-Reply-To: <CC526D64.FA62%alena.prokharchyk@citrix.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Dear Alena
Thanks for your comment.   Please find my inline reply. Also, take a look a=
t the email I've sent at cloudstack-dev@incubator.apache.org addressing Jas=
on Bausewein

-----Original Message-----
From: Alena Prokharchyk [mailto:Alena.Prokharchyk@citrix.com]=20
Sent: donderdag, 16 augustus, 2012 18:31
To: cloudstack-dev@incubator.apache.org
Subject: Re: port-range support in createPortForwardingRule API method

On 8/16/12 5:49 AM, "Mukesh Kumar" <m.kumar@leaseweb.com> wrote:

>>Dear All,
>>We are trying to setup Cloudstack 3.0.2 with advance network.
>>
>>One of our business case, is to forward all the traffic (TCP/UDP), for=20
>>a IP that belongs to a network, to an instance within the same network.
>>
>>Using createPortForwardingRule API method seems good solution, but=20
>>we're not sure how to assign a port-range, as the API doesn't have=20
>>something like privateendport & publicendport.
>>we definitely don't want to do ~130k API calls specifying all TCP/UDP=20
>>ports separately.


>Port ranges are not supported in createPortForwarding rule API.

Found the same in  API manual.   but it is indeed possible; we patched crea=
tePortForwardingRule method to just have public/private endport parameter a=
nd its working.
Are there some reasons why it's not provided in CloudStack 3.x?

>>did we overlook some way of using the network source nat address  as=20
>>the static nat address for an instance?  or some another solution to=20
>>achieve the same?

>We do have static nat support in cloudStack. Following commands need to be=
 called

>* enableStaticNat&virtualMachineId=3D<vmId>&ipAddressId=3D<publicIpId> - m=
aps vm to public ip address
>* createFirewallRule&ipAddressId=3D<publicIpId>&startPort&endPort - opens =
access to the public ip address for specific port range
>

I'm afraid, Not if you want to to use the network's source nat IP address  =
as the static nat address for an instance. It gives an error saying "Can't =
enable static, ip address Ip[10.11.101.156-1] is a sourceNat ip address"

>Hope this solution helps you.

>-Alena.

>>
>>Regards
>>/Mukesh
>>
>>

Cheers
/Mukesh