republican-creole
site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Share Topic
Post a:
Post a:
AuthorAll Replies


wifi4milez
Big Russ, 1918 to 2008. Rest in Peace

join:2004-08-07
New York, NY

reply to espaeth

Re: There is more to it...

said by espaeth:

said by wifi4milez:

Yes, however without ISP support you are doing nothing more than load balancing.
Let me try this again. It's like this:

DSL#1  10.10.10.1  <----->    MLPPP agg (Shareband) 20.20.20.1
DSL#2  10.10.20.2  <----->    MLPPP agg (Shareband) 20.20.20.2
 
MLPPP Bundle 20.20.1.1 <--->    MLPPP Bundle 20.20.1.2
Where the MLPPP bundle is built from PPP tunnels across DSL#1 and DSL#2
MLPPP bundle uses Shareband IP space inside the tunnel, not your ISP's.
 
Today when you get 2 broadband connections you get a unique IP per connection, which is why you are limited to the bandwidth of one connection at a time. (each TCP session can only have a single source IP)

Shareband builds a Point-to-Point Protocol (PPP) tunnel on each connection and then bundles the tunnels together in a MultiLink PPP (MLPPP) tunnel so that the MLPPP virtual interface on each side has a single IP address. Each packet destined for the bundle is usually split between each tunnel in a round-robin fashion so that are get the effective throughput of all of the connections minus the PPP overhead.

You can build the same thing yourself by getting a couple broadband connections at your house and building a MLPPP session to a device (be it router or server) that you colo at a nearby facility. The reason that it needs to be close is because all packets need to run to the aggregator and then out to the public Internet. If you put your MLPPP termination too far away, your performance will actually decrease due to the extra round-trip latency you pick up.

It should also be noted that this generally won't work with unlike pairs. Ie, you can aggregate multiple cable or multiple DSL connections, but not a cable and a DSL connection. The network performance difference between the two networks will result in severely out-of-sequence packets arriving at the MLPPP aggregator and performance will be crap.
Hmmm. I see what you are saying, however I am still not 100% sure how this will work in practice. I can understand how the bundling will occur on the end user side (as the physical equipment sits there), however the back end is what has me confused/doubting this application. For years, people on this website have been arguing that doing this (bundling connections) is impossible without ISP support (hence the dual WAN arguments that come up every few weeks), so unless Shareband is doing something completely revolutionary then this might just be a lot of fluff......

--
с новым годом


Stivo

@choices.org

wifi4miles,

I think you're stuck in a world of black and white - embrace the midtones.

The 'ISP side' can refer anything on the other side of the access portion of the broadband connection. ([CPE] - access - [ISP - Internet]) For the service to work, the aggregation servers can be anywhere on the public internet. The idea is that the closer the servers are to the ISPs network, the lower the latency, and the better the performance. Locating on a individual ISPs network is ideal, but not at all necessary, provided that suitable peering relationships are in place.

Hope this helps.


Tuesday, 29-May 19:10:15 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics