Hi!
From a operator point of view, I think that it would be nice to give to the
FWaaS (IPv4 flavor), the ability to manage the tenant's NAT table, not only
the filter table, as it is today.
If fact, I don't know if it is out of the scope of FWaaS or not, it is just
an idea I had. Because right
- Original Message -
From: Dong Liu willowd...@gmail.com
To: Nir Yechiel nyech...@redhat.com
Cc: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Wednesday, January 8, 2014 5:36:14 PM
Subject: Re: [neutron] Implement NAPT in
I think that these two BP is to achieve same function,it is very necessary to
implement this function!
https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding
https://blueprints.launchpad.net/neutron/+spec/neutron-napt-api
At 2014-01-09 16:56:20,Nir Yechiel nyech...@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).
在 2014年1月8日，20:24，Nir Yechiel nyech...@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
