yahoo-eng-team team mailing list archive

[Harald Jensås <hjensas@xxxxxxxxxx>]

Public bug reported:

When using routed networks[1] on an instance connected to multiple
networks the traffic from a segmant_a to segment_b within a L3 network
might be routed via a different network if the default router/gateway is
not on the interface connecting to the routed networks.

It would be good to (at-least have an option to) automatically configure
host_routes on the subnets in a routed L3 network. In such a way that
traffic with a destination on a different segment within the same L3
network is routed via the instance interface connecting to the L3
network.

Example:
 instance_a:
   - port_a: some_net, segmentA, subnet0  <-- default gateway
   - port_b: net1, segmentA, subnet0

 instance_b:
   - port_a: other_net, segmentA, subnet0  <-- default gateway
   - port_a: net1, segmentB, subnet0

Unless a host-route is in place, traffic from instance_a to instance_b
will use some/other-net, not net1 which both is connected to.

This RFE is to have the host_routes property on the subnets withing net1
populated, so that clients are aware of neighbour L3 networks.

[1] https://docs.openstack.org/neutron/latest/admin/config-routed-
networks.html

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: rfe

** Description changed:

  When using routed networks[1] on an instance connected to multiple
  networks the traffic from a segmant_a to segment_b within a L3 network
  might be routed via a different network if the default router/gateway is
  not on the interface connecting to the routed networks.
  
  It would be good to (at-least have an option to) automatically configure
  host_routes on the subnets in a routed L3 network. In such a way that
  traffic with a destination on a different segment within the same L3
  network is routed via the instance interface connecting to the L3
  network.
  
  Example:
-  instance_a:
-    - port_a: some_net, segmentA, subnet0  <-- The default gateway via this interface.
-    - port_b: net1, segmentA, subnet0
+  instance_a:
+    - port_a: some_net, segmentA, subnet0  <-- default gateway
+    - port_b: net1, segmentA, subnet0
  
-  instance_b:
-    - port_a: other_net, segmentA, subnet0  <-- The default gateway via this interface.
-    - port_a: net1, segmentB, subnet0
+  instance_b:
+    - port_a: other_net, segmentA, subnet0  <-- default gateway
+    - port_a: net1, segmentB, subnet0
  
  Unless a host-route is in place to use a routed on net1 is in place,
  traffic from instance_a to instance_b will use some/other-net, not net1
  which both is connected to.
  
  This RFE is to have the host_routes property on the subnets withing net1
  populated, so that clients are aware of neighbour L3 networks.
  
  [1] https://docs.openstack.org/neutron/latest/admin/config-routed-
  networks.html

** Description changed:

  When using routed networks[1] on an instance connected to multiple
  networks the traffic from a segmant_a to segment_b within a L3 network
  might be routed via a different network if the default router/gateway is
  not on the interface connecting to the routed networks.
  
  It would be good to (at-least have an option to) automatically configure
  host_routes on the subnets in a routed L3 network. In such a way that
  traffic with a destination on a different segment within the same L3
  network is routed via the instance interface connecting to the L3
  network.
  
  Example:
   instance_a:
     - port_a: some_net, segmentA, subnet0  <-- default gateway
     - port_b: net1, segmentA, subnet0
  
   instance_b:
     - port_a: other_net, segmentA, subnet0  <-- default gateway
     - port_a: net1, segmentB, subnet0
  
- Unless a host-route is in place to use a routed on net1 is in place,
- traffic from instance_a to instance_b will use some/other-net, not net1
- which both is connected to.
+ Unless a host-route is in place, traffic from instance_a to instance_b
+ will use some/other-net, not net1 which both is connected to.
  
  This RFE is to have the host_routes property on the subnets withing net1
  populated, so that clients are aware of neighbour L3 networks.
  
  [1] https://docs.openstack.org/neutron/latest/admin/config-routed-
  networks.html

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1766380

Title:
  [RFE] Create host-routes for routed networks (segments)

Status in neutron:
  New

Bug description:
  When using routed networks[1] on an instance connected to multiple
  networks the traffic from a segmant_a to segment_b within a L3 network
  might be routed via a different network if the default router/gateway
  is not on the interface connecting to the routed networks.

  It would be good to (at-least have an option to) automatically
  configure host_routes on the subnets in a routed L3 network. In such a
  way that traffic with a destination on a different segment within the
  same L3 network is routed via the instance interface connecting to the
  L3 network.

  Example:
   instance_a:
     - port_a: some_net, segmentA, subnet0  <-- default gateway
     - port_b: net1, segmentA, subnet0

   instance_b:
     - port_a: other_net, segmentA, subnet0  <-- default gateway
     - port_a: net1, segmentB, subnet0

  Unless a host-route is in place, traffic from instance_a to instance_b
  will use some/other-net, not net1 which both is connected to.

  This RFE is to have the host_routes property on the subnets withing
  net1 populated, so that clients are aware of neighbour L3 networks.

  [1] https://docs.openstack.org/neutron/latest/admin/config-routed-
  networks.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1766380/+subscriptions