Date: Thu, 26 Jun 2008 12:54:33 -0700 From: Julian Elischer <julian@elischer.org> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: freebsd-hackers@freebsd.org, martes@mgwigglesworth.com, Luiz Otavio O Souza <luiz@aonet.com.br> Subject: Re: [Fwd: Re: 3 connections as one] Message-ID: <4863F3F9.6020206@elischer.org> In-Reply-To: <200806261742.m5QHgbWo020788@apollo.backplane.com> References: <1214430974.26401.0.camel@devstation> <4862DCB5.6080005@elischer.org> <001901c8d78d$8180c680$5e00a8c0@note4c47> <200806261653.m5QGrasG020325@apollo.backplane.com> <4863CCF4.3000200@elischer.org> <200806261742.m5QHgbWo020788@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Dillon wrote: > :I've done that running mpd to split the load over the tunnels from the > :colo. > : > :if either tunnel goes down mpd hickups nd hten everything keeps going.. > :.. > :mpd does this for me.. > > That looks almost perfect for the colo idea. I see how the links are > set up and I see the bundle directive, but how do I configure a common > subnet? Do I specify the same subnet for all the links and make them > part of the same bundle (on both ends)? > > Is there a way to backhaul the bundle onto a single TUN interface? > Or is that what ng_eiface is for? I need a tie-in for PF's QOS. > There's no choice about that, my network is 100% saturated 24x7 and > if I don't use PF's QOS with fair-share scheduling it becomes unusable. the ng_iface that is created (ng0 or whatever) is the virtual connection back to the colo. now that we have multiple routing tables we can make the tunnel and its contents use different routing tables which can simplify things. mpd allows you to backhaul through udp or tcp transport 'tunnels' to the remote poitn of your choice. > > Looks like I might have to update netgraph on DFly to use mpd, but it > doesn't look too difficult. But, gods, all those M_NOWAIT kernel > mallocs... how can that possibly be reliable? what can I say without degenerating into a dogfight? The code is designed to copy with failure to allocate.. the error will propogate up.. not much is allocated once you have it set up. > > -Matt > Matthew Dillon > <dillon@backplane.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4863F3F9.6020206>