Open Stack

That is what I thought but it does not seem to be working this way.  How would I check our snat namespace and what specifically should I be looking for?  My apologies but am very new to openstack.

Thanks.


> On May 2, 2016, at 9:51 PM, Dileep Varma Bairraju <varma123 at gmail.com> wrote:
> 
> Hi Jagga,
> 
> I don't think that's the right approach.Floating ip will effectively do a 1:1 NAT for a given a vm to reach external resources. But, there should be a ip from the external network that gets assigned to SNAT namespace on network node, this effectively will let all vm's (without floating ip) access external resources.
> 
> I'd suggest you check at your snat namespace for possible issues, as you seem to have patched the problem for that vm with floating ip's.
> 
> > Is that by design or is there something wrong with our configuration?
> As per design, you don't need to assign floating ip's for your vm's to get out, this should be done by SNAT by default as mentioned earlier, where all the vm's internal ip space maps one external ip.
> 
> Regards,
> Dileep
> 
>> On Mon, May 2, 2016 at 8:32 PM, Jagga Soorma <jagga13 at gmail.com> wrote:
>> Hi Guys,
>> 
>> Need some clarification regarding routing for instances without a floating ip address. Basically we have instances connected to a priv network that is also connected to our external network and our security group allows all egress traffic. However, we can't seem to get to any resource on our external network till a floating ip address is assigned. Once we assign a floating ip address we can get out.  Is that by design or is there something wrong with our configuration?
>> 
>> Thanks.
>> 
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 
> 
> 
> -- 
> Regards,
> Dileep V Bairraju
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160502/3a7f6d49/attachment.html>