[Battlemesh] multipath TCP

Christian Huldt christian at solvare.se
Thu Apr 18 14:25:27 UTC 2013


Ivan Vilata i Balaguer skrev 2013-04-18 14:46:
> Marek Lindner (2013-04-18 20:33:10 +0800) wrote:
> 
>> for those who are interested and missed the irc message:
>> http://lwn.net/Articles/544399/

Would it be possible to use this to route through a mesh (many small
flows...)? (Only for layer 3 meshes I suppose)

(btw I'm using it successfully to get a little bit more speed out of
ADSL and 4g)

-- 
Christian Huldt
+46704612207




boring data for those interested:

### ADSL
# iperf -c mptcp.info.ucl.ac.be
------------------------------------------------------------
Client connecting to mptcp.info.ucl.ac.be, TCP port 5001
TCP window size: 21.8 KByte (default)
------------------------------------------------------------
[  3] local 90.229.134.131 port 44519 connected with 130.104.230.45 port
5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.3 sec  1.00 MBytes   814 Kbits/sec

### 4g
# iperf -c mptcp.info.ucl.ac.be
------------------------------------------------------------
Client connecting to mptcp.info.ucl.ac.be, TCP port 5001
TCP window size: 19.7 KByte (default)
------------------------------------------------------------
[  3] local 90.236.125.64 port 47078 connected with 130.104.230.45 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.9 sec  1.50 MBytes  1.15 Mbits/sec

### mptcp
# iperf -c mptcp.info.ucl.ac.be
------------------------------------------------------------
Client connecting to mptcp.info.ucl.ac.be, TCP port 5001
TCP window size: 41.3 KByte (default)
------------------------------------------------------------
[  5] local 192.168.10.7 port 56763 connected with 130.104.230.45 port 5001
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0-10.0 sec  1.90 MBytes  1.59 Mbits/sec



More information about the Battlemesh mailing list