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. James Sent from my iPhone On Jun 9, 2015, at 6:43 AM, Miguel A Diaz Corchero <[email protected]<mailto:[email protected]>> 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 plugin.ini [ml2] type_drivers = gre, flat ... [ml2_type_flat] flat_networks = p3p1 ... [ovs] local_ip = 111.0.0.1 tunnel_type = gre enable_tunneling = True network_vlan_ranges = p3p1 bridge_mappings = p3p1:br-ex-p3p1 (only flat ??) l3_agent.ini ... 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. -- 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 <image001.png><http://www.ceta-ciemat.es/> ---------------------------- Confidencialidad: 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. Disclaimer: 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 [email protected]<mailto:[email protected]> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
