mptcp
mptcp copied to clipboard
multipath-tcp
Problem with MP-TCP on LEDE
Hi,
I have two TP-Link Routers running LEDE with MP-TCP v0.92 kernel version 4.4.70. One of the routers runs as an AP and the other runs as a station. I use the two wireless interfaces 60 GHz and 2.4 GHz to establish either a single TCP flow or two concurrent flows using MP-TCP. I generate the traffic using iPerf v2.0.9.
When I use the 60 GHz alone (802.11ad), I get around 1.85 GHz of throughput. Whereas, when I use the 2.4 GHz (802.11n) alone, I get almost 20 Mbps. The strange thing is when I combine two interfaces using MP-TCP (i.e. two flows at the same time), I get around 300 Mbps. So why am I getting this strange result? Should not MP-TCP achieves throughout of 1850 Mbps + 20 Mbps?
I tried to tune TCP parameters like maximum read/write buffer but with no success. Here is the network configuration.
60 GHz Interface: Network: 11.0.0.0/24 Station IP Address: 11.0.0.01 AP IP Address: 11.0.0.07
2.4 GHz Interface: Network: 10.0.0.0/24 Station IP Address: 10.0.0.01 AP IP Address: 10.0.0.07
MP-TCP Configuration: Congestion Control: Cubic MP-TCP Enabled: True MP-TCP Checksum: False MP-TCP Path Manager = Full Mesh MP-TCP scheduler = default MP-TCP syn retries = 3 MP-TCP version = 0
Can you capture a packet-trace on the sender side and share it with us? Thanks!
Attached is the traces on both interfaces wlan1 which corresponds to 2.4 GHz band whereas wlan2 corresponds to 60 GHz. I took the traces at the receiver side in my case it is the AP side. In addition, I truncated the payload to save space.
Sorry, I just realized that you asked for the traces on the sender Side. I attach new traces for 10 seconds with snapshot length of 96 bytes. I attach also the output of iPerf session.
iperf-output.txt SenderSide-Traces.tar.gz
Hello, seems like you also have an interface with a 172/8 network. Can you disable this interface for MPTCP (on both, client and server) with ip link set dev [itf] multipath off ?
In the current version,I have the old iproute2 which does not support mptcp options. As an alternative solution, I scripted everything thing to work without the management interface 172.16.17.8 (I verified that in the traces) despite that I am still getting the same low throughput. I checked the CPU usage during the iperf session and I found that when I am not using mptcp it is 20% (over the 60 GHz interface). Whereas when I enable mptcp CPU usage increases to 47%. I attach the new traces.
SenderSide-Traces-NoManagement.tar.gz