3e94111d6b
For networks in the same address scope, network traffic routes directly. This happens not only between internal networks, but also between internal network and external network. No SNAT is applied when routing traffic to the external network because addresses on the internal network are assumed to be viable on the external network. For networks in different scopes, network traffic can't route directly. Between internal networks in different scopes, traffic is blocked. DNAT for floating IPs will still work. Also, shared SNAT to the external network will still work as it does today. Change-Id: I439633ebef432b1a2eecee09b647207d5a271bf6 Co-Authored-By: Hong Hui Xiao <xiaohhui@cn.ibm.com> Implements: blueprint address-scopes
Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
External Resources:
The homepage for Neutron is: http://launchpad.net/neutron. Use this site for asking for help, and filing bugs. Code is available on git.openstack.org at <http://git.openstack.org/cgit/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
- Neutron Administrator Guide
- Networking Guide
- Neutron API Reference:
-
http://docs.openstack.org/api/openstack-network/2.0/content/
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.