gregjc01

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by gregjc01

  1. Awesome work! This is something I've been looking for a while and glad to see such a clean implementation. Just wanted to say thanks for pushing through despite the previous failures and making this a reality.
  2. Just saw your note; basically having 2 LACP (bonding=4) at different MTUs...one with Jumbo frame for transfer between 2 servers and one for nzb, bt, etc, which don't play well with mtu=9000. Technically, I could use the 1 bond with LACP and mtu=9000 for transfer (rsync) between those 2 servers. Then just use 1 nic / bridged for plugins/docker containers/vms to run and serve content for the network. Ideally, I would like the 2nd bridge to be aggregated as well (so bonded=4 + bridged) especially since it'll be used for serving files as well.
  3. Ok; thanks for the heads up. Just curious, is there is a roadmap on when or which version this feature will be included in? I attempted to hard code 2 bonds in network.cfg with no success, so I'm guessing it's not just updating the front-end to allow for it.
  4. I have 4 NICs, and looking to have them in two bonds with 2 NICs each; each bond will bridged. One bridge will go for VMs and Docker, and the other bridge will be for accessing UnRAID and the shares. In essence, this is what I would like to do: br0 --> bond 0 --> eth0, eth1 br1 --> bond 1 --> eth2, eth3 (br1 will be used for all VMs and Docker containers) Is this possible? From the release notes on 6.2, I got the impression it could be done (re: https://lime-technology.com/unraid-server-os-6-2-released/) "You can now create multiple VLAN interfaces off a single physical interface, create multiple bridges or bonds, and either physically or logically separate network traffic between the host, your VM guests, and your Docker containers" I'm running unRAID 6.2.1.
  5. Awesome..thanks! I'll take a look at the script too.
  6. @steini84: did you make any progress in putting together a tutorial for compiling zfs and spl for new kernels? I mistakenly updated to new kernel and cannot access my pool now. Maybe a few high-level bullet points could help steer me in the right direction? While I'm new to the forum, I'm not new to unRAID, ZFS or Linux.