[Openstack-operators] Integrating flat and gre external network together.

James Denton james.denton at rackspace.com
Tue Jun 9 12:14:07 UTC 2015

Hi Miguel,

An external network should really be a vlan or flat network that has some external gateway in your environment. Although sometimes gre and vxlan network types are defined in the external provider network configuration, it's usually seen when the external bridge is br-ex (default) and the bridge is not handled by OVS (meaning there are no flows). Ultimately, the interface in br-ex handles how traffic gets tagged and the provider attributes are ignored.

Hope that helps.


Sent from my iPhone

On Jun 9, 2015, at 6:43 AM, Miguel A Diaz Corchero <miguelangel.diaz at externos.ciemat.es<mailto:miguelangel.diaz at externos.ciemat.es>> wrote:

I'm wondering  if it is possible to create multiple external networks mixing gre and flat types.

This is the current schema of networks:
internal networks -> gre
em2 -> gre
p3p1 -> flat

These are the configuration files

type_drivers = gre, flat
flat_networks = p3p1

local_ip =
tunnel_type = gre
enable_tunneling = True
network_vlan_ranges = p3p1
bridge_mappings = p3p1:br-ex-p3p1 (only flat ??)

gateway_external_network_id =
handle_internal_only_routers = True
external_network_bridge =

After this configuration, only new routers attached to gre external networks are not pingable from outside. The instances can ping to router but not outside.

The routers created under flat network work fine.

Any idea to integrate/repair flat and gre external networks together?


Miguel Angel D?az Corchero
System Administrator / Researcher
c/ Sola n? 1; 10200 TRUJILLO, SPAIN
Tel: +34 927 65 93 17 Fax: +34 927 32 32 37


Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener informaci?n privilegiada o
confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilizaci?n, divulgaci?n y/o copia sin autorizaci?n est?
prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique
inmediatamente respondiendo al mensaje y proceda a su destrucci?n.

This message and its attached files is intended exclusively for its recipients and may contain confidential information. If you received
this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and
may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately.

OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150609/2f9084ba/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 26213 bytes
Desc: image001.png
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150609/2f9084ba/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 26213 bytes
Desc: image001.png
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150609/2f9084ba/attachment-0001.png>

More information about the OpenStack-operators mailing list