You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 31, 2023. It is now read-only.
Current ACA openflow tables doesn't distinguish unicast/multicast packets. It simply sends packets to the multicast table which could flood all the remote tunnel endpoint. While traffic flow still work, but it is not most efficient. The request is to:
add the openflow rule to distinguish between unicast/multicast packets.
add a unicast table
populate the unicast table either by zeta OAM packet, and also create_update_neighbor_port function
Suggestions
Try to create the rules by hands and manually run through it with packet to confirm it is working
I have added unicast/multicast table and modified direct path rule.
The implementation details and test results of unicast/multicast table is in issue-148 chapter 3.1.4/3.2.4 & chapter 5.
Context
Current ACA openflow tables doesn't distinguish unicast/multicast packets. It simply sends packets to the multicast table which could flood all the remote tunnel endpoint. While traffic flow still work, but it is not most efficient. The request is to:
Suggestions
The text was updated successfully, but these errors were encountered: