I’ve been brainstorming the past few days about how to make Samba which is a single session single tcp connection able to be split across 2-4 LACP layer 3+4 links. I’m quite aware of samba and LACP’s drawbacks when not using RDMA or server side multi-channel connections (RSS). Load balancing with LACP over multiple NIC’s with samba isn’t really possible unless it coming from multiple users. Faster NIC’s is always the best answer, but under constraints you have to think harder.
So I need an opinion before I waste some time. What about using WireGuard locally within your network not routing it to the internet. Encapsulating the tcp connection using a udp VPN tunnel might allow the tcp packets to be spread between all available NIC within the bond. Since the router just see this as udp packets.
Maybe I’m grasping or would WireGuard act the same as sambas single session single connection. LACP is really meant for switch to switch load-balancing/failover of many connections. So I’m thinking I’m sol.
Thoughts?
So I need an opinion before I waste some time. What about using WireGuard locally within your network not routing it to the internet. Encapsulating the tcp connection using a udp VPN tunnel might allow the tcp packets to be spread between all available NIC within the bond. Since the router just see this as udp packets.
Maybe I’m grasping or would WireGuard act the same as sambas single session single connection. LACP is really meant for switch to switch load-balancing/failover of many connections. So I’m thinking I’m sol.
Thoughts?
Last edited: