Bug 1042455 - [RFE][neutron]: L3 agent support dual-NAT mode
Summary: [RFE][neutron]: L3 agent support dual-NAT mode
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/neut...
Whiteboard: upstream_milestone_next upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 22:20 UTC by RHOS Integration
Modified: 2015-12-10 20:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:44:55 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-12 22:20:26 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/l3-dual-nat-mode.

Description:

With dual-NAT mode enabled, each router has a 'private' gateway port, which is not maintained by Quantum. All those gateway ports of the routers in a L3 agent are bridged to br-ex and belong to the same local subnet (e.g. 169.254.4.0/24). The subnet's gateway is another tap device in the network node host and bridged to br-ex as well. There will be two NAT ops when a VM access outside network, one is between tenant network and "private" subnet, and the other is between "private" subnet and destination network.

Dual-NAT mode could bring two benefits:
* reduce the usage of public IP address
* VMs can access all the networks that can be accessed by network node host

Specification URL (additional information):

None
Note You need to log in before you can comment on or make changes to this bug.