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
When setting up VLANs I of course forgot about how important the bridge-port pvid setting is. So I tried to correct my mistake at runtime by entering the CLI and adding pvid to all bridge ports.
No success 😢
Saving running-config and rebooting, however, worked.
In addition to fixing the issue (not taking until after reboot), we should either derive/infer (post leave) PVID for untagged ports, or warn users with a YANG must expression.
This patch adds support for small incremental changes to bridge ports.
Changes where the libyang diff does not include a bridge reference so
that it will have to be synthesized from the current configuration.
For example, forgetting to set a port's PVID in a VLAN filtering bridge
setup, changing a bridge port's multicast flooding properties, or any
other per-bridge-port setting after the fact.
Fixes#349.
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
This patch adds support for small incremental changes to bridge ports.
Changes where the libyang diff does not include a bridge reference so
that it will have to be synthesized from the current configuration.
For example, forgetting to set a port's PVID in a VLAN filtering bridge
setup, changing a bridge port's multicast flooding properties, or any
other per-bridge-port setting after the fact.
Fixes#349.
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
This patch adds support for small incremental changes to bridge ports.
Changes where the libyang diff does not include a bridge reference so
that it will have to be synthesized from the current configuration.
For example, forgetting to set a port's PVID in a VLAN filtering bridge
setup, changing a bridge port's multicast flooding properties, or any
other per-bridge-port setting after the fact.
Fixes#349.
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
When setting up VLANs I of course forgot about how important the
bridge-port pvid
setting is. So I tried to correct my mistake at runtime by entering the CLI and addingpvid
to all bridge ports.No success 😢
Saving
running-config
and rebooting, however, worked.In addition to fixing the issue (not taking until after reboot), we should either derive/infer (post
leave
) PVID for untagged ports, or warn users with a YANGmust
expression.Any comments, ideas, suggestions @wkz and @mattiaswal?
The text was updated successfully, but these errors were encountered: