Is it possible to have PPP multilink (CONFIG_PPP_MULTILINK) enabled in the "Latest 2.6 Series" kernel or a future version?

Relevant documentation is here:
Documentation/networking/ppp_generic.txt

Thanks for your consideration.

-Aaron

Just out of random curiosity, why would one want PPP anything on a linode? I tend to associate PPP with modems and bad DSL providers.

_________________
The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world.
-- seen on the net

I might have a pretty unique situation. I'd like PPP multilink for improved upload performance to my linode. I have redundant ISPs, but neither have good upstream, so I'd like to be able to join PPP-over-SSH links (one per provider) for much improved upload performance.

-Aaron

Hi.
Has this request been actioned?

I'm trying to setup multilink ppp with vtun on my linode but I'm getting the following error, which I believe might be because multilink isn't supported by the kernel.

Dec 11 16:04:53 soapartners pppd[10351]: Couldn't set MRRU: Inappropriate ioctl for device

On the client side I get failure messages from the linode (server)
Dec 11 16:05:17 rpi pppd[4060]: Protocol-Reject for unsupported protocol 'Multi-Link' (0x3d)

According to the linode dashboard this is what I'm running:

Ubuntu 12.04 LTS x64 Profile (Latest 64 bit (3.16.7-x86_64-linode49))

Regards,

Eddy

Your best bet is probably going to be https://www.linode.com/docs/tools-refer ... s-distros/

- Les

As one of the authors of the defunct Tomato/MLPPP project, I can tell you that the stock MLPPP support in the kernel is a tad buggy. It's been tagged experimental for so many years, and if memory serves we had to do some kernel patches to get things working well enough for a consumer product.

I'm also not sure that it's the best solution here. PPP over SSH is going to suck in general, because there's a lot of overhead to SSH tunnels, and running a VPN over TCP is a bad idea in general.

There are other VPN-based solutions for bonding connections that will probably work better. For example, using a UDP-based VPN like OpenVPN to provide two tun interfaces, and then using the bonding driver on top of that to do interface-level bonding.