Dear Jason,
Thanks for your reply.  I'm not sure if you understand my question correctly,  
we wanted to use the network's source nat IP address  as the static nat address 
for an instance.
The enableStaticNat API method doesn't support the same and results in "Can't 
enable static, ip address Ip[10.11.101.156-1] is a sourceNat ip address".

Besides, since return value of createPortForwardingRule (successful asyncjob) 
does have public/private endport and if I remember correctly it did worked in 
previous version of cloudstack,  we tried to patch createPortForwardingRule 
method to have publice/private endport parameter.   
It does work.  Now we can use this method for specifying port range. 
command=createPortForwardingRule&response=json&virtualmachineid=f123fa46-1d9c-4fec-ada0-a261920efe9c&ipaddressid=fe3d6a4a-4afc-4967-9850-f92451e11e28&privateport=1&privateendport=65535&publicport=1&publicendport=65535&protocol=UDP

we would like to contribute the patch if there are no obvious reasons for 
having it missing from Cloudstack 3.x version.

Cheers
/Mukesh

-----Original Message-----
From: Jason Bausewein [mailto:jason.bausew...@tier3.com] 
Sent: donderdag, 16 augustus, 2012 18:23
To: cloudstack-dev@incubator.apache.org
Subject: RE: port-range support in createPortForwardingRule API method

Hi Mukesh,

You could enable a static NAT which would forward all traffic from a public IP 
to a private IP.

http://download.cloud.com/releases/3.0.0/api_3.0.0/root_admin/enableStaticNat.html

-----Original Message-----
From: Mukesh Kumar [mailto:m.ku...@leaseweb.com] 
Sent: Thursday, August 16, 2012 5:49 AM
To: cloudstack-dev@incubator.apache.org
Subject: port-range support in createPortForwardingRule API method

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 a IP 
that belongs to a network, to an instance within the same network.

Using createPortForwardingRule API method seems good solution, but we're not 
sure how to assign a port-range, as the API doesn't have something like 
privateendport & publicendport.
we definitely don't want to do ~130k API calls specifying all TCP/UDP ports 
separately.

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

Regards
/Mukesh

Reply via email to