[Openstack-operators] multiple gateways for network

Bajin, Joseph jbajin at verisign.com
Fri Dec 18 17:04:22 UTC 2015

You could put an interface from your first network to R2.  That will now allow connectivity between the two routers. 

Then on R1, you can setup host routes on R1 to point all traffic to the interface on R2 and you’ll most likely need to do vice-versa on R2 to point traffic back to R1.  

We don’t do cross Router host routes, but we use host routes, to send particular traffic to say a NAT device. 

From:  Akshay Kumar Sanghai <akshaykumarsanghai at gmail.com>
Date:  Friday, December 18, 2015 at 9:00 AM
To:  "openstack-operators at lists.openstack.org" <openstack-operators at lists.openstack.org>
Subject:  [Openstack-operators] multiple gateways for network

I have a network ,net1 with 2 VMs connected to it. One router R1 is connected to the n/w which connects to ext-net. I have another router R2 that connects to a diff network net2 in the tenant. Can i create matching rules for the network so that it forward the packet to R2 if destined to that network and set R1 as the default gateway for all other traffic. Is this possible? I do not want to add routes individually to each VM on net1 to forward traffic to net2. I also do not want to use a single router and connect to net2 and ext-net.

I have a use-case of 3 tier network architecture and each network will be connected to atleast 2 other networks. For a network ,adding static routes to VMs is not a good way to go.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20151218/7b261577/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5296 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20151218/7b261577/attachment.bin>

More information about the OpenStack-operators mailing list