Live data from Hacker News

Multipath routing on a Raspberry Pi 2

whizzy.org

11–12 of 12 posts

Re: Multipath routing on a Raspberry Pi 2

#11
post #8

Very cool project. One downside to this approach is that each tcp connection cannot use more than one link's bandwidth. I've been meaning to try this with a multipath VPN to work around that issue but haven't had the time yet.

I tried this[0] and successfully round-robin packets in a single stream. Problem was that the two links had different latencies and Linux has no tolerance for out of order packets. Instead, it would cause a huge number of retransmissions. [0] https://github.com/erjiang/tuntuntun

Interesting, even so was it a net win?

It looks like tuntuntun is pretty basic, my thought was OpenVPN with null encryption over MPTCP. But the combination would obviously have a lot more overhead than that.

Re: Multipath routing on a Raspberry Pi 2

#12
post #7
post #6

I do not know much about networking but: > I don’t really get how, in the case of an HTTP conversation (or flow) which is connectionless, all the packets in the conversation get marked the same. What do you mean? HTTP is stateless, not connection-less. This is probably related to: > Although HTTP is a connectionless protocol this change of IP address did seem to freak some services out. Maybe what you saw is a single…

I thought he would put all the connections back together on the other end with VPS or something.

quite a few outfits do this with MPTCP, with varying degrees of success.
Post reply on HN