-
Notifications
You must be signed in to change notification settings - Fork 171
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Trapping DHCP packets in the ingress processing of Tap interface
Right the DHCP packets are processed in L2 multicast nexthop as DHCP request packet is a multicast packet. In a scaled setup, this leads to issues, as Agent receives the config late and VRF correspodning to VMI, L2 broadcast route and multicast nexthop also does not get added. This leads to DHCP request packet getting dropped. As "D" flag is set on VMI by Agent when nova-compute plugs the interface, the DHCP packet can be trapped to Agent without even the configuration. Agent in this case can provide the short lease to VM. So as a fix, the DHCP processing both in V4 and V6 are moved from L2 multicast nexthop to Vm ingress processing. Change-Id: I2a01aa282b6662ea1ef5832770cc92da931ee833 closes-bug: #1525028
- Loading branch information
1 parent
5c6390a
commit fdeb3c5
Showing
2 changed files
with
47 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters