[openstack-dev] [neutron] Implement NAPT in neutron (https://blueprints.launchpad.net/neutron/+spec/neutron-napt-api)

Nir Yechiel nyechiel at redhat.com
Thu Jan 9 08:56:20 UTC 2014

----- Original Message -----

From: "Dong Liu" <willowd878 at gmail.com> 
To: "Nir Yechiel" <nyechiel at redhat.com> 
Cc: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org> 
Sent: Wednesday, January 8, 2014 5:36:14 PM 
Subject: Re: [neutron] Implement NAPT in neutron (https://blueprints.launchpad.net/neutron/+spec/neutron-napt-api) 

在 2014年1月8日,20:24,Nir Yechiel < nyechiel at redhat.com > 写道: 

Hi Dong, 

Can you please clarify this blueprint? Currently in Neutron, If an instance has a floating IP, then that will be used for both inbound and outbound traffic. If an instance does not have a floating IP, it can make connections out using the gateway IP (SNAT using PAT/NAT Overload). Does the idea in this blueprint is to implement PAT on both directions using only the gateway IP? Also, did you see this one [1]? 


[1] https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding 

I think my ide a is duplicated with this one. https://blueprints.launchpad.net/neutron/+spec/access-vms-via-port-mapping 

Sorry for missing this. 

[Nir] Thanks, I wasn't familiar with this one. So is there a difference between those three? 


Looks like all of them are trying to solve the same challenge using the public gateway IP and PAT. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140109/0df56e3e/attachment.html>

More information about the OpenStack-dev mailing list