this post was submitted on 13 Nov 2023
1 points (100.0% liked)
Home Networking
11 readers
1 users here now
A community to help people learn, install, set up or troubleshoot their home network equipment and solutions.
Rules
- Please stay on topic.
- Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered.
- No Ads. This community is for support and discussion. Ads and self promotion are not welcome here.
- No product reviews or announcements. If you have a question about a product, be specific about what you want to know.
- Be civil. Don't be a jerk. Not being a jerk is surprisingly easy.
- No URL shorteners. URL shorteners tend to hide the real use of a link. For this reason, please use normal links, even if they're long.
- No affiliate links.
- No gatekeeping. With profession shall come professionalism. Extend help without judging others for their ignorance. The same goes for downvoting of comments or posts for "stupid questions" or not being as knowledgeable as others.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
LAG only works well when there is a sufficient diversity of traffic flows that can be distributed equitably across the child links. Since many LAG implementations hash only on MAC and/or IP addresses, the distribution can often be poor when there are only a few clients, as is often the case in a home network. This can possibly be finessed by careful assignment of IP addresses, but the point is LAG doesn't guarantee access to the entire aggregate throughput of the child links.
For this reason, I believe LAG is seldom worthwhile in a home network.