Routes to neighbour subnets should be provided via DHCP
Bug #1372885 reported by
Alexey I. Froloff
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-
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 |
Changed in neutron: | |
milestone: | none → kilo-3 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/125043
Review: https:/