During the migration from the legacy 3 table approach (Classifier, ingress and egress) to the 10 table pipeline approach with each table representing a service, the Flooding rules got impacted.

Essentially, we need 2 flooding rules per tenant in L2Fwd Table.
1. Identify if the flood traffic is originated remotely (maybe use a register value in CLASSIFIER) and send only to local ports in that tenant.
2. Identify if the flood traffic is originated by a local VM (use the same register with a different value) and send it to all the ports in that tenant (Tunnels and local ports). Reverse-poison will automatically drop the traffic to an output-port=input-port.