Link aggregation bonds two or more network cables together so data moves faster between devices on your home network

Link aggregation (also called bonding or teaming) takes multiple network cables running between two devices and treats them as a single, faster connection. Instead of one cable carrying data at, say, 1 gigabit per second, two cables bonded together can move data at 2 gigabits per second. The devices on both ends must support it, and you need a switch or router that understands the setup — but when it works, you get a real speed increase without buying faster cables.

Most home networks do not need it. A single modern network cable (Cat6 or Cat6A) is fast enough for streaming, gaming, and video calls. But if you have a network storage device, a media server, or a desktop that regularly moves large files to another computer, link aggregation can cut transfer times noticeably. It is also useful if you have a network switch that handles traffic from many devices at once and you want to prevent that switch from becoming a bottleneck.

Key Takeaways

  • Link aggregation requires compatible hardware on both ends — your switch or router and the devices you are connecting must both support it, usually through a feature called LACP (Link Aggregation Control Protocol).
  • You run two or more physical network cables between the same two devices and configure them as a single logical connection in your device settings or router interface.
  • The speed increase is real but only applies to traffic between those two specific devices — it does not speed up your internet connection or make Wi-Fi faster.
  • Most home networks see no practical benefit unless you regularly move large files between devices on your local network or run a media server that streams to multiple devices at once.

When link aggregation actually helps in a home network

Link aggregation makes the biggest difference when you have a network-attached storage device (NAS) or a dedicated media server and you regularly copy large files to or from it. If you back up a 500 GB external drive to a NAS over a single gigabit connection, that transfer takes roughly 45 minutes. With two bonded cables, it takes roughly 23 minutes. The time savings are real, but only if you do this kind of transfer often enough to justify the extra cables and configuration.

It also helps if your network switch is handling traffic from many devices at once. A switch has a total amount of bandwidth it can move between all its ports. If you have a switch with eight gigabit ports, and four of those ports are in heavy use simultaneously, the switch itself can become the bottleneck. Bonding the connection from your switch to your router or to a central storage device can ease that congestion. Again, this is uncommon in a typical home setup.

Link aggregation does not speed up your internet connection. It only affects traffic between devices on your local network. If your internet comes in through a single cable from your modem, bonding cables elsewhere in your network will not make web browsing, streaming, or downloads any faster.

What hardware you need to set up link aggregation

Both devices must support LACP (Link Aggregation Control Protocol), the standard that lets them negotiate and maintain the bonded connection. Check the specifications for your network switch, router, and the device you want to bond to. Most modern managed switches support it. Most consumer routers do not — they typically support only basic switching and do not have the configuration interface for LACP. If your router is not a managed switch, you will need a separate managed switch to bond devices together.

You also need at least two network cables of the same type and length running between the two devices. Use matching cables (both Cat6, for example) so they perform identically. The cables do not have to be new or expensive — standard network cables work fine. You will plug both cables into separate ports on the switch or router, and separate ports on the device you are bonding to.

Some network interface cards (NICs) in desktop computers or servers support bonding in software, even if the switch does not. This is less common and requires driver support from the manufacturer. Check your device's documentation before assuming software bonding is an option.

How to physically set up the cables

Run two network cables from the device you want to bond (your NAS, media server, or desktop) to your network switch or router. Plug one cable into one port on the switch and the second cable into a different port. Do the same on the device side — each cable goes into a separate network port if the device has multiple ports, or into a separate network interface card if you have added one.

Label the cables or ports so you remember which ones are bonded together. This matters later when you configure the connection. Take a photo of the setup with your phone if it helps you remember.

Do not plug both cables into the same port. Do not use a splitter or hub. Each cable needs its own dedicated port on both ends.

Configuring link aggregation on your switch or router

The exact steps depend on your hardware. If you have a managed switch, log into its web interface (usually by typing the switch's IP address into a browser). Look for a section called "Link Aggregation," "Port Bonding," "LACP," or "Trunking." Select the two ports you just plugged cables into and create a new aggregation group. The switch will ask you to choose a protocol — select LACP if it is an option, as it is more reliable than static bonding.

If your router is a managed switch (some higher-end models are), follow the same process in the router's admin interface. If your router is a standard consumer model, it likely does not have this option, and you will need a separate managed switch.

On the device side, you may need to configure bonding in the operating system. On a Linux server or NAS, this usually means editing network configuration files or using a graphical interface to create a bonded interface from the two physical ports. On Windows, some network interface cards have bonding software in the driver package — check the manufacturer's website. On a Mac, bonding is not typically supported in the standard network settings.

After you configure both ends, the bonded connection should come up automatically. Check the switch or router interface to confirm both ports show as active and bonded. On the device itself, you should see a single logical network interface with an IP address, even though it is backed by two physical cables.

Testing whether link aggregation is working

Copy a large file from your computer to the bonded device and watch the transfer speed. On Windows or Mac, the file manager shows transfer speed in real time. On Linux, use a command like iperf3 to measure bandwidth between two devices. You should see speeds close to double what a single cable would give you — roughly 1.8 to 1.9 gigabits per second with two bonded gigabit cables, accounting for overhead.

If the speed does not improve, check that both cables are plugged in, that both ports on the switch are part of the aggregation group, and that the device is configured to bond the two interfaces. A common mistake is configuring only one side of the connection — the switch must be set up, and the device must be set up, or the bonding will not work.

Troubleshooting common link aggregation problems

If the bonded connection does not come up, start by confirming that both cables work individually. Unplug one cable and verify the device still has network access through the other. Then unplug that one and plug in the second. If both cables work alone but not together, the problem is in the bonding configuration, not the cables.

Check that the switch and device are using the same bonding protocol. If the switch is set to LACP and the device is set to static bonding (or vice versa), they will not negotiate correctly. Most managed switches default to LACP, which is the safer choice.

Verify that the cables are plugged into the correct ports on the switch. Some switches require bonded ports to be consecutive (ports 1 and 2, or ports 3 and 4). Check your switch's manual if bonding is not working after configuration.

If the connection comes up but the speed does not improve, the device may not be using the bonded interface for traffic. On a NAS or media server, check the network settings to confirm the bonded interface is the one with an IP address. On a desktop, check that the bonded interface is the default route for network traffic.

Frequently Asked Questions

Do I need link aggregation for a home network?

Most home networks do not. A single modern network cable is fast enough for streaming, gaming, and everyday use. Link aggregation helps only if you regularly move large files between devices on your local network or run a media server that streams to many devices at once.

Can I bond Wi-Fi and a wired connection together?

No. Link aggregation only works with wired network cables. Wi-Fi and wired connections use different technologies and cannot be bonded. If you want faster Wi-Fi, upgrade to a newer Wi-Fi standard or move closer to your router.

Will link aggregation speed up my internet?

No. Link aggregation only affects traffic between devices on your local network. Your internet speed is limited by your modem and internet service provider, not by your local network cables.

What if my router does not support link aggregation?

You can use a separate managed switch instead. Connect your router to the switch, then bond devices to the switch. The switch handles the bonding, and your router just passes traffic through it.

Can I bond more than two cables together?

Yes. You can bond three, four, or more cables if both devices support it. The speed increases proportionally — four bonded gigabit cables give you roughly 3.6 to 3.8 gigabits per second. Most home setups use two cables because the benefit of additional cables is small and the cost and complexity increase.