Date: Fri, 6 Apr 2001 07:15:58 -0700 (PDT) From: Benjamin Gavin <virtual_olympus@yahoo.com> To: freebsd-net@freebsd.org Subject: Re: Multi-provider load balancing Message-ID: <20010406141558.44180.qmail@web9615.mail.yahoo.com> In-Reply-To: <Pine.BSF.4.21.0104052242530.13888-100000@cody.jharris.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Also, and perhaps I should be more clear: 1. I am load-balancing outbound connections from an internal (non-routable) network. 2. There are hardware solutions that do this. 3. There are Windows based programs that do this. I will look into that probability stuff for ipfw, thus far it looks promising. My only concern is that packets coming back in get redirected to the correct natd process, but I can probably control that by using a slightly modified ruleset. Also, the rest of the internet sees my outgoing connections as generating from two separate endpoints. I'm not trying to provide access to internal web sites, DNS, etc through these connections, so I fail to see how assymetric routing would have anything to do with this. I've also checked with a couple people who are addmittedly more versed in TCP/IP and routing and they seemed to think that it would be possible to set something up as I propose. I understand the purpose of BGP, but I just don't think it applies in my case. This is for a simple home network, and every home network in the world is hardly going to apply for an AS number if this type of thing is going to be widespread (nor can they afford to buy expensive hardware solutions). Thanks again, Ben --- Nick Rogness <nick@rogness.net> wrote: > On Thu, 5 Apr 2001, Benjamin Gavin wrote: > > > Hi all, > > I've got a problem. I have two providers (cable modem/DSL) and I > need > > to load-balance the connection between them. I don't want to do BGP, > and > > would prefer something that is marginally easy to maintain. I don't > care > > about balancing based on load, simple round-robin style balancing > would be > > fine. Here's a "picture": > > > > Internal Network (192.168.x.x) > > | > > v > > FreeBSD 4.2-RC firewall > > | | > > V V > > cable DSL > > > > Each external side is currently DHCP, but could be static if > necessary. > > What I need is when a request goes out through the firewall for the > > machine to basically "choose a side". Then once the connection is > > established it could stay on that pipe, or flip back and forth > (whichever > > is easier). > > > > Here's what I've tried: > > > > 1. ipfw + 2xnatd, doesn't seem to work, since ipfw rules can't > randomly > > choose on of two rules (AFAIK) > > Check out the probability stuff in ipfw. There has been a battle > over this for a while. Many people say that you MUST run a > routing daemon (ie BGP) to do this. Don;t know about ipfilter. > > > Nick Rogness <nick@rogness.net> > - Keep on Routing in a Free World... > "FreeBSD: The Power to Serve!" > __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010406141558.44180.qmail>