[DSL] Basic question - Can MLPPP be applied with *ANY* ADSL line Hi,
I'm new to MLPPP.
We live in a rural area with limited bandwidth connectivity. Hence I'd like to try to bond 2 ADSL lines. They're from 2 different providers, but on the same network, provided by the same "Master" PSTN company. (Hope I express myself correctly, meaning classical phone line, we have only one such company.)
Purpose is to add e.g. 7,5 Mbps (line#1) with 4,5 Mbps (line#2) to get something like +/- 12 Mbps all together.
As far as I'm aware, bonding is not very common around here.
Can this be done WITHOUT cooperation of the providers? (As I seem to have understood that this would need to be "supported" by the provider...)
Thank you very much for answering my basic question.
Re: [DSL] Basic question - Can MLPPP be applied with *ANY* ADSL Hello,
Unfortunately it does not sound like MLPPP will work for you in this scenario. There are a couple reasons that I say this:
First of all no, it will not work with different providers. And yes, it does have to be supported by the provider you are using.
On top of that, MLPPP does not simply combine speeds. In a situation like you described where the two speeds are different it will dummy itself down to the slowest. This would leave you with the 4.5Mb being doubled. So you would be looking at approximately 9Mbps, with increased overhead. You likely won't see much of an improvement over the 7.5Mb line as a stand alone.
I hope this answers your questions, sorry I didn't have better news for you. If you have any further questions, please let us know.
TSI Keith (E-Services) - TekSavvy Solutions Inc.
Authorized TSI employee ( »TekSavvy FAQ »Official support in the forum )
Thanks for your reply.
Can you point me towards a 'possible' solution to achieve my bonding goal?
Thanks a lot,
TSI Support1TSI SupportPremium
You would need to have both lines through the same provider, and subscribe to a provider that supports MLPPP.
You would want the provider to raise the 4.5 Mbps line to a higher profile if it supports it. Honestly, if they can't, you are going to see only a marginal improvement.
Would you like any further clarification on this? If so, please ask and we would be happy to do so.
reply to ipanini
ipanini, you can use the two lines at the same time. For Windows, you just connect the two models to your computer and Windows will use either connection as it will. In Linux, there's a module that allows multiple network interfaces to be bonded and appear as a single virtual network interface called bonding.o for exactly that purpose.
Under the hood however, the two lines will operate independently from one another. Once a [TCP] connection is established, it will be established on one line and cannot hop from one line to the other. That's because each line will have a different IP address. When you send a packet out, the response will always come back on the same line. If you're watching a movie on Netflix for instance, you'll send a request to the Netflix server on one of the two lines saying "Please send me a movie". But the response, the whole ~700MB response, will have to came back the same line the request was sent on. There is no way to tell the server "Please send me half the packets on this IP and the other half on that other IP". At least not with TCP streams. There are however many file download protocols (ftp and http for instance) that can be accelerated on multiple-links using specialized software (Down Them All! extension in Firefox for instance).
To achieve what [I think] you want to do, you'd have to have a server sitting on the net somewhere that consolidates your two network connections into a single IP address and, conversely, splits any incoming traffic on the two lines. That's pretty much what MLPPP does for you.
reply to TSI Support1
Hi Ashley and JeanInNepean,
Thanks both for your answer.
Yes I would like to have further clarification on the subject.
Perhaps first some more detail:
I use OS X mostly and also Linux. (some Solaris too but only for zfs NAS) Of course also a couple of windoze boxes around.
I realize that a traffic request going out on mac address #1 will receive its reply on that same mac #1.
I'm not familiar with MLPPP, but perhaps it would be possible to say: send each 1 (first) package via mac#2 and send each 2nd and 3rd package via mac #2.
Your suggestion about protocols;
I use a lot of nzb and torrent stuff, so perhaps there I could gain some benefit.
At the moment I have a pfsense machine running, as that was my first attempt to get some bandwidth increase. However I see no traffic over my 2nd (slowest) WAN. This will very probably be due to me misconfiguring pfsense or firewall rules. I was hoping to be able to first set up "pass all" on both WAN's and after verification of functionality and speed, do more narrowing down.
Also I have a TP-Link TL-WR1043ND (version 1.7) and am thinkering of running DD-WRT or MLPPP or something on it.
Anyhow I would prefer to have a solution that is available to any machine on my network, and not only for a single machine.
Open to your suggestions!
Thanks a lot!
reply to JeanInNepean
said by JeanInNepean:Okay, I get the idea. I have a rented virtual server that I could use for some testing.
you'd have to have a server sitting on the net somewhere that consolidates your two network connections into a single IP address and, conversely, splits any incoming traffic on the two lines. That's pretty much what MLPPP does for you.
Would this mean that *ALL* the traffic would pass through this (web)server?
Or is there some way to have it function as router / gateway of some kind (like no-ip or such) in such a way that not all of the traffic passes through the virtual server?
If not this would get expensive once I'd exceed the traffic limit.
reply to ipanini
If you currently have pfSense then I recommend using its load balancing features. Basically, as each TCP connection is established it will get assigned to one of your DSL lines. A plain HTTP download will only be able to use one line, but something like a torrent or newsgroups where you have multiple connections will get full (combined) bandwidth.
All that being said, the VPS option does work too. You'd basically establish a VPN connection on each line to the VPS, and have the VPS combine the traffic from the two VPN connections. A MLPPP with PPTP rather than PPPoE basically (though it would be better for security if you could do it with IPsec rather than PPTP).
The latter setup isn't something that's commonly done. You'll also want to make sure your VPS is near (network wise) to your ISP's gateway or you'll add a lot of latency. I don't think the downsides (latency, complexity, cost) are worth it over the load balanced setup, but maybe you have particular needs that make it worthwhile.