One thing which is a bit awkward as long as the bridge itself is configured as an interface, is that as far as I have understood, creating a tagged interface to the bridge requires first setting up an interface for the bridge, e.g. with protocol Unmanaged, and then setting up one or more vlan tagged interfaces on top of it which can then be configured with ip addresses.
(Maybe this isn't such a big deal though.) On Thu, 16 Jul 2020 at 06:00, Felix Fietkau <n...@nbd.name> wrote: > > On 2020-07-15 13:52, John Crispin wrote: > > > > On 15.07.20 13:39, Jo-Philipp Wich wrote: > >> Hi, > >> > >>> If we can't come up with a working automatic scheme, maybe we could have > >>> an option to disable the cpu port per vlan? > >> Having a default-enabled "option self" or "option local" was my idea as > >> well. Any idea which name fits better? > >> > >> ~ Jo > >> > > self is what ip-bridge uses as a parameter name for this feature > I think local is a better fit - self/master seems to be used for bridge > vlan filter command target selection, not just for this feature. > > - Felix > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
