openstack team mailing list archive

[Ahmed Al-Mehdi <ahmedalmehdi@xxxxxxxxx>]

Thank you very much for the explanation.  However, I am still a bit
confused.  In the command "quantum subnet-create ..." for external network,
I am already providing start/end allocation pool IP addr.  What is the need
for the "192.168.50.100/24" option?  In this case, is this option redundant
 OR  not needed (as in not used by Quantum)  OR not correctly specified?

You mentioned "192.168.50.100/30", how did you get "/30"?  Is that an
example?  Or is that based on the start/end IP allocation pool?

Thank you,
Ahmed.



On Wed, Nov 28, 2012 at 4:44 PM, gong yong sheng <gongysh@xxxxxxxxxxxxxxxxxx
> wrote:

>  On 11/29/2012 07:56 AM, Ahmed Al-Mehdi wrote:
>
> Hello,
>
>  I have a few questions related to private and external network in
> Quantum.  I am running into some odd behavior with networking related to my
> VM instance that I am trying to resolve.
>
>
>  # quantum net-create --tenant-id $put_id_of_service_tenant ext_net
> --router:external=True
>
>  # quantum subnet-create --tenant-id $put_id_of_service_tenant
> --allocation-pool start=192.168.50.102,end=192.168.50.126 --gateway
> 192.168.50.1 ext_net192.168.50.100/24 --enable_dhcp=False  (step b)
>
>
> -  192.168.50.100/24:  Is 192.168.50.100 assigned (reserved) for any
> purpose?  What is this cidr represent?
>
> It should be a wrong cidr.
> I think if you are using 192.168.50.100/30, the 192.168.59.101 will be
> reserved.
>
>