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.

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

FS#2986 - Functionality broken by migration to DSA for Ubiquiti ER-X #7756

Closed
openwrt-bot opened this issue Apr 9, 2020 · 6 comments
Closed
Labels

Comments

@openwrt-bot
Copy link

mar-kolya:

Supply the following if possible:

  • Ubiquiti ER-X
  • Trunk
  • Build trunk of Openwrt and try to configure vlan enabled interfaces on an embedded switch.

Hi.

I have Ubiquiti ER-X which I have been using for quite a while and it was working just fine.
I was using it to route traffic from external internet connections to a 'trunk' port connected to a different OpenWrt device used as access point. So to clarify: I have one of the swich ports configured as 'tagged' ('tunk') for multiple vlans.

Unfortunately commit 30644bc that switched this device to use DSA for switch configuration have completely broken this setup.

And I'm not talking abut soft bricking - that was to be expected. Unfortunately DSA doesn't provide functionality that was available in swconfig for years. Namely it seems to be impossible to configure switch ports to be 'tagged'.

It looks like DSA is considered to be 'the future' but unfortunately it doesn't see to be ready for prime time - it seems to be impossible to use DSA enabled devices in configurations that were perfectly possible before.

@openwrt-bot
Copy link
Author

mar-kolya:

This is probably related to FS#1622 but for different HW.

@openwrt-bot
Copy link
Author

dl3it:

related to bug #2981.
With change to DSA, the configuration of the switch is fully broken. I managed to configure the switch by hand with multiple VLANs on one connection (e.g. LAN1), but it is impossible to integrate this in any way into the standard config process within openwrt/LUCI.

For shure, it is good to see DSA is working. But releases with DSA enabled are useless unless the configuration is fully supported.

BTW, openwrt documentation for DSA is non existing. Most likely for a good reason :-)

So please... Either provide configuration examples for using DSA with openwrt/LUCI or switch back to swconfig.

@openwrt-bot
Copy link
Author

n8v8R:

The correct method for VLAN management of DSA ports (switch downstream ports) is via the bridge v command [1 | 2] and which works well but is known as currently not being supported via L/UCI [3]


[1] [[https://www.linux.org/docs/man8/bridge.html]]
[2] [[https://www.kernel.org/doc/html/latest/networking/dsa/configuration.html]]
[3] [[https://github.com/openwrt/luci/issues/2798]]

@openwrt-bot
Copy link
Author

mar-kolya:

Hi n8v8R, thank you for your response!

Thank you for providing those links. I've seen them before I've posted this bug. Unfortunately I was not able to setup 'tagged' port that has multiple vlans (i.e. pvids) passed through it. I do no think any of the links provide an example for this and FS#1622 suggests it may not be possible with DSA.

Am I missing something?

Would really appreciate your help.
Thanks!

@openwrt-bot
Copy link
Author

n8v8R:

The forum has this thread [4] particular to the device/issue, citing some sort of patches. The thread though seem to exhibit a bit of confusion (and redundancy deployment) on tag management on DSA ports (//bridge v// vs. //virtual interfaces//)

IMHO FS#1622 is unrelated, because:

  • different device with a particular CPU - Switch setup (dual CPU, each CPU featuring its own physical lane to the Switch chip, CPU eth0 <-> Switch port 6 and CPU eth1 <-> Switch port 5)
  • for the aforementioned setup the device manufacturer has a developed a patch that is not available in OpenWrt however (and communication with about patch acceptance in Linux kernel has stalled)
  • with the patch deployed DSA tagging with //bridge v// works on the device

[4] https://forum.openwrt.org/t/er-x-sfp-vlans-not-working-properly-with-kernel-5-4/60002

@ynezz
Copy link
Member

ynezz commented May 23, 2022

Try to reproduce it with latest 22.03-rc2 or development snapshot and report back, we can re-open the ticket.

@ynezz ynezz closed this as completed May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants