Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

A How To Guide: Setting up SMB3.0 Multichannel on FreeNAS

Recommended Posts

Posted · Original PosterOP

This guide has been written by someone who is NOT a certified expert. If any information is inaccurate or could be phrased better do contact me so I can update it.


A step by step guide to setting up SMB3.0 Multichannel on FreeNAS.


What is Multichannel?

Multichannel, which is a feature of SMB3.0 (a Microsoft file sharing protocol) enables people to simply and easily aggregate multiple physical network links and allows a single client to utilize the combined bandwidth. For example, instead of being stuck with 1Gbit file transfers you could have 2Gbit or 4Gbit. In theory if you're using 10Gbit you could aggregate them to create 20Gbit or 40Gbit to a single client.


As of Windows 8 and later SMB3.0 Multichannel is included and enabled by default. At the same time Microsoft has refined the drivers for this process to a point where setting it up is plug'n'play in most instances. Now SMB3.0 multichannel on FreeNAS or any other *NIX based system on the other hand isn't as easy. Not only are there prerequisites but your configuration has to follow specific instructions. SAMBA is responsible for bringing SMB support to *NIX not Microsoft so enabling certain features of the protocol are done differently.


This guide will help people who want to set this up on FreeNAS but may prove to be useful for people using other versions of *NIX. It should also be known that Multichannel as of late 2017 is still considered experimental and you mileage may vary. SAMBA has no official support for it but it can work with the right setup.


What are the prerequisites?

In order to use multichannel at all on FreeNAS you need to have SAMBA version 4.4.0 or later. You can check what version you have by entering shell and using the following command:

samba --version

If your version is outdated one method of obtaining an up to date version is to update FreeNAS itself.


What hardware is needed?

There's a few options. You can use a single multiport NIC that has 2 or 4 ports or you can use multiple NICs which will offer redundancy as SMB multichannel if the aggregated link is lost the remaining link(s) will continue to operate at the cost of reduced performance. Each machine will require an equal number of ports.


IMPORTANT: It is very recommended when aggregating the links that the NICs support Receive Side Scaling (RSS). RSS allows the responsibility of handling multiple TCP/IP connections to be divided up across multiple CPU cores. If you just so happen to have NICs that support Remote Direct Memory Access (RDMA) this will also work but this is a feature on enterprise NICs and is only really applicable to very low latency applications.


The best way to check if your NICs support RSS is to find what chipset is used and search that chipset on the web. For example the Intel i210, Intel 82574L, & Broadcom BCM57810S all support RSS.


You will also require a network switch. Any layer 2 switch should suffice so long as it has a sufficient number of ports and the ports support speeds equal to that of the NICs.


How to configure:

This is where things differ quite a bit from Microsoft Windows implementation. Note that the interface configuration on your Windows machine will need to follow the same structure as on the FreeNAS server. The way Microsoft setup the protocol to work was in 2 different ways. The user could plug every port into the switch, have a router connected running DHCP, have every port on the NICs set to DHCP, then SMB would automatically see every port on the same network

and aggregate them.


IMPORTANT: The other way SMB3.0 multichannel can work is by setting up the interfaces in pairs on different networks/subnets. At this time this is the only method SAMBA supports for multichannel. Below are a few ways of achieving this:


If the server is part of your local network and you want 2Gbit or 4Gbit but everyone else is fine with 1Gbit then that means the existing network needs to stay in place. So lets say the existing network is and the server has a static address of you can set up the other interfaces on the server on the network then and 3.0. Now admittedly this is a huge waste of addresses if the aggregated connection is only for one host. The following is a more proper configuration in this instance:


PC NIC1: (/24 =
PC NIC2: (/30 =




A /30 subnet is very useful for point to point connections. This prevents wasting addresses. If you have 4 interfaces on the server and you're the only person who needs 4Gbit probably the best way to set up the addresses without modifying the existing local network would be to go:






In this configuration (above) each pair of interfaces (.10 & .254, 1.1 & 1.2, 1.5 & 1.6, 1.9 & 1.10) are all on different networks or more accurately would be to say each pair are on different subnets. The subnet mask (the /24 & /30 also depicted as & determines what addresses or octets are network bits and which are host bits.


What if I want an independent dedicated 2Gbit or 4Gbit network with 1 host?

If you buy or have a pair of dual/quad port 1Gbit NICs and have a switch you want to dedicate to linking the server to your computer with then it makes things easier. First off you'll have to setup the interfaces on networks other than your home/office network. Personally if the primary network is or or 10.>0.0.0 then the easiest way for me to subnet the interfaces would just be to use Class A:


What other configuring is necessary?
A big thing that differs from Windows is that SAMBA has multichannel disabled by default. You have to enable it. You can do this by going to the FreeNAS WebUI then going to Services and configuring the service CIFS/SMB (its name will be either CIFS or SMB depending on your version) you will then have to find the Auxiliary Parameters option (to see it you may have to click Advanced Mode). In here you will have to type the following command:

server multi channel support = yes

This will modify the smb.conf file. You will also have to set the Server maximum protocol to SMB3.0_11. There's also _02 & _00 these correspond to which version of windows you're using but setting the maximum protocol to _11 will make the connection between Windows and the server use the highest protocol that they both support.



With everything setup in this manor you should now see speeds in excess of 1Gbit for file transfers. If not re-check your configuration. If this doesn't fix the issue try using SMB3.0_02, SMB3.0_00, or SMB3.0. If none of this helps it is sometime necessary to update windows for multichannel support.

Guides & Tutorials:

VFIO GPU Pass-though w/ Looking Glass KVM on Ubuntu 19.04

A How-To Guide: Building a Rudimentary Disk Enclosure

Three Methods to Resetting a Windows Login Password

A Beginners Guide to Debian CLI Based File Servers

A Beginners Guide to PROXMOX

How to Use Rsync on Microsoft Windows for Cross-platform Automatic Data Replication

A How To Guide: Setting up SMB3.0 Multichannel on FreeNAS

How You can Reset Your Windows Login Password with Hiren's BootCD - (Depreciated)


Guide/Tutorial in Progress:

How to Setup Drive Sharing in Windows 10


In the Queue:

How to Format a HDD/SSD in Windows

How to Flash a RAID Card to IT Mode


Don't see what you need? Check the Full List or *PM me, if I haven't made it I'll add it to the list.

*NOTE: I'll only add it to the list if the request is something I know I can do.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now