From owner-freebsd-questions@FreeBSD.ORG Fri Feb 4 22:54:06 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FDD416A4D0 for ; Fri, 4 Feb 2005 22:54:06 +0000 (GMT) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 7FCED43D41 for ; Fri, 4 Feb 2005 22:54:05 +0000 (GMT) (envelope-from derekm.nospam@rogers.com) Received: from unknown (HELO chesed.razorfever.net) (plick@rogers.com@70.25.112.61 with plain) by smtp103.rog.mail.re2.yahoo.com with SMTP; 4 Feb 2005 22:54:04 -0000 Received: from [192.168.0.172] ([192.168.0.172])j14Ms3nA095295; Fri, 4 Feb 2005 17:54:03 -0500 (EST) (envelope-from derekm.nospam@rogers.com) Message-ID: <4203FD2E.6060705@rogers.com> Date: Fri, 04 Feb 2005 17:54:38 -0500 From: Derek User-Agent: Mozilla Thunderbird 1.0 (X11/20050112) X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org, tjg@meitech.com References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.70, clamav-milter version 0.70j Subject: Re: Routing Problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2005 22:54:06 -0000 Gustafson, Tim wrote: > I know it "can" be done. I have a feeling that the FreeBSD TCP > stack lacks the capability. If you are looking for multiple routes to the same destination, you are correct. I believe that if you see the thread on net@ from 03/01/04 with the subject "My planned work on networking stack": [] move IPv4 routing to its own optimized routing table structure and add multi-path and policy-routing options. (planned) I think this is the feature you are looking for: multi-path I am also not sure of the status of this. There are some hackish ways of dealing with this: eg. route add 0.0.0.0/1 router1 route add 128.0.0.0/1 router2 (or some such hideous incantation) If you want to get real nasty, I would try some jiggery pokery with vlans/ng_one2many: # receiving is done with public ips (all the same here as your current config) router1 vlan0 pubip1 router2 vlan0 pubip2 server vlan0 pubip1/2 #transmitting is done through faked gateway 50% load each router1 vlan1 10.0.0.1 router2 vlan2 10.0.0.1 server vlan1/2 10.0.0.2 route add default 10.0.0.1 You'll need to be sure that both upstream providers will route either ip address though. Also, there is no "dynamic" type of functionallity on this, if one of the links goes down, you'll lose 50% of your traffic. You could probably rig up a script to notify netgraph when the remote g/w goes down though. I've never tried this, but it seems this wouldn't be a bad way to start if you've got some time on your hands. Cheers, Derek