379a9faf62
The native OVS/ofctl controllers talk to the bridges using a datapath-id, instead of the bridge name. The datapath ID is auto-generated based on the MAC address of the bridge's NIC. In the case where bridges are on VLAN interfaces, they would have the same MACs, therefore the same datapath-id, causing flows for one physical bridge to be programmed on each other. The datapath-id is a 64-bit field, with lower 48 bits being the MAC. We set the upper 12 unused bits to identify each unique physical bridge This could also be fixed manually using ovs-vsctl set, but it might be beneficial to automate this in the code. ovs-vsctl set bridge <mybr> other-config:datapath-id=<datapathid> You can change this yourself using above command. You can view/verify current datapath-id via ovs-vsctl get Bridge br-vlan datapath-id "00006ea5a4b38a4a" (please note that other-config is needed in the set, but not get) Closes-Bug: #1697243 Co-Authored-By: Rodolfo Alonso Hernandez <ralonsoh@redhat.com> Change-Id: I575ddf0a66e2cfe745af3874728809cf54e37745 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| async_process.py | ||
| base_polling.py | ||
| ip_lib.py | ||
| ovs_lib.py | ||
| ovsdb_monitor.py | ||
| polling.py | ||
| resource_processing_queue.py | ||
| utils.py | ||