01.09.2015, 09:50, "Nigel Williams" <njwilli...@swin.edu.au>: > Hi, > > A new mptcp v0.5 patch is available at > http://caia.swin.edu.au/urp/newtcp/mptcp/tools.html. This release > represents a near-complete rewrite of the v0.4 implementation and as > such there have been a large number of changes (see [1] and [2]). The > patch applies against r285254 of HEAD. Hi Nigel,
If not early enough, I'd like to discuss mptcp<>routing interaction. It is stated in the readme that "In future releases, routing will involve using multiple FIBs and and route management within the MP connection". My question is - how route management is planned to work: e.g. if we have fibs 1 and 2 w/ default route, what will instruct connection to use given fibs? application? kernel itself? if we have multiple default routes in fib 0 (and we're using single fib), what will make connection utilize both routes? what kind of kernel interfaces might be needed for that case? e.g. my current understanding is that you need - the ability to get number of nexthops (routes) to particular destination at the session setup - the ability to select particular nexthop in ip[6]_output routines - the ability to track nexthop changes for particular destination (route addition/removals) What's you vision on this? > > Current functionality is slightly advanced of the previous patch, though > the new code base should allow for an increased rate of improvement over > the next few months. I'm hoping to keep to release incremental updates > on a more regular basis over this time period. > > Along with the patch there are also pre-configured VMs and a pre-built > kernel binary available for download, for those who want to try it out > without going through the patching/building process. There is also a set > of scripts that demonstrate some basic multi-path connections. > > The patch is still under heavy development and testing so consider this > release code to be of alpha quality (expect bugs/panics etc). Currently > it supports MPTCP for FreeBSD-to-FreeBSD connections only. Feedback re > bugs encountered or suggestions on code/design improvements is welcome. > > To come in the near future: > - A public-facing source repository > - A report that details the design of the current implementation > > This work has been made possible in part by grants from the FreeBSD > Foundation, and The Cisco University Research Program Fund at Community > Foundation Silicon Valley. > > cheers, > nigel > > [1] http://caia.swin.edu.au/urp/newtcp/mptcp/tools/v05/mptcp-readme-v0.5.txt > [2] > http://caia.swin.edu.au/urp/newtcp/mptcp/tools/v05/mptcp-changelog-v0.5.txt > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
