Hi folks
I switched from TrueNAS to ZimaOS on my NAS systen and I am to 98% happy with the change.
But I have one “problem”
In my system is a 1GB Nic Onboard and additional 2 2.5GB Nic Interfaces on an extension card.
Everything is working fine but I would like to combine the 2 2.5 GB Interfaces in one Linkagg or bond (don’t know how you would call it)
Is there a way to do this? I wasn’t able to finde a way over the GUI Interface
Thats not possible within the UI.
MAYBE with CLI, but keep in my mind: ZimaOS is built upon „Buildroot“-Linux and not debian/ubuntu/etc.
Damn it…
Tht is what I alerdy expected but I didn’t want to accept jet…
Has anybody already managed to get a link agg / bond working via cli?
Or do we need a feature request for the next version?
I mean I cannot be the only one who wants to use more then just one network interface.
The only other option to increase speeds for me would be to upgrade to 10GB nic and a matching 10GB switch…
I’m more a fan of “less is more” and I hate feature-packed operating systems, but everyone is free to submit a feature request. „Wieso nicht“, a german would say. 
Thank you for your opinion.
I think I will submit a request in the next days.
As a german I just say “Wieso nicht” 
Have you seen these posts?
Wow, thanks for attaching my post. In that post, to bridge the network, I used a script method executed via SSH.
I am not sure If I got it right…
So you configured a network bridge with two Interfaces and assigned an IP to the bridge Interface?
Did you configure anything on your network device (the switch)?
The “old school” way to combine Interfaces is LACP in it’s different variations on network and server side.
What I did was just create an IP binding on the Router to the ZimaOS device, then I made ZimaOS stay on DHCP as a bridge for the ethernet1 port from the main internet path on the ethernet0 port.
I read through your thread again and sorry If I ask a dumb question but your network topology is Like this:
Your WAN Router → your Zima Device with eth1 → your Zima Device with eth0 → your personal Pc
So you use your Zima Device as a switch and just need the IP on the device itself to acces your Zima Device?
Yes, that’s right, I use ZimaOS like a Switch Hub as a bridge to distribute internet and data via Ethernet port, because if it’s via WiFi, the speed is limited and not as good and stable as via LAN to my PC.
OK then I understood it right.
But for my use case it is not a suitable solution…
Reason: If I configure it this was with 2 interfaces in one bridge and the IP on the bridge itself the network switch cannot deal with it
When I plug in both Interfaces the switch has 2 ways to one MAC. This would result in “MAC Adress Flapping”
That’s the reason why I am looking for LACP.
But maybe the script solution you did can work for me too
The NAT thing maybe not to do link aggregation this post that was linked by @gelbuilding will indeed give instructions on how to aggregate those 2 ports. I was going to post if this is possible but searched first and found your thread. I just looked at this link How to Configure Link Aggregation on Linux to Increase Bandwidth
And it has step by step instructions on how to do it. Essentially you will end up with a new bond0 which has both nics under it, that the bond0 talks to your router with the one unified nic that is an aggregation of the 2 2.5gb nics.
It might be CLI, and it makes it look like the mode in the example is for redundancy vs getting 5gb combined througput There is probably a mode for aggregation for double throughput.
But I do think multiple nic management and bonding for aggregation both redundant and the create a double speed bond should be in the ZimaOS settings in the future. More and more devices are being sold with dual nics now. And lots of consumer switches have the ability to do aggregate links now.
I have a new sfp+ SWITCH and in a little over a month hopefully I’ll have a new NAS hardware device with ZimaOS on it that has dual SF+ plus ports that I hope to have aggregated for 20gb link. Also has 2 2.5gb nics, that 1 of those for sure will be setup for out of band management if I can. Maybe I can set 1 up as a bridge from the internal network space of a group of containers or a vm to the host network in a safe way.
I found the same article that you posted and tried to follow the guide.
My problem is to understand how ZimaOS handles it’s network configuration.
There is no configuration under /etc/network
Instead ZimaOS uses the NetworkManager
This is the folder where you can find config files for each network Interfaces.
I copied one of the files and edited it the way the guide shows to create a bond Interface.
Of course I also named the file corresponding to the existing files and checked the settings of the file.
But a restart of the NetworkManager and even of the whole system didn’t work.
I would really appreciate If link aggregation would be implemented in the Gui in a future version. I mean the ZimaCube has 4 network Interfaces