Routes to neighbour subnets should be provided via DHCP

Bug #1372885 reported by Alexey I. Froloff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Wishlist
Alexey I. Froloff

Bug Description

As RFC3442 says:

   In some cases more than one IP subnet may be configured on a link.
   In such cases, a host whose IP address is in one IP subnet in the
   link could communicate directly with a host whose IP address is in a
   different IP subnet on the same link. In cases where a client is
   being assigned an IP address on an IP subnet on such a link, for each
   IP subnet in the link other than the IP subnet on which the client
   has been assigned the DHCP server MAY be configured to specify a
   router IP address of 0.0.0.0.

When network contains more that one IPv4 subnets, routes to these subnets should also be reported in 'classless-static-routes' DHCP option.

Tags: l3-ipam-dhcp
summary: - Routes to neighbor subnets should be provided via DHCP
+ Routes to neighbour subnets should be provided via DHCP
Changed in neutron:
importance: Undecided → Wishlist
tags: added: l3-ipam-dhcp
Changed in neutron:
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/125043

Changed in neutron:
assignee: nobody → Alexey I. Froloff (raorn)
status: Confirmed → In Progress
Kyle Mestery (mestery)
Changed in neutron:
milestone: none → kilo-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/125043
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6dce817c7c210b0c0862463384221ba5730cb8f3
Submitter: Jenkins
Branch: master

commit 6dce817c7c210b0c0862463384221ba5730cb8f3
Author: Alexey I. Froloff <email address hidden>
Date: Tue Sep 30 17:01:15 2014 +0400

    Provide routes for neighbor IPv4 subnets

    Network may contain several Subnets. In this case all these subnets are
    accessible via same link and two VMs with addresses from different
    Subnets may talk to each other directly, bypassing default router. For
    this to work, "neighbour Subnets" should have entry in VM's routing
    tables. RFC3442 describes this situation:

       In some cases more than one IP subnet may be configured on a link.
       In such cases, a host whose IP address is in one IP subnet in the
       link could communicate directly with a host whose IP address is in a
       different IP subnet on the same link. In cases where a client is
       being assigned an IP address on an IP subnet on such a link, for each
       IP subnet in the link other than the IP subnet on which the client
       has been assigned the DHCP server MAY be configured to specify a
       router IP address of 0.0.0.0.

    When network contains more that one IPv4 subnets, report these subnets
    in 'classless-static-routes' DHCP option.

    DocImpact

    Change-Id: Ifcf1d99e0f0136bf52b8d13675b7ccfd48005fab
    Closes-Bug: #1372885

Changed in neutron:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: kilo-3 → 2015.1.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Quan Tian (<email address hidden>) on branch: master
Review: https://review.openstack.org/352530

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.