Link aggregation/bonding on managed switch powered by OpenWRT

Hardware Questions and Recommendations
1

Hi everyone, I go through the forum and get a lot of informations but still being confuse.

Basically I have a OPNsense router and I want a managed switch for some extra ports. I want it to do vlan, also LAG/Bonding for redundancy and extra bandwidth.
I know if I want to do LAG/bonding I having to configure myself through CLI.

Here's my confuse point:

  1. switch like GS1900/DGS-1210/GS308T/etc that has Realtek chip(RTL83XX and others) has bad support on LAG/bonding, is it?

  2. OpenWRT itself also have no official support on LAG/bonding, is it?

Thank you!

2

LAG hardware offloading is not implemented for rtl838x/ rtl839x/ rtl93xx so far, and without the hardware acceleration it's too slow to be useful.

I don't think luci has a means to set up LAGs either, but on most devices other than realtek this isn't much of an issue (4+1 ports on almost all devices, LAGs don't help you there).

3

The drivers actually contain a broken LAG implementation, so the current state is even worse than just being slow.

It is supported with the package luci-proto-bonding. Unfortunately, it allows only configuration as an interface which needs to have an IP address and thus can't be part of a bridge. This is not just a limitation of LuCI. To be actually useful, netifd would have to be changed to support configuration as a device instead. There is an open issue about this (which seems to be associated with the wrong repository).

4

Are there ongoing work to have integrate OpenMPTCProuter into OpenWrt?

5

Do you happen to know if this issue is covered in a bug report anywhere? Or what the status is on LAG support? Thanks.

6

Aside from your reply to a nearly 2 year old thread, did you see the user's link to the bug report in the same post you quoted?

7

I did. That's not about LAG hardware offloading support in the driver, that's about bonding support in netifd.

8

The linked issue is actually invalid/outdated: netifd seems to support configuring bonding as a device just fine, and LuCI was extended to allow configuring this as well: https://github.com/openwrt/luci/commit/fb4cf432d2232a0ba2ccd3a8ff81a3679c8d054d

However, so far nobody has worked on improving/fixing bonding in the RTL83xx switch driver. I also don’t know of any issue tracking this.