#SPEEDIFY BONDING MIKROTIK PC#

You can bond up to 8 connections according to the developer, and those need to be reconstituted into a single connection (with a public IP!) on the server end. I used a Raspberry Pi 4 with 4GB of RAM:Įxt4 images are preferred over squashfs, when both are offered.īefore you start configuring your OpenMPTCProuter device, you'll want to get your VPS (Virtual Private Server) running, as WAN bonding always depends on having a server on the other end with a very high speed Internet connection.

It's OpenWRT based, so this should be familiar territory for everyone here.

Here's how I did it, just in case there are others that have WAN bonding on their 'to do' list.ĭownload whatever version will work with that extra bit of kit you have laying around and get it up-and-running. Like many other projects, it's easy to get off track without a little guidance, and OpenMPTCProuter is a bit thin on tutorials. I'm happy to say after a number of failed attempts at getting WAN bonding working properly - I've finally got it functioning the way I want. I'll bring a 2vCore VPS online sometime soon. OpenMPTCProuter needs an Internet appliance with some horsepower, but it has proved amazing for true WAN bonding - there's little else like it! With my low end VPS (1vCore, 1GB RAM, 25GB vSSD), I'm frequently topping out at about 235Mbps on the D/L.

#SPEEDIFY BONDING MIKROTIK PC#

I did this post in late January, and I've since moved from the Raspberry Pi 4B to a Qotom x86 (i3) industrial PC with 4x gigabit Ethernet ports, 2x USB3 and 2x USB2 ports. Here's another post I did earlier this year on the ROOter forum, which is now a bit difficult to find.

Speedify bonding mikrotik