<div dir="ltr"><div>I've been using net2atlanta for consumer internet for a whiles. No major complaints.<br><br></div>-- CHS<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jul 12, 2014 at 2:41 PM, Michael Trausch <span dir="ltr"><<a href="mailto:mike@trausch.us" target="_blank">mike@trausch.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I can do a more detailed write-up later, perhaps, but here's the 30,000<br>
foot overview for a "simple" setup:<br>
<br>
- You have a single Linode ("BISP"), which has at least 2 IP addresses<br>
(and a pool of routed IPv6 doesn't hurt—Linode does that for you for free,<br>
but in blocks smaller than /64).<br>
- You have an edge router which is attached to two separate "real" ISPs<br>
("BER"). Ideally, the ISPs have static IP addresses. If you don't, you'll<br>
need to add some machinery to ensure that the tunnel endpoints stay<br>
up-to-date. I don't consider this problem since I don't have dynamic<br>
addresses.<br>
- You configure the BISP system to have two virtual (layer 2) interfaces<br>
which will talk to BER, one for each "real" ISP.<br>
- You configure the BER system to have two virtual (layer 2) interfaces<br>
that talk to the Linode. This is where it starts to get interesting. You<br>
need to configure the system so that there is one route to the Linode IPv4<br>
#1 over ISP 1, and one route to the Linode IPv4 #2 over ISP 2. Then ensure<br>
that BER and BISP are both routers (kernel forwarding is turned on).<br>
Establish the tunnels and test them individually. If at this point you're<br>
working, you can continue.<br>
- Now, create a bonding interface on both BER and BISP. Configure them<br>
using the same parameters, and add the two tunnel interfaces to the bond<br>
point in same manner as you would with Ethernet cards. At this point,<br>
perform link testing and ensure that you're using both connections between<br>
yourself and the Linode. You should at this point be able to transfer data<br>
between yourself and Linode faster than with a single connection alone.<br>
- Configure your network to use BER as a network gateway, and enjoy a<br>
faster connection!<br>
<br>
Now, there are some caveats:<br>
<br>
- You might want to configure very-high bandwidth things of<br>
not-terribly-high import to simply use your faster leg. For example,<br>
Netflix. You don't want all that crap going through your Linode.<br>
- There are plenty of opportunities for traffic management, depending on<br>
the needs for your own network.<br>
<br>
However, at this point, your network should remain online as long as it has<br>
power and at least one of the ISP links is working and active. You can add<br>
extra IP addresses e.g., at Linode and route them to your network (using<br>
Proxy ARP in order to chain-route; like any ISP, Linode assumes that<br>
they're the "last hop", meaning that if you need to relocate the IP address<br>
or use it e.g., for dial-up or other PPP links, you're going to need to<br>
have a suitably-configured proxy ARP config on BISP).<br>
<br>
Hope this helps. It's lacking in tons of detail, but it should have enough<br>
to get you going—or at least give you an idea.<br>
<div><div class="h5"><br>
<br>
On Sat, Jul 12, 2014 at 2:00 PM, Phil Turmel <<a href="mailto:philip@turmel.org">philip@turmel.org</a>> wrote:<br>
<br>
> On 07/12/2014 11:46 AM, Michael Trausch wrote:<br>
> > Stacked and bonded connections.<br>
> ><br>
> > E.g., comcast and att, with bonding interfaces at a linode for bandwidth<br>
> aggregation and failover.<br>
> ><br>
> > More expensive than "simple" internet, but cheaper than leased lines and<br>
> more flexible, too.<br>
><br>
> I've been considering this in the near future... At the moment, only<br>
> Comcast serves my office complex at >8mb/s, unfortunately. But AT&T has<br>
> indicated they are working to bring U-Verse to the party. U-Verse<br>
> (internet only) has been rock solid at my home. Comcast Business at the<br>
> office, not so much.<br>
><br>
> Can you share details of your routing/bonding configuration? Or point<br>
> to a howto you recommend? I'm familiar with layer 2 bonding between<br>
> switch and server, not with remote links.<br>
><br>
> Phil<br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
><br>
</div></div><div class="">-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
</div>URL: <<a href="http://mail.ale.org/pipermail/ale/attachments/20140712/d9d8de55/attachment.html" target="_blank">http://mail.ale.org/pipermail/ale/attachments/20140712/d9d8de55/attachment.html</a>><br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br></div>