Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ovs_bridge is not applied for fake bridges #313

Open
lachbaer opened this issue Oct 15, 2024 · 1 comment
Open

ovs_bridge is not applied for fake bridges #313

lachbaer opened this issue Oct 15, 2024 · 1 comment

Comments

@lachbaer
Copy link

An OVS fake bridge with VLAN ID 100 should be configured like this.

auto vmbr1
iface vmbr1 inet manual
        ovs_type OVSBridge
        ovs_bridge vmbr0
        ovs_options 100

However this fails, because the parent vmbr0 is not applied to the ovs-vsctl add-br command.
lachbaer added a commit to lachbaer/ifupdown2 that referenced this issue Oct 15, 2024
@lachbaer
openvswitch.py fix fake bridge parent
567585a 
This fixes issue CumulusNetworks#313 where the ovs_bridge parameter
for fake bridges was not applied.
@lachbaer
Copy link
Author

lachbaer commented Oct 15, 2024 •
edited
Loading

The current workaround is to put the parent bridge and VLAN ID in the ovs_options parameter.

auto vmbr1
iface vmbr1 inet manual
        ovs_type OVSBridge
        ovs_bridge vmbr0
        ovs_options vmbr0 100

@lachbaer lachbaer mentioned this issue Oct 15, 2024
Open
lachbaer added a commit to lachbaer/ifupdown2 that referenced this issue Oct 15, 2024
@lachbaer
openvswitch.py fix fake bridge parent
d4ac2a6 
This fixes issue CumulusNetworks#313 where the ovs_bridge parameter
for fake bridges was not applied.

This fix is backward compatible to the workaround where
the parent bridge name is repeated at the beginning of the
ovs_options parameter.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lachbaer