Hacker News Reader

This is all well and good until you start doing anything with address sensitive replies. For example a VoIP call would need some way of anchoring the packets to a specific connection for the duration of the call (some kind of session pinning would be ideal).

I like the idea but I wonder how it performs on many use cases (like Skype or online gaming).

View on HN

routing should be 'sticky' to an ip address; connections to any given ip address should use the same outbound route for the duration of that connection.

from http://wiki.openwrt.org/doc/howto/mwan3

Linux outgoing network traffic load-balancing is performed on a per-IP connection basis – it is not channel-bonding, where a single connection (e.g. a single download) will use multiple WAN connections simultaneously

Ahh cool! That's way better. I thought it was just channel bonding.

I can still easily imagine a conflict where your signaling IP and your media IP are different in VoIP, but binding connections to IP addresses is pretty reasonable.

Reply on news.ycombinator.com