Skip to content

bridge: honor bridge-allow-untagged in query-check - #353

Open
masonelmore wants to merge 1 commit into
CumulusNetworks:masterfrom
masonelmore:fix/bridge-allow-untagged-pvid-query
Open

masonelmore wants to merge 1 commit into
CumulusNetworks:masterfrom
masonelmore:fix/bridge-allow-untagged-pvid-query

Conversation

@masonelmore

Copy link
Copy Markdown

ifquery --check and ifup disagree about the PVID a bridge port should have when bridge-allow-untagged is no. Apply leaves the port with no PVID (bridge.py:1914-1922). The check expects a PVID of 1, so it fails on a correct configuration. This aligns ifquery with ifup. Ports that allow untagged traffic are unaffected. Closes #332.

Tested on Proxmox VE 9.1.7 with ifupdown2 3.3.0-1+pmx12:

# ifquery --check nic0; echo "exit=$?"
auto nic0
iface nic0 inet manual
exit=0

A bridge port with "bridge-allow-untagged no" is configured with no
pvid, but query-check derived the expected pvid from bridge-pvid alone
and fell back to 1 when there was none. ifquery -c reported "bridge
pvid error" on every such port.

Closes CumulusNetworks#332
Signed-off-by: Mason Elmore <masonelmore@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bridge pvid error on bridge-allow-untagged no port

1 participant