> > Well, the upstream code does not support VLAN/Bridge Forwarding. So, > > all traffic goes through the CPU (with the expected lower > > performance). I implemented that part in the driver but the maintainer > > rejected it as my implementation was based on Shared VLAN Learning and > > he already had one based on Independent VLAN Learning. However, that > > happened in early 2023 and no IVL appeared upstream. I've been keeping > > my code for personal usage. Should I include it as well as a pending > > (or hack) patch? > > We also need to get somewhere with this. I'm not sure I can help > super much, every time I deal with VLAN I feel like a hippo in a porcelain > store, but can you point me to the patches so I can form an > opinion?
There is some good news. I contacted the maintainer again and he plans to resume the work on that in a couple of months (customer demand). He did share his working tree but it is not in a publishable state yet. Let's keep this quiet for a couple of months for now. I don't think it is worth it for now to review my limited patches. Anyway, for the record, they are here (pending patches): https://github.com/openwrt/openwrt/commit/72959ee699a272ad9477449431da1cb8e4788945 (with some extra WIP not directly related to the vlan/forwarding). Regards, Luiz _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
