Redundant DHCP Request checks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DragonFlow |
New
|
Wishlist
|
rajiv |
Bug Description
In short we check all packets coming from routers and from VMs for DHCP IP resolution.
We need this check only for packets coming from VMs.
Technical explanation:
By default, all packets coming from virtual routers and from VMs is forwarded to OVS table 9.
One of the checks in this table is to check that the packet is DHCP IP resolution request that later is forwarded to CONTROLLER.
Basically all packet received from all interfaces (routers and VMs) pass this check.
We just need to check packets coming from VMs. All other checks are redundant.
Example:
table=0, n_packets=9, n_bytes=872, priority=
table=0, n_packets=1593, n_bytes=175246, priority=
table=0, n_packets=16, n_bytes=1685, priority=
In table 9:
table=9, n_packets=2, n_bytes=672, priority=
Where port1, port2, port3:
1(qr-f5fac1e2-29): addr:00:
2(qr-6bb13220-73): addr:00:
3(tap1ce66674-4f): addr:fe:
We just need to check only for port3: tap1ce66674-4f
Thanks
Yuli
Changed in dragonflow: | |
importance: | Undecided → Critical |
importance: | Critical → Wishlist |
Changed in dragonflow: | |
assignee: | nobody → rajiv (rajiv-kumar) |
We need to check if we can apply an optimization to not send all flows to table 9 (for example we might not need to send router ports to that table)